SOLVED: After adding custom class and saving, save button reverts to unsaved state

Bugs
1
  1. Add a custom class to a section
  2. Click save button
  3. Click on empty are in structure panel

The save button reverts back to unsaved state.

This also happens in step 3 when view on frontned button is clicked. If I go back and look at the buider, the save button has reverted to unsaved state.

See video: Jam

2

Hi @macksix,

thank you so much for your report and the video. I was able to replicate it and I’ve added it to our internal bug tracker.

Thank you,
Matej

3

Hi,

I’m not sure it is the same, but something similar is haunting me lately - it seems to happen on more than one site. The unsaved dot appears, sometimes with a message that all the classes were deleted and added, and after saving and refreshing the page, the dot re-appears.

I was sure that it had to do with some changes I did yesterday, so basically got rid of all of them, only to find out later (stupid me for not checking before), that a previous version also has this.

Bricks version 2.0.2

bricks
bricks617Ă—540 22.5 KB

4

Hi @chanart,

this is weird. When does this appear and can you replicate it?

Matej

5

It appears after random saves. Regardless if anything was changed in the CSS or not. Actually regardless if there have been any changes at all. As I noted, the saving dot is always there after each refresh of any template or page.

6

Can you try to disable auto-save? Just in case, if it’s that. Also, how often that this happen?

7

Auto-save I always keep disabled. And I’d say it happens several times a day (the strange classes deleted/added notifications)

8

Next time you see this, try to undo the last action and try to replicate the issue. If you manage to do it, please let me know.
Sadly, without me being able to replicate it, there is not much I can do :face_with_diagonal_mouth:

Best regards,
Matej

9

Matej hi,
The thing is, it happens regardless of whether some changes were made or not. I think always when there are more then one tab open.
What about the other thing - the constantly appearing unsaved dot?

10

The other thing—the consistently appearing unsaved dot will be fixed in the next release. I was just testing it internally. :slight_smile:

This might be the clue. More than one tab of the same page? In the same browser?

Do you have “sync global classes” enabled?

11

Good about the “other thing” :slight_smile:
“Sync global classes” is enabled. Same browser,not same page.

12

Ok, thanks for this info. The “Sync global classes” is still in experimental phase, and it might be the reason for that. Can you try to disable it for a day, and let me know if it’s still happening? We can narrow it down that way, because I’ve tested, but could not replicate it now :frowning:

Matej

SOLVED: Save error [object Object] when trying to save
13

Indeed seems to be ok now, when the “sync global classes” is disabled. Good catch.

14

Thank you, @chanart, for this feedback. In this case, I’ll ask a colleague who was working on this feature, if he knows why this could happen.
If there is anything new, I’ll let you know. :v:

Thank you so much,
Matej

15

We fixed this issue in Bricks 2.1, now available as a one-click update in your WordPress Dashboard.

Please take your time to read the changelog entry before updating: Bricks 2.1 Changelog – Bricks + Bricks 2.1-beta Changelog – Bricks, and let us know if you continue to experience issues.