Anthony Ledesma

Hi @machepap,

I accidentally responded here from another thread. Sorry about any confusion with that.

Concerning the Carousel block bug that you are reporting, we are attempting to test it out and see if we can find a way to replicate and then resolve the issue. I did have a question for you on that, you mentioned a custom theme, Is this one that we could download and use? Or is it something that was custom-built/ not available publicly? What version of WordPress are you running, also?

Best,

• This reply was modified 1 year, 7 months ago by Anthony Ledesma. Reason: Replied with incorrect post test

Hi @ewd910,

Okay, that is good to hear about the configuration thank you for the clarification. We spotted a condition in the code that may have caused the issue you were seeing. Do you mind updating to the latest version of CoBlocks to test the issue again? We suspect the 3.1.2 version could resolve your issue.

Best,

Hi @webmandesign,

CoBlocks Version 3.1.2 has been released which resolves the issue with the shape divider block. Thank you for reporting this to us! We have also added a test to prevent an event like this from occurring in the future.

Best regards,

Anthony

@ewd910,

I realize also that you may have added additional blocks to your form. Can you identify all the blocks in the form for us please? A screenshot would really help also if you can provide.

Hi @ewd910,

Are you able to provide additional information regarding the Form error you posted earlier today? We have had a few of our engineers attempt to replicate this error without success. Any extra information like debug logs, or other plugins for example I would greatly appreciate.

Best,

Hi @ewd910,

That is not good to hear! We have the Form block tested with the latest version of WP as well as PHP 8.1 so I am very surprised to hear about this. I will take a look and see if I can track down why that is happening on the plugin side of things.

Best,

@ispheare CoBlocks version 3.1.1 is now released. The hotfix updates the supported version. That should resolve the issue of incompatible distribution with previous WordPress versions. Thanks again for the contribution and for taking the time to make this thread and provide information.

Best,

Anthony

Hi @ispheare,

Thank you for bringing the backward compatibility issue to our attention. It has become clear to us that we have not been updating the minimum supported WordPress version as required. We will be pushing out a patch release of CoBlocks that updates the minimum supported version to 6.2.

Unfortunately, CoBlocks has changed to the point where further backward compatibility will not be feasible. If continued backward compatibility is required, you may need to run older versions of CoBlocks.

Best regards,

Anthony

Hi @askwpgirl,

Glad to hear the issue was resolved with the patch version. Indeed the changes really had nothing to do with loading of assets but rather was a bug relating ‘the loop’ around posts. Pretty strange indeed. Hopefully we never see this issue again.

Best,
Anthony

Hi @askwpgirl,

You are correct that specifically altering a plugin’s load order is not an acceptable practice. That would, for instance, likely cause issues with CoBlocks if another plugin were to alter our load order purposefully. I can tell you there are zero intentional changes that might affect the plugin load order. For that reason looking for something that explicitly changes load order would be dead-end I can say that as a developer of CoBlocks. However, I believe that something somewhere is affecting the load order. Possibly a side-effect, a bug, something that should not be happening. I think it may even be a core bug that we have inadvertently raised somehow by using a public API.

At this point, we just do not know yet what is happening. If anything let me tell you that our team is aware of the issue and we are looking to understand why that is happening to you. If we can work with Elementor to find a solution, even better.

Best regards,

Anthony

Hi @askwpgirl,

Thanks again for taking the time to write up this issue. We are still not sure what is causing this behavior and are still working on it. I’ve taken the liberty to re-create this issue on GitHub for our development team and possibly the Elementor development team to collaborate. For your reference here is the issue I created based on your report: https://github.com/godaddy-wordpress/coblocks/issues/2517

Best regards,
Anthony

Thanks all for the rapid reports. CoBlocks had a bug with the release process leading to this version with the errors you reported. Being a critical error as it makes fixing it a matter of reverting sadly. We wound up reverting to version 2.25.5 and removing the 3.0.0 release.

If any of you has not yet reverted, the fix for this will be to revert to version 2.25.5.

Thanks again to all who reported this and sorry for any inconvenience.

Hi @daveporter,

Thanks for pointing this out. It is something that is a bit strange for sure. We will work on getting that list sorted out with proper block names.

Best,

Anthony

Hi @drewe2000,

Sorry for the delay in getting back to you on this. We have identified an unexpected style conflict that was previously introduced and removed in CoBlocks version 2.22.6. Would you mind giving that a test and seeing if it resolves the issue?

Best,

Anthony

Hi @jtank2,

Sorry for the delay in getting back to you on this. We have identified an unexpected style conflict that was previously introduced and removed in CoBlocks version 2.22.6. Would you mind giving that a test and seeing if it resolves the issue?

Best,

Anthony