Troubleshooting site issues after a WordPress update


  • Applies to: Grid
    • Difficulty: Easy
    • Time Needed: 10-20 minutes
    • Tools Required: WordPress Admin access, FTP access, or SSH access
  • Applies to: DV
    • Difficulty: Easy
    • Time Needed: 10-20 minutes
    • Tools Required: WordPress Admin access, FTP access, or SSH access
  • Applies to: Managed WordPress
    • Difficulty: Easy
    • Time Needed: 10-20 minutes
    • Tools Required: WordPress Admin access, FTP access, or SSH access

Overview

On December 6th, 2018 WordPress released version 5.0. One of the most notable updates done with this version is in the visual editor which has been named "Gutenberg." For a large portion of sites, the Gutenberg update should not affect the "front-end" of your site that your customers/clients/viewers see. But should only be noticed on the "back-end" of the WordPress Admin Dashboard.

However, as with any update, there is the possibility that certain portions of a WordPress site may begin to experience issues after an update is performed. This article guide was created to provide you with some troubleshooting solutions with this recent WordPress update.

However, please keep in mind that troubleshooting the configuration/functionality of third-party applications is not covered by our statement of support. The troubleshooting of a WordPress sites is best handled by the developer who created the site. However these resources were provided as a courtesy to assist you to the extent of our abilities. For more information on our statement of support, feel free to click here.

Before Starting

To complete some of these troubleshooting steps you will need access to ONE of the following:

Instructions

Disabling Gutenberg

If you wish to revert to the Classic Editor, WordPress has provided a plugin for this option at https://wordpress.org/plugins/classic-editor/

Updating all third-party applications

Update all plugins and themes to their latest versions. This can be done through the wp-admin dashboard or manually through FTP.

Clearing Caches

You can clear your browsers cache, or try opening a different web browser (Chrome, Firefox, Safari, etc) to see if there's caching on the browser level.

Certain plugins or other third-party applications may also have caching capabilities so you may want to ensure those are cleared as well.

The Managed WordPress Servers also have a cache which can be disabled by following the instructions here.

Re-saving your Permalink settings

  1. Click on Settings. Then click on Permalinks.
  2. Click on the Save Changes button.

This should help reset parts of the site (such as the .htaccess) which may be causing issues.

Disabling plugins

It is recommended to disable ALL the plugins at once, then check if the issue is resolved. If disabling all the plugins does resolve the issue, they can be re-enabled one at a time to narrow down the potential culprit(s).

If you are not able to disable the plugins through wp-admin, they can be disabled using SFTP/FTP or SSH by renaming the /plugins folder.

Changing theme

Switching to a WordPress theme (such as Twenty Nineteen) can help determine if there is a theme related issues.

If wp-admin is not accessible, the theme can be changed by updating the template/stylesheet in the database, or through FTP/SSH by renaming all the theme folders except Twenty Nineteen.

Manual WordPress Upgrade

This applies particularly to sites that were updated automatically through a "1-click method". The  upgrade can be re-done manually using FTP or SSH.

If you require a refresher on updating a WordPress, feel free to view our additional article here.

Restore using a backup

If you have a copy/backup of your site prior to updating to WordPress 5.0+, you can attempt to roll back your site temporarily (as it is recommended to maintain your websites on the latest version of WordPress).

For Grid Personal, Pro, or Elite, you can restore from a backup using the 30-day File Manager backups.

Legacy Grid users, such as the (gs) Grid Service or Grid Lite will not have this option, and will have needed to manually created a backup prior to performing the WordPress update.

For the DV/VPS servers it would be necessary to have manually created a backup of the website prior to the WordPress update.

However, in the event that you do not have a manually created backup, you can check with our support agents to see if there is a backup available through our paid Emergency Restore Service.

The Managed WordPress servers are equipped with 30-days of backups which can be restored through the Account Center. If you require a refresher on how you to locate and use these backups, feel free to click here.