|
ICLE
|
July 2, 2019 at 1:15 pm
https://monosnap.com/file/KLwABQRA04UD4cjqHU8fZ3VLVw0WWc
On the left is my localhost version, on the right is my production site.
How can I get the editor back?
I have tried the wp-config.php method of inserting:
define(‘CONCATENATE_SCRIPTS’, false);
and that didn’t seem to effect it.
|
|
Josh
|
July 2, 2019 at 1:36 pm
Hi,
I’m not sure. Can you compare the differences between the localhost version and production site? For example does one site have plugins that the other site does not have?
|
|
ICLE
|
July 2, 2019 at 1:48 pm
The localhost has all sorts of weird and wacky plugins the production site does not have.
This is critical. You have never seen this before? We just launched Friday!
|
|
Josh
|
July 2, 2019 at 2:21 pm
Hi,
I have not seen this before. May I assume that the production site was OK up until recently? Or was it not ever working, in which case your deployment from staging to production may have not included some critical files.
|
|
ICLE
|
July 2, 2019 at 2:25 pm
Nope. Had been running fine for a year. It was not deployed: it was my dev and we went live with it.
It was working fine until today. I can even see the wp-content-editor-container instance in the devtools, it just isn’t displaying.
devtools can see the block
|
|
Josh
|
July 2, 2019 at 2:39 pm
Have you checked to see if the content editor is being hidden with CSS?
Since it was working fine until today, can you revert any recent changes that may be causing this?
|
|
ICLE
|
July 2, 2019 at 5:58 pm
Solved.
The ACF editor has a list of functionality to HIDE when checked.
Content Editor was checked.
There are no stupid questions or stupid solutions. Right?
This will help someone!
Please award me a newbee-shame badge.
|
|
Tony
|
July 3, 2019 at 4:28 am
It’s an easy thing to miss but I’m glad you found it anyway 🙂
|
