Opened 6 years ago
Last modified 5 years ago
#44516 new defect (bug)
Unable to edit theme's file on multisite from default editor
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Awaiting Review | Priority: | normal |
| Severity: | normal | Version: | 4.9.6 |
| Component: | Administration | Keywords: | reporter-feedback |
| Focuses: | multisite | Cc: |
Description
I am using WP 4.9.6 and on multisite when I tried editing theme's files from the editor it shows that it generated some fatal error. The actual message is 'Unable to communicate back with site to check for fatal errors, so the PHP change was reverted. You will need to upload your PHP file change by some other means, such as by using SFTP.'
Please see: https://prnt.sc/k2mshy
Attachments (1)
Change History (5)
This ticket was mentioned in Slack in #core by talldanwp. View the logs.
5 years ago
#3
follow-up:
↓ 4
@
5 years ago
- Component changed from Editor to Administration
- Focuses multisite added
- Keywords reporter-feedback added; needs-patch removed
#4
in reply to:
↑ 3
@
5 years ago
Replying to jeremyfelt:
Thanks for opening a ticket @prashantvatsh, sorry for the delayed response.
Is this still an issue in WordPress 5.3.2?
If so, it would be helpful to know a few things that may help in reproducing the issue:
- Is this a subdomain or subdirectory configuration?
- Does the issue occur when all plugins are disabled and when a default theme is activated?
- Are you able to upload media files or plugins manually?
I've changed the component from Editor to Administration as I'm not sure we really have a component that covers the file editor. I'm also going to attach the screen shot directly so that the link to it is unnecessary.
- I tried this on the subdirectory configuration.
- Yes, all the plugins were disabled and Twenty Twenty theme was active during my latest test.
- Yes, I am able to upload plugins manually in the plugins folder and then could easily activate them.
Please check the latest error screenshot: https://prnt.sc/qe2l7x
The error is coming in the latest version of WordPress as well.
Thanks for opening a ticket @prashantvatsh, sorry for the delayed response.
Is this still an issue in WordPress 5.3.2?
If so, it would be helpful to know a few things that may help in reproducing the issue:
I've changed the component from Editor to Administration as I'm not sure we really have a component that covers the file editor. I'm also going to attach the screen shot directly so that the link to it is unnecessary.