Benjamin Intal

Hello @castlelandcommunitycentre thanks for the report. Kindly update to v3.11.3, it should fix the issue.

Hey @viche the issue reported by the original poster was an issue of the premium version of Stackable. So if you are using the free plugin, then you should be okay.

If you are a premium user, you can log in our website https://wpstackable.com/account/ and you’ll be able to see the websites where you have Stackable activated.

Hey @banijadev we’ve been adding performance improvements and we were able to shave off some memory usage as you can see here: https://wphive.com/plugins/stackable-ultimate-gutenberg-blocks/?plugin_version=3.11.0

It may still show an ? but this is because of how memory scoring is computed in WPHive.. whether a plugin is memory friendly or not is computed against all the other plugins in the Plugin Directory, and because I would assume that the vast majority of plugins are smaller plugins, then Stackable’s score gets skewed to showing as being not friendly. Most of our memory overhead is introduced because of registering blocks inside Gutenberg.

I’m marking this thread as resolved. But rest assured, we will be continuing to make things more memory efficient.

Hello, thanks for providing a workaround for the issue. I’m happy to report that this has already been fixed in v3.11.1 (premium)

This issue also only happens in the premium version of the plugin and only in some scenarios. I’m resolving this for now, please let me know if you need any more help!

It looks like the solution we provided may have resolved your issue, as we haven’t received any further updates from you. If you require more help, please don’t hesitate to reach out. Have a great day!

The error is pretty bad and leaves you clueless as to how to set things up, and had to resort to checking this forum for an answer. Unfortunately, going incognito in Brave did not solve this for me, but using Safari worked and let me continue on with the rest of the setup.

Hello @douglsmith , apologies for this. What you encountered was a very unfortunate bug that we have fixed months ago.

We’ve added a pinned thread on it here that includes how to update: https://www.ads-software.com/support/topic/update-issue-asking-to-buy-premium-read-this/

Here are the steps enumerated there:

To update, follow these steps:
1. Navigate to Plugins > Add New
2. Search for “Stackable”
3. Click on “Update Now”

Alternatively, you can deactivate Stackable plugin, then update it. Or you can manually update Stackable by downloading the v3.1.5 plugin zip file and uploading it into your site.

I 100% agree with you that the update list is not the place for any promotional stuff, and it is not my intention to add any promotional things in there. Unfortunately, we had a painful bug that showed the premium warning for free users. While we have addressed this quickly months ago, we are still sometimes seeing the effects of this.

Thank you! These should be okay now in v3.6.4 (we had to adjust some things though to be compatible with lower PHP versions)

Hey @illycz @vadikcoma @jessekoomen @igor4wp @youyal @deanoakley, actually, since my last reply there has been 2 speed improvement updates that have been released.

There’s another speed improvement update that is currently undergoing testing, this one should make things faster. We’re aiming for its release in a week or two from now.

My previous suggestions still hold though, try and lessen Block nesting and make use of block backgrounds and containers. Doing those should make thee editor faster.

Please update to v3.3.3, this should be okay now

Hello, would you be able to send over your page content so we can try it out? We want to see the scenario for the slowdown. Please click on the 3-dots button on the upper right of the post editor, then click on “Copy all content”, then please upload it to PasteBin, then email the link to us at [email protected] .

Based on experience, it’s possible that when the page is really long, especially if you use a lot of columns and nested blocks, it can be slow even with just the native blocks. Lessening the amount of levels of nested columns can drastically improve the editor performance. Two easy ways you can reduce the need to nest multiple columns inside each other is by utilizing the block’s background setting (under the block tab in the inspcector), or a column block’s container setting (under the style tab).

Also, are you using a lot of Stackable columns in the page? Because if you do and then you disable Stackable, that might make it look like it improves the editor performance, but probably because it also stopped the nesting of a lot of blocks because the columns have also been disabled.

• This reply was modified 2 years, 6 months ago by Benjamin Intal.

Thanks for the report! We’ll be releasing a fix for this today or tomorrow.

Hello, Stackable does not generate any WooCommerce stuff. It’s possible that those are from another plugin.

To remove all the Stackable options that were left behind, you can remove all the rows in your wp_options table that have an option_name that starts with stackable_

Hi Jeremi @stridecreative, yes there was an unfortunate issue with v3.1.4, the free plugin will always have free updates. Please see this thread: https://www.ads-software.com/support/topic/update-issue-asking-to-buy-premium-read-this/

To update, follow these steps:
1. Navigate to Plugins > Add New
2. Search for “Stackable”
3. Click on “Update Now”

Thanks for the great suggestion! Speed is always important. Already implemented this in our codebase and it will be included in the next update release in a week or two ??