sujaypawar

@amybabyreview + @tamfit:

Have you guys tried rolling back to the previous version until we identify issues and release fixes for them?

Spectra offers a one-click, roll-back functionality as explained here: https://wpspectra.com/docs/rollback-spectra-version/

Hi @queenielow

The file UAGBIcon.json is no more present in the latest version of the plugin.

Hi @ukandrzej

Thank you for the suggestion. Did you read the latest changelog where we decided not to “deprecate” some blocks but just call them “legacy”?

Here is part of the changelog of the last release:

* Decision: Instead of deprecating some blocks, we decided to call them “legacy” blocks. Legacy blocks work fine and will get support/bug fixes.
* Improvement: Removed deprecation notices from the settings of the blocks.

I think this should resolve your concern, and you would not need a separate plugin as old blocks will be maintained.

Rest of the changelog:

* Improvement: Added a setting to set default values for “column gap” & “row gap” in the container.
* Fix: Advance Columns – Full-width layout not getting full width on the frontend.
* Fix: Padding in some blocks were not visible in the editor for old user.
* Fix: Post Grid – Content padding getting applied to post image.
* Fix: Icon List – Fixed word wrapping and breaking behavior.
* Fix: Info Box, Heading, Call to Action – overridden text color on frontend when used in the Cover Block.
* Fix: Post Carousel, Grid, and Masonry – Disabled ‘Read More’ links in the editor and ensured pointer is shown on button hover.
* Fix: Post layout – Title color turns white when background image position is set.

This should fix most of the issues people faced after updating.

1. After updating, please be sure to regenerate the assets. We do this automatically after the plugin is updated, but just to be sure, go to “Spectra > Settings > Asset Generation > Regenerate Assets” and press the button.

2. Do you see the Advanced Column block layout was not as full width as it was in the 1.x.x release? We noticed this problem only by people who updated to the 2.0.x version and changed the page content. To fix this, please update the plugin’s latest version, go to the edit page/post screen, refresh the editor, and click the update button.

If you still see any issues, please contact our support team on our website and let us know. We need your help to debug if there are still any other problems left so that we can fix them.

Hey @ukandrzej:

This is strange. Perhaps, your host might be updating the plugin to the latest version?

I can confirm our plugin does not have any functionality or code related to automatic backups.

Hello @hubcomco

Version 2.0 is a massive release. We’re sad that this update has caused you issues.

Our team worked hard, tried its best to make it a smooth transition from prior versions to 2.0, and ran an extensive public beta testing program for several weeks.

However, it seems we could not test all these possibilities. We’re so sorry for the trouble.

Our development team has identified a few issues that were reported by users like yourself. They are actively working on fixing them, and an update will be released in just a few hours.

Please feel free to get in touch with our support team if you need any help. Rest assured, we are working hard to get the issues fixed and release an update ASAP.

Hey @mbitswebcontent

Thank you for sharing your opinion about the blocks we deprecated in the 2.0 release.

The community has shared their concerns, so we’re internally discussing this. We will find a solution, and an update will be released in just a few hours.

1. By the way — deprecated blocks do not mean they will stop working altogether. They will continue to work, and we will even offer support for them and release fixes. We only want to encourage people to use the newer and better blocks instead of the legacy ones.

2. If you faced any issues after the update, could you please get in touch with our support team? If you already have — rest assured we will work with you and fix the issues you are facing.

Again, thank you for sharing your concerns. We’re listening!

Hey @cschallo,

We’re sad that this update has caused you issues.

Our team worked hard, tried its best to make it a smooth transition from prior versions to 2.0, and ran an extensive public beta testing program for several weeks.

However, it seems we could not test all these possibilities. We’re so sorry for the trouble.

If you get in touch with our support team (or if you already have) — rest assured we will work with you and fix the issues you are facing.

@staartmees – thank you for sharing your opinion and concerns about the blocks we deprecated in the 2.0 release.

The community has clearly shared their concerns, so we’re internally discussing this. We will find a solution, and an update will be released in just a few hours.

By the way — deprecated blocks do not mean they will stop working altogether. They will continue to work, and we will even offer support for them and release fixes. We only want to encourage people to use the newer and better blocks instead of the legacy ones.

Again, thank you for sharing your concerns. We’re listening.

We’re sad that this update has caused you issues. Version 2.0 is a major release.

Our team worked hard, tried its best to make it a smooth transition from prior versions to 2.0, and ran an extensive public beta testing program for several weeks.

However, it seems we could not test all these possibilities. We’re so sorry for the trouble.

If you get in touch with our support team (or if you already have) — rest assured we will work with you and fix the issues you are facing.

We’re sad that this update has caused you issues.

Our team worked hard, tried its best to make it a smooth transition from prior versions to 2.0, and ran an extensive public beta testing program for several weeks.

However, it seems we could not test all these possibilities. We’re so sorry for the trouble.

If you get in touch with our support team (or if you already have) — rest assured we will work with you and fix the issues you are facing.

Hey guys,

I just wanted to share an update:

1. We have identified and fixed some issues in the Advance Columns, Icon List, FAQ, Post & Table of Content Blocks. Our developers have already fixed them, and our QA team is testing them. A new version will be released in a few hours.

2. We hear your sentiments about the “deprecated” blocks. We’re discussing this internally and find out a solution.

Thank you for all the feedback. And once again, we’re sad that this update has caused you issues.

Our team worked hard, tried its best to make it a smooth transition from prior versions to 2.0, and ran an extensive public beta testing program for several weeks. However, it seems we could not test all these possibilities. We’re so sorry for the trouble.

Thanks for the details @evit

We will see if we’re able to replicate it. Thank you for taking time to report this.

Hey guys,

I just wanted to say; that we’re sad that this update has caused you issues.

Our team worked hard, tried its best to make it a smooth transition from prior versions to 2.0, and ran an extensive public beta testing program for several weeks.

However, it seems we could not test all these possibilities. We’re so sorry for the trouble.

If you guys could help us understand the problems and provide steps to replicate them with some screenshots or videos, we would really appreciate it.

Hello @evit

The problem you’re describing is not yet on our list of “known issues.”

Could you please share more details about where you saw these 405 errors? More information on how we can replicate this will be really helpful.

@sterndata

I understand and thank you for volunteering and keeping the forums clean ??