Several users shared concerns about relying exclusively on localStorage for saving builder UX settings. I may have been a bit overexcited about the benefits, like reducing database load and offering a snappier, more “live” experience, without fully considering edge cases. For example, some users constantly clear their browser cache, while others need to enforce consistent…

You can now export/import/reset all the data related to the UX builder that has been saved to the database.

A new option in the Reset Settings allows you to remove all the Local Storage related to AT.

Visibility Floating bar could show wrong settings when hide/remove settings were set to false in the element object.

That error could be triggered when installing AT for the first time, before saving the Theme Settings.

In case you connected an element to a missing component, a JS error would be triggered and break some functions of AT inside the builder.