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

READ THIS FIRST WordPress 5.5 Master List

  • Moderator Marius L. J.

    (@clorith)


    2 weeks, 4 days ago

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

    So you’ve just updated to WordPress 5.5 “Eckstine” is here! But what’s this? Something broke? Or maybe you just have some questions you want to ask? This will help guide you through both troubleshooting, and common questions after the new update.

    If your site broke, 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.

    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.5 Article, and for developers, the WordPress 5.5 Field Guide.

    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.

    Still having problems after going through the troubleshooting steps below? Please feel free to ask your question here in the support forums.

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

    (@clorith)

    2 weeks, 4 days ago

    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 Twenty Twenty 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 for this release (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 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)

    2 weeks, 4 days ago

    Core Changes

    Auto-updates for plugins and themes

    With WordPress 5.5, you will now be able to easily enable automatic updates for plugins and themes (if your site is set to allow them, some hosts may handle this for you, and the option may then not be available to you).

    Although the functionality for automatic updates have existed since WordPress 3.7, there is now a way to turn them on or off with relative ease, all from within your WordPress dashboard.

    Learn more about the new auto-update feature.

    The block editor has received numerous updates

    As with any major release of WordPress in the past year, the block editor has seen many updates which are included in this release (a total of 10 releases of the Gutenberg plugin are included).

    Learn more about the changes to the block editor.

    Lazy-loading of images

    Media is an integral part of most websites these days, and as your internet browser improves, so does the technology available to improve the experience for your website visitors.

    With this release, native lazy-loading (images will not be downloaded to your visitors device until they are needed) will be available by default for any sites using the media features WordPress have made available to theme and plugin developers.

    Learn more about lazy-loading in WordPress.

    All websites now come with a sitemap

    Sitemaps, a tool often used by search engines to discover what content exists on a website, so that they can more effectively index the site, are now built into WordPress.

    Learn more about the new sitemap feature.

    jQuery Migrate is disabled by default

    jQuery Migrate, a tool which WordPress has bundled, and enabled by default, for many years, has now been turned off by default.

    This is a tool intended to help developers in a transitional period, when jQuery (a framework for writing JavaScript code) was upgraded and removed some features.

    In the time since it was created, the jQuery project has received many updates, and as WordPress prepares to make the transition to updating as well, this was a required first step to make sure plugins and themes are up to date.

    If your plugins or themes has been negatively impacted by this change, and no update is available at this time, there is a jQuery Migrate Helper plugin, which will re-enable the migration tool, and provide you with information about what plugin or theme might be misbehaving.

    Read about the roadmap for updating jQuery.

    Moderator Marius L. J.

    (@clorith)

    2 weeks, 4 days ago

    Not a bug

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

    The drag and drop interface for the block editor is missing

    In version 5.5.0 of WordPress, the drag and drop feature for blocks is still there, but it now requires you to click, and hold, on the up or down arrows, and then drag the block from there.

    A ticket to improve discoverability is available at https://github.com/WordPress/gutenberg/issues/24506

    Moderator Marius L. J.

    (@clorith)

    2 weeks, 4 days ago

    Reported bugs

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

    – Site Health flags define WP_AUTO_UPDATE_CORE value as an error https://core.trac.wordpress.org/ticket/50912#ticket
    – WordPress 5.5 update adds height and width attributes to images https://core.trac.wordpress.org/ticket/50909

    • This reply was modified 2 weeks, 4 days ago by Marius L. J..
    • This reply was modified 2 weeks, 4 days ago by t-p.
    Moderator Marius L. J.

    (@clorith)

    2 weeks, 4 days ago

    Reported plugin compatibility issues

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

    – Conflict with Schema and Structured Data For WP plugin: no longer able to edit or add tags to a post.
    – WPBakery plugin: Broken Buttons and tabs.

    • This reply was modified 2 weeks, 4 days ago by Marius L. J..
    • This reply was modified 2 weeks, 4 days ago by t-p.
    • This reply was modified 2 weeks, 4 days ago by t-p.
    • This reply was modified 2 weeks, 4 days ago by t-p.
    Moderator Marius L. J.

    (@clorith)

    2 weeks, 4 days ago

    Reported theme compatibility issues

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

    – Artisteer Theme: widgets section is not working as before

    • This reply was modified 2 weeks, 4 days ago by Marius L. J..
    • This reply was modified 2 weeks, 4 days ago by t-p.
Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘READ THIS FIRST WordPress 5.5 Master List’ is closed to new replies.

Views