Support Master List for WordPress 5.0

WordPress 5.0 is under preparation, and we’ve hit the Release CandidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. stage. As per usual, this means we’ll start preparing for the Master List we generally provide for every major releaseMajor Release A set of releases or versions having the same major version number may be collectively referred to as “X.Y” -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality..

For reference, you may view the WordPress 4.9 Master List (formerly known as the “OMGWTFBBQ” thread, but that term didn’t mean much to users, so we simplified it).

This time around, the releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. has one focus, which makes things a bit more streamlined for our sake. We’ll include the default stuff we always do, but with some added emphasis on JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. debugging, as this the new editing experience relies heavily on that.

Notable exclusions is the 2nd reply, noting “CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. changes”, as the release is all about one feature this isn’t needed. We also need to go over the links once the new user documentation is launched properly, as better documents than the Codex pages will exist at that point.

We’ll retain the other sections as they are today, there’s not much we need to change there, so this will be to field input on the first reply which focuses on troubleshooting. Let’s focus it a bit and expand the JavaScript section.


The Troubleshooting Section

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.
  • 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.
  • 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 pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party(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 Sixteen 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 twentysixteen. That will force your site to use it.
  • Manually upgrading. When all else fails, download a fresh copy of the latest.zip file of 4.9 (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, consider getting the Health Check plugin to provide debug data for the support volunteers.