Issues after X 6.3 and Cornerstone 3.3 Upgrade

Hello,

I just updated my site to the latest versions of Cornerstone and X theme and am now having multiple issues. The most significant issue is:

  • unable to access any of the subsections of the customizer (https://blog2.turbosquid.com/x/#/options for example shows the loading twiddle indefinitely) or save changes like fonts in the settings there (“Uh oh! Could not save Fonts.” for example). The console shows warnings saying “Rejecting AJAX promise {invalid_user: true, message: “nonce verification failed.”}”. I am indeed logged in.

There are other smaller issues that probably stem from the same source but that’s the most significant. Those include fonts failing to load, no htaccess file is created by switching permalink structures, etc.

I’ve tried:

  • Cleared style cache in X Settings
  • Disabling all plugins
  • Disabling child theme
  • Turning on debugging (nothing showing up the the logs)
  • Increasing the memory limit
  • Revieweing changelog

I’ve reactivated the plugins and switched back to the child theme for the moment. My site has a different siteurl and homeurls and there are redirects in place to orient users to the homeurl but the wp install is available at https://blog2.turbosquid.com/resources/. Any suggestions would be greatly appreciated.

Kind regards

Hey @sbintliff,

Regretfully, this is honestly quite tricky to replicate because this is not a standard setup. Can you try the items in the list below too:

Hey there,

Please check for the following first:

  1. Ensure everything is up to date according to our version compatibility list at https://theme.co/apex/forum/t/troubleshooting-version-compatibility/195. Please follow the best practices when updating your theme and plugins. See https://theme.co/apex/forum/t/setup-updating-your-themes-and-plugins/62 for more details.

  2. If you’re using a caching plugin, clear all caches including browser cache then deactivate your caching plugin and other optimization plugins.

  3. If you’re using a CDN, please clear the CDN’s cache and disable optimization services.

  4. Reset your htaccess file by renaming it to .htaccess-bak. Then in WP Admin Menu, go to Settings > Permalinks and just click the Save Changes button.

If nothing helps, please copy your site over to a staging server first so we could troubleshoot without disrupting your live site’s operation. Also give us the staging’s WordPress Admin and FTP access.

Thanks.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.