Variables crash

Community resources General
1

Hi,

When I try to call up the created base variables on our current page, I get an error message.

Earlier I worked with the variable modes on a blank page and everything worked fine.

But unfortunately not on our existing page.

Is this a known crash?

Thanks and greetings
Toby

3 Likes
2

Bildschirmfoto 2025-01-15 um 12.04.39
Bildschirmfoto 2025-01-15 um 12.04.391650×1854 115 KB

chrome browsercache emptied, restarted, logged in again, crashed at every start.

3 Likes
3

Even if I’m not exactly making myself popular here:

Short interim status in exchange with Webflow Support 3 days later:

I was asked to do a restore of an older backup, whereupon I initially refused, as I am currently doing a lot of work on the site and don’t feel like blowing 1 day’s work to the wind because of a bug I didn’t cause myself.

After 3 days of being put off by the fact that the developer team still hadn’t found a solution to the problem, I imported an older backup today, as I simply have to keep working on the site and can’t wait for an uncertain answer.

Result of the restore: The error still occurs.
I then went back to a backup that was 6 days old and before the new variable modes were introduced - the same error here too.

Too bad. Next week I will consider whether to stay with Webflow or look for an alternative. Not at the prices that Webflow is now charging.

Kind regards
Toby

3 Likes
4

This issue has been happening to me as well for weeks now. I thought it was just a one off bug - but no, you still can’t access variables of any kind (font sizes, color palletes, etc) without this bug occurring.

This is a huge issue that is slowing down development, when can we expect a fix?

1 Like
5

This has been happening for me since they launched the changes to the variables panel which I believe was on the day of this original post. I can’t even open the variables panel for the last 27 days. Just because an issue is only happening on existing sites and not happening on new ones does not make it less of a priority. This needs to get escalated and fixed ASAP.

1 Like
6

For everyone here, remember this is the community forum, and is not closely monitored by Webflow.

Make sure to file a support ticket so that the appropriate teams are notified.

7

I made a support ticket and after a couple weeks of back and forth they finally found a fix for this issue. I’m not sure why they haven’t pushed the fixed to all sites, but here’s they steps they gave me to fix it manually on your project:

  1. Backup your project: Command + Shift + S (on Mac) or Control + Shift + S (on Windows)
  2. Open the console (press F12)
  3. Run the code snippet below in the Devtools console (copy > paste into console > hit Enter)
  4. Backup your project again
  5. Reload the Designer
  6. Check that Variables panel should be open without crashing

Code snippet to run in console:

let p, r = x => x === p ? ‘default-body’ : x;
_webflow.dispatch({type:‘STYLE_BLOCK_UNNESTED’, payload:
_webflow.state.StyleBlockStore
.update(‘styleBlocks’, b => b.mapEntries(([k,v]) =>
!p && v.type===‘tag’ && v.name===‘body’
? ((p = v._id), [‘default-body’, v.set(‘_id’,‘default-body’)])
: [k,v]
))
.update(‘affectsMap’, m => m.mapEntries(([k,v]) => [r(k), v]))
.update(‘globalOrder’, l => l.map(r))
.update(‘styleBlockIds’, l => l.map(r))
});