Loooooong time known issue: when I use the Chrome extension to try to change the spacing strategy, it bugs out. (See screenshot.) I asked Claude to take a look, it maybe debugged it (in thread). When will we get a fix? 😕
This is a Relume extension bug, not something you did wrong. Here's what's happening: The extension's "Update Spacing Strategy" pane reads your Webflow project's variables to do its work. But its schema (Zod validation) only knows about three variable types: length, font-family, and ref. Your project has color variables, which Relume hasn't accounted for — so when it tries to parse them, it chokes. The two specific problems:
Every variable has type: "color" but the schema only accepts "length", "font-family", or "ref"
The createdOn field is null on all of them, which the schema also doesn't allow
Since it fails on every single variable (0 through 35), the whole page list can't load. What you can do:
This is a Relume bug to report to their team at support@relume.io — it's reproducible and the error gives them exactly what they need to fix it
In the meantime, if you need the spacing strategy feature, you could try it on a Webflow project that doesn't use color variables to see if that unblocks you
Ugh, made worse by the export refusing to build with spacing blocks, despite picking it in the webapp and starting a whole new project to try to get it working.
Aw crud just realized I'm in the Figma channel posting about Webflow. What a loser lol
Lee F. totally understand the frustration here - especially for something as painful as setting a foundational preference for spacing - doing this manually would not have any kind of ROI at all. Your AI summary of the issue makes complete sense and the timing is spot on - broken since we released style guide export - I will add this to the bug ticket we have in hopes that it helps speed up the time to fix. As for timing of a fix, I'll be completely honest with you, I don't see this getting fixed anytime soon. And by that I mean potentially not even this year. We're in a marathon that has lasted 8 months so far, and likely will last another 3-4 more months, of doing a complete rebuild and rethink of our platform with a small but mighty team - stretched as thin as we can get, grinding it out day in and day out in the trenches of really intense work - while I think an engineer would actually enjoy such a simple task as this, its just not in the cards to allocate the resources right now. We have some other bugs that need fixing ahead of this as well. My hope - and this is just my opinion of things, not a decision, is that we get this new platform up, get our vision built, grow the team, and allocate a little bit of resources back into fixing these bugs. I'll do whatever I can to advocate for doing so. I have always appreciated your feedback Lee, your voice always gets heard with our team and your support is greatly appreciated. Hoping you can extend some more patience and grace for us and if so, I hope that good karma comes back around in the form of fixing incredibly annoying bugs like this one.
and yes, that was a super long and nice way of saying "ain't got no gas in it!". 🤣
Ha!! And I always appreciate your responses and attention, Matt. Keeps me confident this is all going to work out. And yeah, I assume my use of Relume in 6 months will not match how I'm using it now, and maybe sidesteps a lot of issues. Somewhat relatedly, do yall have an affiliate program? I'm recommended we build my next client's site tightly sticking to fairly naked Relume standards so they can paste in Relume modules fairly reliably, giving them a much wider breadth than if I just built out an internal-to-Webflow component library. I demoed Relume, there were a lot of oohs and aahs. 🙂
Lee F. for sure - send us an email at affiliates@relume.io and we'll get that sorted! 🙌
