WIP: Save error [object Object] when trying to save in 1.11 beta

Bugs
22

Yep.
I don’t see a full response from the code that you pasted, but from what I see, it looks like it’s the same issue that we already have a bug report :slight_smile:

–
Matej

23

OK, time for a new update.

After disabling the “Sync global classes” option issue disappeared.

At the request of @Matej I re-enabled the “Sync global classes” option to try and capture the request response and it started to get interesting.

The error still occurs but behavior is different.
First, error happens a lot less. Like 10 times less. Maybe once every 3 to 4 hours.
Second, before I could not save the template no matter what after the error occurred for the first time. It simply would not save. Now I can hit the save button a second time and it will always work.
Error just disappears and works properly. Which means capturing the problematic response is very difficult unless one keeps the dev tools open and waits for the error or puts a proxy in the middle to record all requests.

Another piece for the puzzle: today I received a 429 error for the first time. Which leads me to believe that maybe this is an input queue / request order / concurrency problem, something along those lines.

Makes me remember the fun I had debugging C/C++ code only for the error to disappear when the debugger was attached.

Anyway, just an update.
Thanks!

24

OK, managed to capture the error response.

If you need the entire response, let me know. I’ll send it by email because that’s 400k of JSON.

I was not editing the class in question in any other place.

{
	"success":false,
	"data":{
		"notifications":[
			{
				"data":[
					{
						"id":"vpkobj",
						"name":"lab-gallery__media",
						"settings":{
							"_border":{
								"radius":{
									"top":"var(--radius-s)",
									"right":"var(--radius-s)",
									"bottom":"var(--radius-s)",
									"left":"var(--radius-s)"
								}
							}
						},
						"category":"wmyjla",
						"modified":1730479404,
						"user_id":1
					}
				],
				"key":"globalClasses",
				"action":"modified",
				"author":"h.udo",
				"avatar":false,
				"timestamp":"1730479404",
				"desc":"Modified: Classes (1)"
			},
			{
				"conflict":"<strong>Conflict<\/strong>: The following classes have been modified by the user below since your last save. Accept or discard those changes to continue your save.",
				"data":[
					{
						"id":"vpkobj",
						"name":"lab-gallery__media",
						"settings":{
							"_border":{
								"radius":{
									"top":"var(--radius-s)",
									"right":"var(--radius-s)",
									"bottom":"var(--radius-s)",
									"left":"var(--radius-s)"
								}
							}
						},
						"category":"wmyjla",
						"modified":1730479404,
						"user_id":1
					}
				]
			}
		]
	}
}
25

I have this problem as well and I initially thought it was a server issue. I’m getting similar error codes as noted by previous comments here.

We have a multisite, and the odd thing is it happens on one subsite, but not the other. I’m always editing different pages in different tabs, but the error happens more frequently on the second subsite.

The ONLY difference I can tell between the two subsites: one subsite has a Section template on only one page while and the other has a Section template on multiple pages.

26

This is stull happening in 1.11.1.1 for me (not sure if it was supposed to be fixed for that one)

27

Hi,

I can see that the fix is created locally but has not yet released. So it’s still happening. When this happens, consider that two classes conflict.

Matej

1 Like
28

The same problem is happening constantly here. To avoid losing big changes I am saving every new change. But productivity is very compromised.

Bricks: 1.11.1.1

29

Hi guys,

We’ve fixed this in Bricks 1.12 BETA, now available as a manual download (Bricks – Account)

Please let us know if you are still experiencing issues.

You can see the full changelog here: Bricks 1.12 Changelog – Bricks

As with any beta release, please do not use it on a production/live website. It is only meant for testing in a local or staging environment.

Best regards,
Matej

30

The experimental setting of “Global Data Sync” does not correct this issue and results in the following " Error: [Object Object] "

image

1 Like
31

Hello,

this should be solved in 1.12, can you make sure that you are on at least 1.12 or 1.12.1 version?

Matej

32

Hey all,

thanks to @KevDev, we can now reproduce this issue and I’ve linked this topic to the internal bug task for this.
As always, we will update this task when the issue is solved.

Thanks and best regards,
Matej

2 Likes
33

I’m using 1.12.3 and have to manually save my work every 5 minutes or so to avoid magically disappearing / not-saving work. Is this still a known bug? If not, what could possibly be leading to Bricks not saving my work from time to time? Server settings or something else?

By not saving, I mean I will do some work thinking everything is fine. I hit save, refresh the browser, and voilĂĄ - it was is if I did no work.

[edit] I see Builder Changes Not Saved is a known issue, but the issue identified is not relevant to my case (my postmeta meta_value is longtext).

34

Hi,

the task is still a WIP. If you have the issue, you As for now, you can disable “Global Data Sync”, and the issue should be gone.

Best regards,
Matej

1 Like