SOLVED: Variable reordering is not saved

Browser: Firefox
OS: Windows

I’m trying to reorder my css variables, but after I change category tab they revert to previous order

2 Likes

Hi Illarion,
Thanks so much for your report!

Unfortunately, I cannot reproduce the issue. Would you be so kind as to provide a screencast using https://jam.dev showing and explaining what’s happening?

Have you tried to save in between? Does that keep the order?

Best regards,
timmse

Hi @timmse
Jam

On other installation I saw the same bug, but after reordering with AT manager it’s disappear (and in native bricks manager too)

I’m having the same problem. Whether I save or not, the order of my variables is not being remembered.

I’ve disabled all plugins that I can, and switched off shields in Brave, but nothing is working.

I’d love to better understand how you solved this issue @Illarion

Hi guys,
Sorry for the late response. Meanwhile, sorting within a category is a known problem that we are already working on.

We’ll let you know when the problem has been solved :v:

2 Likes

I’m very surprised to see this issue still present, several months later. :frowning: Hoping this is fixed soon.

I have a workaround I discovered accidentally today… if you sort it in the default “All” category, then it is ordered inherently in the sub-categories too.

1 Like

This doesn’t seem to be fixed yet in 2.0 beta either. :frowning: Hopefully this will come soon.

Edit: A new workaround I discovered today was to export the JSON of the variables, then use ChatGPT to order the variables in the way you desire, then save to JSON again and import it. This seems to fix the ordering at least in my quick test.

I’m seeing this exact same issue - ordering works outside of categories, but not inside of categories.

If you are chaining variables somehow, seems like order is important.

Other people are recently reporting this issue on the Facebook group too.

Can we please get this resolved? It’s concerning that this has taken so long to resolve as it’s been nearly 11 months since this was first reported now. :frowning:

Experiencing the same

Same here, we are waiting for solve this. :slight_smile:

Paging @timmse, I wanted to just see if there was any possibility of this being fixed in 2.1, as this is a very big inconvenience when using CSS variables because the display in the editor is the same order in the Variable Manager, and if that’s wrong then it’s easy to select unintended variables. This defect was reported nearly a year ago now, it’s disappointing this one is taking so long to fix. I do hope a fix for this will be coming soon, if not in 2.1 then hopefully the very next version if possible. :crossed_fingers: Thank you so much.

3 Likes

Still not fixed in 2.1.3

Why’s this still broken? Feels like it should be a quick fix.

1 Like

We fixed this issue in Bricks 2.2 beta, which is now available in your account.
Changelog: Bricks 2.2-beta Changelog – Bricks

Please let us know if you are still experiencing issues.

As with any pre-stable release, please do not use it on a production/live website. It is only meant for testing in a local or staging environment. The more feedback we get, the better :v:

1 Like