DO NOT update to 3+

We are testing the plugin and preparing a lot of migrations. The plugin has been upgraded and works on all our sites. We have an alert in the changelog about the major update of v3 – https://www.ads-software.com/plugins/ghostkit/#developers, and you have to test it on staging first to check for possible bugs. But who cares, right?

There are some specific cases that are not working correctly with the latest plugin update. Furthermore, there are some issues with the latest Gutenberg changes, which have not yet been fixed.

And you, instead of ruining the plugin rating, can help fix it. But you don’t care and prefer not to do anything and ruin the plugin, like these other users who don’t even want to reply…

• https://www.ads-software.com/support/topic/reveal-animation-not-working-anymore/
• https://www.ads-software.com/support/topic/upgrade-breaks/

We have some paid users who found bugs, such as not saving changes of paddings and margins, and we will fix it in the next plugin update, but free users who don’t care don’t provide any helpful info. Instead, you are ruining the plugin rating. Good job.

Well, then obviously you didn’t test it properly…

I maintain hundreds of websites and thanks god only a few tens have installed Ghostkit and now I need to go through each one, downgrade plugin, disable updates and fix all broken pages in all languages and set margins and paddings for each element… and you are telling me that I’m ruining?something? ?? I need to spend long hours with fixing what your updated caused…

Do not lie please, you will not fix anything in next update, because all spacing data are deleted after you update any page/post with Ghostkit v3+… there is no way to restore this, sometimes not even with revisions…

Contact me and tell me what is happening with your business because of our plugin update. I will make a hotfix together with your help (at least tell me how to reproduce this problem locally, provide testing info or something).

The problem with margins/padding is somehow related to the Group block. In some installations, it works as expected (in all our sites and most user’s sites). In some cases, it stops working only with the installed Gutenberg plugin because they are changing many things every time, and we have to test and fix compatibility. In some cases, like yours, it stops working even without the Gutenberg plugin (right?). And I never get a reproduction guide for your case.

You are right. If you have this bug and click Publish, the page will be published without paddings and margins. This is a strange conflict, and you can check it – add margin/padding, click Publish – everything will be fine in the editor and on the front end. Then reload the editor; no margin/padding will be available on blocks, but it is still there on the front end. If you don’t click on Publish, it will be fixed with the next Ghost Kit update.

If you see this bug and use Gutenberg, we know about it. This is something related to their latest changes. They broke all our plugins with it, and we will fix it. But if you don’t use Gutenberg, provide me some info so I can reproduce it…

Sure, but firstly i need to fix all these websites, because I have a lot of emails and calls from clients, so right now I don’t have time to help you with this, but as soon as I will have some time I’ll provide you with more info.

As I wrote, you will be not able to fix this with any update, because spacing data are completely gone once you update page / post with Ghostkit v3+, but at least I don’t need to fix all the pages everywhere, but just these that were updated after GK3+ update. Right now I’ve spent 3-4 hours fixing things and I’m at 50% done (hopefully).

No I don’t use Gutenberg plugin and actually no one should do that on live website as it is just some testing / early access plugin.

Yes, it’s the usecase like you wrote, but unfortunately clients are updating their content by themselves and often they press Publish and check website after each small change, so there is nothing I can do… right now I’ve stopped them, but it’s already too late and there is too much broken things now.

Hi,

Please check the latest plugin update. There was a conflict between old deprecated block transformations and our custom attributes for extensions. Now everything works correctly.

Regards,
Nikita.