- This topic has 1 reply, 2 voices, and was last updated 1 year, 11 months ago by
.
-
Posts
-
Good morning Support,
Wasn’t the Grimlock upgraded by any chance lately? Is it possible to get the previous version of Grimlock?
I have read the previous topic on it and it’s not about Kirki (I tried the previous version out, I mean Kirki 4.0.24) and removed cache from the brower, so it had a chance to show me the new site if it’s fixed).Generally speaking Customise doesn’t load, it’s stuck on ‘Customize: Loading…’. When it turn off the Grimlock plugin, it works fine. The very significant thing is that it WAS working recently and suddenly stopped. I’m experiencing the same problem on both externally hosted ‘production’ and on a local WordPress environment hosted on XAMPP.
I tried everything both on the current, latest versions of both wordpress and the relevant plugins, as well as on their older counterparts (one-two versions back). I can’t get too deep into historical plugins, because there is a security issue at stake.
Please, provide me with an earlier version of Grimlock (if there has been an update recently – I suspect this scenario, because I didn’t have such a problem before and it appeared suddenly), I’ll try and if I still have a problem, I’ll just run WordPress debugging in wp -config.php and I’ll provide you with the logs, because maybe it’s really just a matter of this one thing. As I said – taking an earlier version of Kirki (which was last updated over 2 months ago anyway – and the problem appeared maybe a week ago) did not bring any result.
Yours faithfully,
Ernest Platos
Hi Ernest,
Thank you for reaching out. Please note that we released a new update of Grimlock in December.
To help us getting clues and find a solution to this issue, please activate logging on your website, just turn WP_DEBUG to true, by pasting the following code lines in your wp-config.php file, just before the line that says ‘That’s all, stop editing! Happy blogging.’:
// Enable WP_DEBUG mode define( 'WP_DEBUG', true ); // Enable Debug logging to the /wp-content/debug.log file define( 'WP_DEBUG_LOG', true ); // Disable display of errors and warnings define( 'WP_DEBUG_DISPLAY', false ); @ini_set( 'display_errors', 0 );More on this in the following topic: Debugging in WordPress.
Thank you.
Hi there,
This topic has been inactive for a while now so we will be closing it to keep the forum tidy. Don't hesitate to create a new topic if you still need help and we'll be glad to help you!
Best regards,
The Themosaurus team.
The topic ‘Customise does not work’ is closed to new replies.
