Theme Options won't load

[WideBlueSound]

I can’t access Theme Options.

On my live site, I get a white screen and spinning wheel. I followed everything on this page:

Issues with Theme Options | Themeco Docs

except in order to update Cornerstone I moved everything to a staging site. Now Theme Options gives me a page titled “Nothing found for Staging Pro” and the page that loads looks exactly like a 404.

Can you take a look at the website and let me know what the issue may be?

My website is in the secure notes.

[ruenel]

Hello Nathan,

Thanks for writing in! You are using Pro theme. You do not have to update Cornerstone anymore. You can actually disable that plugin. Most of the time, the white screen with a spinning wheel means that you have exhausted your memory limit. ​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. */

And by the way, please make sure that you have the latest WordPress core of at least WordPress 5.3. If nothing is helping, provide us access to your site so that we can check your settings. Please create a secure note with the following info:
– Link to your site
– WordPress Admin username / password
​
To know how to create a secure note, please check this out: https://theme.co/apex/forum/t/how-to-get-support/288

Regards.

[WideBlueSound]

Well I already did both of those things, as mentioned in my first post.

Memory limit is 512 and I added login creds in the private note above.

I have a lot of things riding on this so I’d love to get a solution ASAP. Thanks!

[lely]

Hi Nathan,

The same credentials is not working on staging site.

I did check the issue on the live and I can confirm it.
I saw the following error:

Uncaught SyntaxError: missing ) after argument list
(index):38 Uncaught ReferenceError: _ is not defined
    at (index):38
(index):42 Uncaught ReferenceError: moment is not defined
    at (index):42
(index):133 Uncaught TypeError: Cannot read property 'editor' of undefined
    at (index):133
(index):171 Uncaught ReferenceError: tinymce is not defined
    at (index):171
cs-vendor.fa34ec9.js:3809 Uncaught TypeError: Cannot convert undefined or null to object
    at Function.keys (<anonymous>)
    at a.callback (cs-vendor.fa34ec9.js:3809)
    at a.exports (cs-vendor.fa34ec9.js:18)
    at a._reify (cs-vendor.fa34ec9.js:21)
    at a.reify (cs-vendor.fa34ec9.js:20)
    at a.exports (cs-vendor.fa34ec9.js:17)
    at a._reify (cs-vendor.fa34ec9.js:21)
    at a.reify (cs-vendor.fa34ec9.js:20)
    at a.exports (cs-vendor.fa34ec9.js:17)
    at a._reify (cs-vendor.fa34ec9.js:21)
wp-backbone.min.js?ver=5.3.2:1 Uncaught TypeError: _.pluck is not a function
    at wp.Backbone.Subviews.detach (wp-backbone.min.js?ver=5.3.2:1)
    at i.render (wp-backbone.min.js?ver=5.3.2:1)
    at i.render (media-views.min.js?ver=5.3.2:1)
    at HTMLDocument.init (media-editor.min.js?ver=5.3.2:1)
    at i (jquery.js?ver=1.12.4-wp:2)
    at Object.fireWith [as resolveWith] (jquery.js?ver=1.12.4-wp:2)
    at Function.ready (jquery.js?ver=1.12.4-wp:2)
    at HTMLDocument.J (jquery.js?ver=1.12.4-wp:2)

Those error usually exist if you do have a defer parsing code for your JS. If you do have it on your child theme or via plugin, please try to remove / disable it. See this thread.

Also, from Pro > Status page, your PHP version is 7.1.33
Please note that as a general wordrpress requirement, PHP should be at least 7.3 or greater.

Hope this helps.

[WideBlueSound]

Thanks! I had the Async JavaScript plugin enabled, which Theme Options apparently doesn’t like.

Nothing else on my website has an issue with this important plugin – is there something we can do to fix it?

Thanks

[rad]

Hi Nathan,

Any plugin that alters script loading will have an effect. It’s not that the theme options doesn’t like it, it’s just that defer and async loading implementation can break anything.

It’s the same reason why any optimization plugin should be configured correct and should be cleared/cleaned. So what you should be looking at are the features that rely on scripts, which is yes, all sites, themes, and plugins. They may break using this async plugin implementation.

Using Defer And Asynchronous For A Non-Blocking JavaScript Execution

While This Can Speed Up The Process Of Downloading A Script And Its Execution, There Is No Guarantee Which Of The Scripts Will Execute In Sequence. So If One Script Is Depending On Other Script To Run, Using The Async Method Can Break A Web Page From Working Properly.

If the script is modular and doesn’t at all rely on any other script to run as it is intended, the asynchronous will work the best. But if the script relies upon or is upon other script(s), then the defer is the solution.

And Wordpress itself is modular, it’s a platform where scripts, themes, and plugins are made by multiple authors. Hence, you have no other choice but to disable it if you prefer a working site, or configure it.

Thanks!