Hi there,
Thanks for posting in.
We don’t have direct control over bundled plugin’s development, and we could only forward the bugs we can find. I’m not sure what issue you’re having with Essential Grid, would you mind providing a video recording? I can add that to our issue tracker for further checking.
Or is it just related to skin layers (excerpt) as you said? Then it’s probably not a bug but configuration related. And how did you move your staging to live? That process could cause issues as well.
I checked the grid in the builder and I can confirm the issue, but it’s not because of the theme or updates. Plus, this works okay on my installations, so if it’s update related then I should get the same issue as well. In your case, it’s because of this error Uncaught ReferenceError: ajaxurl is not defined
and it’s not theme related. And about the header and footer, make sure to use a template that has header and footer, your blog page template uses a No Footer
template.
I also created a draft page here and added the shortcode https://umbertofederico.de/?page_id=16163 but it’s blank which means, it’s an internal server error.
Let’s do this,
-
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.
-
Clear all caches including browser cache then deactivate your caching plugins and other optimization plugins.
-
If you’re using a CDN, please clear the CDN’s cache and disable optimization services.
-
Test 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.
-
Remove custom CSS, Javascript and templates.
-
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.
-
Contact your host to increase your allocated memory or do it yourself by adding this code to your wp-config.php
define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );
If the issue persists, then what’s left to do is get the details of the error and before we move forward. Please edit your site’s wp-config.php
and replace this line define('WP_DEBUG', false);
with these new lines
define('WP_DEBUG', true);
define('WP_DEBUG_DISPLAY', false);
define('WP_DEBUG_LOG', true);
Then test your blog page in the builder and in the live, please test the draft page the same way too. Then provide the debug.log
file’s content in your reply. You can find that file under /wp-content/
folder and you may use your hosting’s file manager or FTP to do that.
About the updates, we always recommend doing maintenance, major updates, and even redesign in a staging site(cloned from the stable site). It’s common practice in web development. Any major updates contain more features and maybe different structures than the previous versions. And it’s normal since it’s major update, a different one from a previous stable version. We have to release updates for users starting from scratch or for users who wish to test it first. For existing and stable site, it’s not recommended to jump right into the big changes without testing it.
And for unseen issues upon updates, we will try to find some workaround, or at least add them to our issue tracker to inform our developers. Pro has known issues with translations even from its first version, it’s known issues which a bit complex, and the updates only contains partial fixes especially for WPML, but yes, still buggy (given that there are many kinds of translation plugins) and our developer are still in the process of improving them
As for unchecked issues, the updates for cornerstone/X/Pro overlaps with the updates of the bundled plugin which breaks the integration between them, it’s when the plugin’s author decided to change the naming of their internal codes/classes. And its slipped since it passed our first set of tests, but I agree that we should strictly check it more often.
Thanks for understanding.