Tagged: x
-
AuthorPosts
-
November 11, 2016 at 2:14 pm #1253693
Blair WParticipantBeen trying to figure out why I have been having so many problems with Cornerstone Loading, Pages not loading just for editing (takes 3 or more refresshes) and the refusal of Essential Grid Editor to load at all (getting out of memory error).
Tracked it down to Essential Grid and WooCommerce Subscriptions plugins.
The site and the plugins are all recently updated to latest versions (that’s when I noticed the problem).
November 11, 2016 at 2:23 pm #1253700
Blair WParticipantThis reply has been marked as private.November 11, 2016 at 2:35 pm #1253709
Blair WParticipantLooks like I know have to turn off all of my Woocommerce plugins to work with Essential Grid.
November 11, 2016 at 8:25 pm #1254110
Rue NelModeratorHello There,
Thanks for writing in! What you have been experiencing is the PHP memory limit exhaustion. By default, WordPress will attempt to increase memory allocated to PHP to 40MB (code is at the beginning of /wp-includes/default-constants.php) for single site and 64MB for multisite, so the setting in wp-config.php should reflect something higher than 40MB or 64MB depending on your setup. I see that you have 100MB WP Memory Limit (WooCommerce > System Status) and this isn’t enough. 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. */We would loved to know if this has work for you. Thank you.
November 12, 2016 at 12:03 pm #1254529
Blair WParticipantCornerstone loads without any fuss now but I still have to deactivate all the woocommerce plugins to access the essential grid editor.
November 12, 2016 at 7:15 pm #1254838
Rue NelModeratorHello There,
Thanks for the updates! I have tried in my local testing server and I could replicate an issue or conflict between Essential Grid and WooCommerce. I have tested in your site and I can confirm that you cannot create a grid or edit a grid. This may have been caused by a WooCommerce extension or another 3rd party plugin.
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.Please let us know how it goes.
November 14, 2016 at 2:07 pm #1256896
Blair WParticipantIt would seem that Gravity Forms is the culprit.
November 14, 2016 at 6:09 pm #1257155
JadeModeratorHI Blair,
Glad to hear you were able to get it work.
Cheers!
November 15, 2016 at 11:33 am #1258222
Blair WParticipantSooooo, am I supposed to not use GF anymore? That impacts my future plans for extending out woocommerce product choices.
November 15, 2016 at 11:33 am #1258223
Blair WParticipantSooooo, am I supposed to not use GF anymore? That impacts my future plans for extending out woocommerce product choices.
Whoops, double post. Had an issue on my end with the browser.
November 15, 2016 at 12:07 pm #1258279
RahulModeratorHey There,
Thanks for writing in!
Kindly walk-through the guidelines given in the link here :
https://theme4press.com/fixing-wordpress-plugin-conflict-errors/
Hope this helps!
November 15, 2016 at 12:59 pm #1258351
Blair WParticipantI’m aware of all this information.
November 16, 2016 at 2:42 am #1259083
ChristianModeratorHey Blair,
We’re sorry but we currently don’t have an immediate solution to this and we can’t guarantee a fix in plugin conflict cases. Please stay tuned for plugin updates.
Thank you for understanding.
November 16, 2016 at 3:12 pm #1259900
Blair WParticipantNo worries, I am digging through GF fact/info looking for a solution there as well.
November 16, 2016 at 5:03 pm #1260075
FriechModeratorThank you for understanding, please feel free to get in touch with us regarding any further queries about the X|Theme and Cornerstone.
Cheers!
-
AuthorPosts
- <script> jQuery(function($){ $("#no-reply-1253693 .bbp-template-notice, .bbp-no-topic .bbp-template-notice").removeClass('bbp-template-notice'); }); </script>
