Hello @ExploreMars,
Sorry for the confusion. Cornerstone must be paired with the X theme version so that it will work smoothly. If you have X theme 6.5.5, please go to plugin’s section, deactivate Cornerstone and delete it. Go back to X > Validation and wait for a couple of second while the bundled version of Cornerstone is installed automatically in the background. The same goes with any other version. It is find if you do not update Cornerstone as long as the version is supported by the X theme.
Now, if you have X theme and with the right Cornerstone but still not loading, there are a few reasons why it is happening.
1.) It could be that the WordPress core is out dated or the latest. Each version of X and Cornerstone will only support two version behind. For example, X theme 7.1.0 and Cornerstone 4.1.0 supports 5.3, 5.2 and 5.1. WordPress versions later than 5.0 will give issues with the Cornerstone in loading the preview or even the Theme Options.
2.) It could also be that you have exhausted the PHP memory limit. And if this happens, we recommend that you increase your memory allocated to PHP. To increase it, please edit your wp-config.php file and insert these lines:
define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );
You can add it before the line
/*That's all, stop editing! Happy Blogging. */
3.) Sometimes, your staging dashboard URL is different from your Site URL. The must be the same as always.
4.) Improper SSL setup might also give an issue in loading the Cornerstone preview and even the X > Theme Options.
5.) A certain 3rd plugin, especially outdated ones, may also create issues and conflicts with Cornerstone. When this happens, you could try testing for a plugin conflict. You can do this by deactivating all third party plugins, and seeing if the problem remains. If it’s fixed, you’ll know a plugin caused the problem, and you can narrow down which one by reactivating them one at a time.
All of these are just guesses since we can longer access the site. We really love if we can log in and investigate further for the resolution of your issue.
Thanks.