James

@obiedo32 YMMV is short for “Your mileage may vary”. What I meant to communicate is that the functions file modifications worked for me, but your situation may work out different ??

Glad you were able to get things working @jwmc.

@obiedo32, the thing that helped me solve my issue is detailed in this post. If CloudFront is not part of your architecture, or something you have control over, you can test adjusting your functions.php like the post describes.

Obviously YMMV, and i suggest backing up your site before making an edit like that.
Good luck ??

@rzon Thanks for the post, this may be something people want. But I don’t want future readers to this think this will solve the issues this thread addresses.

For future readers, the issues with Amazon CloudFront removing headers were present in my system when Gutenberg was installed and also after Gutenberg was removed. Please note in my original post:

Removed and Added Jetpack, Gutenberg, and Classic editor plugins many times while debugging this issue

Glad to hear it @gregsh303!

I’m happy to report the same, our site’s editor is working again ??

I asked our host to look into this issue of header caching and he gave me the following explanation and solution:

I added the following to the functions.php file in the theme. Researching it I found that WP does an odd thing in looking at the UserAgent to determine if it should show the editor or not. […] A CDN strips the UserAgent out to improve caching, so the following code forces it to be shown. […]

function richedit_wp_cloudfront () {
   add_filter('user_can_richedit','__return_true');
}

add_action( 'init', 'richedit_wp_cloudfront', 9 );

I can confirm it’s fixed now.

Fixing your headers in CloudFront should take care of this, or utilize the above code in your theme’s functions file (YMMV, of course).

Many thanks to @designsimply for so much help, here and on GitHub. And a thank you to @g3luka for suggesting that headers and CloudFront behaviors were the issue!

• This reply was modified 6 years, 2 months ago by James.

@gretche I’m not quite sure how to achieve what you’re asking.

Sounds to me like your issue is different from mine, though. I recommend creating a separate topic.

@mattsmith33 Have you walked through the previous suggestions in this post yet?

I’m especially curious to see if @g3luka’s suggestion works for anyone else (I’m still workin through this with my host and will post an update once I know).

@designsimply, I’ll definitely check in on the headers and update here and GitHub with what I find. Thanks so much for all your work and suggestions!

@designsimply, @g3luka

I’ll be looking into CloudFront behaviors and headers with my host, maybe there is something to that? Thanks for the tips from both of you!

@designsimply

They’ve noted that they are using an EC2 instance going through a load balance and through CloudFront with Route53 set to the domain.

Do you have a similar setup by chance?

Our site is run by a third-party host and they use AWS, but I’m not sure about much more than that. I don’t know of any load balancers. I plan to ask my host to get involved soon, probably after the holidays at this point ;).

Thanks @designsimply

I ignored that solution since I didn’t really understand it and it looked like a long shot to me as well. But, I may as well try to understand and give it a try.

I may still not understand enough about APC and what effect it has on my WP instance but the Health Check’s PHP information and the PHP manual’s APC configuration options seem to indicate I have the defaults in place. Here’s a screenshot of the segments and size properties for my site. apc.enabled is set to On.

My guess is that the solution from that post doesn’t really apply to my situation.

Thanks @arabnas

In my original post, I mention that I have verified that the option to disable the Visual Editor is unchecked:

Verified that the option to disable the visual editor is unchecked for my user account

@edwardroofvents, thanks for the tip ??

i got the email telling me about my site’s auto-update to 5.0.2 last night and checked as soon as i could!

Unfortunately, i’m still in the same boat.

i’ve found a few issues on Gutenberg’s GitHub page that seem related to this problem. Here’s a list for reference:

• Cannot add block for any post or any user! #12927
• Need a better experience for users when switching between Visual Editor and code editor #12881
• The visual editor is not available #12760

I think I’m experiencing the same thing, and have a post about it on this forum too.

@designsimply had some good additional recommendations in that thread (after running health check, which is a very good suggestion). even though they didn’t solve my issue, maybe they’ll be helpful?

Hi @designsimply, thanks for your attention and assistance!

I have tested with all plugins turned off using troubleshooting mode. I did mention it above:

Run health check and have done all this with troubleshooting mode on and all plug-ins disabled

…but after reading my original post I can see where the state of the site during my testing and screenshots (and the current state of my site) is not clear. I hope this helps:

1. I uninstalled the Gutenberg plugin after installing WP 5.0.0
2. All gutenberg-related issues above were tested in troubleshooting mode with WP v5.0.1, 2019 theme, all plugins disabled
3. The classic editor issues were tested in troubleshooting mode, WP v5.0.1, 2019 theme, all plugins disabled except the classic plugin

The Gutenberg plugin was already uninstalled, and I have just uninstalled the Classic Editor plugin (it was already disabled, but now it’s gone completely). With the classic editor plugin removed, I still see the same issues in multiple browsers:

• Chrome 71 on Win10: Can’t add a block and only can access HTML, no visual mode. There are no JS errors in the console.
• Edge 42 on Win10: Can’t add a block and the editor is stuck in HTML, no visual mode available (sorry, didn’t look at the JS console. I can, though, if that would be helpful.)

Thanks again ??

• This reply was modified 6 years, 2 months ago by James. Reason: Simplify wording
• This reply was modified 6 years, 2 months ago by James. Reason: Add notes on other continuing issues