Don’t Panic!

Before you go any further, make sure you’ve updated your plugins and themes to the latest versions, clear your browser’s cache and cookies and re-log into your WordPress dashboard.

The New Editor can be disabled!

If you’re in a pinch and need the editor rolled back ASAP, please install the classic editor – https://www.ads-software.com/plugins/classic-editor/ – which will restore the old editor.

Still having problems? Okay, read on!

This thread contains the known issues with plugins and themes found in 5.0. Please read this WHOLE topic and come back and check again later, as it will be updated.

Remember to be calm, be patient, and be respectful. Volunteers are out here to try and help you, but we need your help too. All of the normal?forum rules still apply. Remember, you are just as important as everyone else.

If your post doesn’t show up right away, please be patient. With the higher than normal post volume, more posts get flagged as spam by our auto-spam tool. We’re working hard to keep the queue clear, but making multiple posts slows us down, as we have to go back and check if you already posted. Post once.

• Do?use proper capitalization in post titles and body. Punctuate your sentence properly and humanely, it helps us read.
• Do?use descriptive subject lines. “All permalinks broken since 5.0” is much better than “Augh! Help ASAP! This version is terrible!”
• Do?describe the problem clearly. Explain what you’re seeing, include error messages and link to screenshots if needed. Linking to your site, if the problem is on the front-end, also helps.
• Do?be patient. We know it sucks to be down, but posting multiple times doesn’t get you help any faster.
• Do?make your own topic unless you are using the exact same version of WordPress on the same physical server hosted by the same hosts with the same plugins, theme and configurations as the original poster. You may find it weird, but it will be easier for us to help you specifically if you have your own topic.
• Do?mark your topic as resolved when it’s fixed so we know not to come looking there anymore.
• Do?remember you’re not alone.

Also keep in mind that not liking the direction of WordPress’s design is a not a bug. If you don’t like a feature, please don’t make a series of posts complaining about it. Look and see if someone already did, and post there, or?consider joining the process earlier on?(like in Beta or even test via SVN). What you’re seeing today is the result of thousands of hours of work and testing, and unless something is outright broken, it’s highly unlikely to be changed.

Again,?before?you post:

Make sure you’ve read this entire thread and?New Features in 5.0 Article.

Go to your own install’s about page –?example.com/wp-admin/about.php?(or click the WordPress logo in the top corner) – to see what’s new.

• Flushing any caching plugins you might be running, as well as server and/or?browser caches. Not just your browser, but any op cache or content network cache as well?such as Cloudflare. That will solve many weird JavaScript issues.
• Flushing Managed host caches. Managed WP hosting often has special caches. If your host has a “Purge Varnish” or “Flush Memcache” tool, try that. You can ask your provider to flush memcache and Varnish for you if necessary.
• Resave your Permalink settings. In a few cases, we’ve seen third-party installers, such as Softaculous, creating sites with slightly incorrect rules in the .htaccess file. While these rules would not have been a problem in previous versions, in WordPress 5.0, having these incorrect rules can break the REST API. Resaving the permalinks on the Settings->Permalinks page in WordPress will fix these rules in the .htaccess file, and possibly fix “failed” errors in the new editor.
• Troubleshooting with your browser. Your browser can help you identify JavaScript issues or conflicts and?this article can assist you in doing that diagnosis. This could help identify Visual Editor issues as well.
• Make sure you have the Visual Editor enabled. Visit your Users->Your Profile page. The first option will disable the visual editor. Make sure that option is unchecked, and save your profile settings.
• Deactivating?all plugins?(yes, all) to see if this resolves the problem. If this works, re-activate the plugins one by one until you find the problematic plugin(s). If you can’t get into your admin dashboard, try resetting the plugins folder by?SFTP/FTP?or PhpMyAdmin (read “How to deactivate all plugins when you can’t log in to wp-admin” if you need help). Sometimes, an apparently inactive plugin can still cause problems. Also remember to deactivate any plugins in the mu-plugins folder. The easiest way is to rename that folder to?mu-plugins-old
• Switching to the Twenty Nineteen theme to rule out any theme-specific problems. If you can’t log in to change themes, you can remove the theme folders via?SFTP/FTP?so the only one is?twentynineteen. That will force your site to use it.
• Manually upgrading. When all else fails, download a fresh copy of the latest.zip file of 5.0.* (top right on this page) to your computer, and use that to copy up. You may need to delete the wp-admin and wp-includes folders on your server (NOTE: do not delete the?wp-content?directory or your?wp-config.php?file) Read the?Manual Update directions first.
• If you can install plugins, install “Health Check”:?https://www.ads-software.com/plugins/health-check/On the troubleshooting tab, you can click the button to disable all plugins and change the theme for you, while you’re still logged in,?without affecting normal visitors to your site.

If you need to create a support topic, the?Health Check plugin?is also able to provide debug data for the support volunteers.

Noteworthy and recurring scenarios users are encountering that are not actually bugs, but rather changed or new behaviors.

None as of yet.

Bugs that have been reported against this release of WordPress, with links to tickets for further followup will be listed here.

As WordPress 5.0 is a special release, some known issues have been pre-emptively ticketed, and can be seen in the WordPress 5.0.2 milestone?and WordPress 5.0.x milestone?respectively.

* 5.0 does not recognize the date format l j F Y – This appears to be a translation issue and should be corrected per-language pack.
* CSV files fail to upload properly in 5.0.1 – This is due to a security patch to validate CSV filetypes. The files are saved as text/plain instead of text/csv See Trac 45615 for details.

This section contains noteworthy (high impact/large) plugins with compatibility issues, and their responses when available.

• Advanced Custom Fields (ACF) version 5.7.7 is not fully compatible, find out more about known limitations in their blog post. Resolved in version 5.7.8
• WPML are reporting compatibility issues with WordPress in their latest version at this time (2018-12-07). WPML has released 4.1 which is compatible with 5.0. However please read their announcement post which recommends delaying updates.
• The TinyMCE Advanced plugin has been updated, and has a new “Hybrid Block Editor” mode, which defaults to enabled. This may cause confusion on the plugin update, as having this option enabled will remove the default blocks in favor of others. Notably, the “Paragraph” block may seem to be missing. The normal blocks can be restored by disabling the plugin, or turning off the “Hybrid Mode” in the plugin’s settings screen. The TinyMCE Advanced plugin no longer replaces the default blocks.

This section contains noteworthy (high impact/large) themes with compatibility issues, and their responses when available.

None reported at this time

The new block-based editor (called Gutenberg during it’s development) can be disabled by installing the CLASSIC EDITOR plugin

https://www.ads-software.com/plugins/classic-editor/