Support » Fixing WordPress » READ THIS FIRST WordPress 5.4 Master List

  • Moderator Marius L. J.

    (@clorith)


    First steps | Core changes | Not a bug | Reported bugs | Plugin issues | Theme issues ]

    Hooray! WordPress 5.4 “Adderley” is here! But OMGWTFBBQ!? Everything is now broken?

    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 in to 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 – wordpress.org/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 the latest release. 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 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.4 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.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Moderator Marius L. J.

    (@clorith)

    Before posting, please make sure you’ve tried started by performing the troubleshooting steps outlined below:

    • 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, having these incorrect rules can break the REST API in newer versions. 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
    • If you can install plugins, install “Health Check”: wordpress.org/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.
    • Switching to the current default 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 twentytwenty. 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.4.* (top corner 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 need to create a support topic, you can provide debug data for the support volunteers by visiting the Site Health section under Tools > Site Health > Info.

    Moderator Marius L. J.

    (@clorith)

    Fullscreen editing by default

    The block editor will by default display in fullscreen mode after WordPress 5.4.

    For instructions on how to leave fullscreen mode, please see our article about the block editor.

    Note: Some browsers, most notably Safari, does not properly remember your settings at the time of release for WordPress 5.4.0, you can use the Blockeditor Fullscreen Mode Control plugin to persistently save this option and change the default display at this time.

    Changes to the calendar widget

    The calendar widget had some changes made to its HTML code, this may mean that your theme might not display it as you would normally expect, if you are using the widget, and it looks a bit out of place, please reach out to your theme author for an update.

    More Details

    You can find all the release details in the Field Guide.

    Moderator Marius L. J.

    (@clorith)

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

    • “The editor has encountered an unexpected error”. This message often appears with this in the browser console: “TypeError: Cannot read property ‘DotTip’ of undefined”. This error is caused by either an incomplete upgrade of your site, or your site using aggressive caching plugins or systems. Basically, the old javascript code, from the previous version of WordPress, is still being sent to your browser. You need to clear any server side caches, clear any caches with CloudFlare, and purge your browser cache as well. If you are using Cloudflare, check the settings and ensure that the Cloudflare caching level is set to “Standard” or “No Query String”. The “Ignore Query String” option is not compatible and should not be used.
    • “The Buttons Block is missing the ability to align buttons!” – No, it has that ability, You just can’t find it. Here is an imgur album which should help you figure out how to align buttons: https://imgur.com/a/57Kt0l5
    Moderator Marius L. J.

    (@clorith)

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

    • Media Uploader interface is not working on all browsers (currently known to be problematic: Edge, iOS Safari) — Trac #49753
    Moderator Marius L. J.

    (@clorith)

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

    • KingComposer – infinite load on editor page.
      Update of the plugin has been released version 2.9.2
    • The AMP plugin had an issue that could cause reusable blocks to be deleted. This is not directly connected to WordPress 5.4, but it happened in the same timeframe. To solve, update the plugin to version 1.5.1.
    • This reply was modified 6 months, 4 weeks ago by Marius L. J..
    • This reply was modified 6 months, 3 weeks ago by t-p. Reason: update of the plugin released, version 2.9.2
    Moderator Marius L. J.

    (@clorith)

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

    • Preview of blocks in the Block Editor has errors with current version of Hestia theme. See: https://wordpress.org/support/topic/problems-with-blocks-in-hestia-after-wordpress-updating-to-wordpress-4-5_nl/ <br>An update of the theme has been released that hopefully solves the issue, see comments under he linked post.
    • Some non-free themes from paid sources cause minor incompatibility issues with the latest version of the block editor. These can manifest as “This block has encountered an error and cannot be previewed”. Go to where you purchased your theme, and download an update for it. The marketplace where you bought the theme may have an update plugin you should use to keep the theme up to date.
    • Stargazer (free) theme not compatible with the block editor
    • This reply was modified 6 months, 4 weeks ago by Marius L. J..
    • This reply was modified 6 months, 4 weeks ago by tobifjellner (Tor-Bjorn Fjellner). Reason: Added notice about failing block preview with Hestia theme
    • This reply was modified 6 months, 4 weeks ago by tobifjellner (Tor-Bjorn Fjellner). Reason: A fix for Hestia has been published
    • This reply was modified 6 months, 3 weeks ago by t-p.
    • This reply was modified 6 months, 3 weeks ago by t-p.
    • This reply was modified 6 months, 3 weeks ago by t-p.
Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘READ THIS FIRST WordPress 5.4 Master List’ is closed to new replies.