Relume I have been working on a figma file for sveral months now and all of a sudden it says my file is outdated and can't use the relume plugin in figma anymore. You can't expect users to just move every file over to the latest version as soon as you release an update. Can you please undo this. Was working fine as of yesterday.
Adrian T. I feel your pain, exactly what I am going through too. It's unacceptable.
yup they broke everything overnight... and from what I am seeing it's a new way of working, but you gotta give teams time to catch up... You can't just up and change everything overnight with 0 notice
Yep with the new style guide. I'm happy to work with it, but I have a lot of old sites that are under the different clone, and if I can't put any elements into that, I might as well use a different resource and keep Relume only for new sites. They need to fix this, and have two forks of the clone guide, that way it can take both the new and the old. This renders every web developer useless right now who use Relume
Adrian T. I can understand your frustrations here with this lack of backward compatibility. The team is definitely aware of how unfortunate this is. I'll talk to the team about what the future holds here, if anything. As for bringing in new pages/components into an existing project, you should still be able to copy/paste these into your project. I think in order for the team to understand the gravity of this situation, it would also be super helpful to understand the use case for why you would be needing to import new pages into a figma file over the course of several months. I have my assumptions, but I think it would be more valuable to hear straight from you.
Hi Matt J., thank you for the reply! I have a figma file that's based on v2.7 that I started a while ago. Today I made some changes to the website in Relume using the site builder and went to paste in a component. Trying to open the Relume figma plugin gave me the message I posted earlier. So the main issue is that the Relume Figma plugin refuses to work completely, I can't paste anything I can't import anything at all. As an example I was able to make an update and import the entire sitemap and all the wireframes in one click not even a day ago. (same exact operation worked 24h ago with the same file and conditions and now no longer works), and I get that notice saying I need v3 styleguide. I get the need for progress, and can't wait to try out the new features introduced with V3 on my next project but you can't just ask us to re-do months of work, over this. You have to realize that your ideal user will have a few projects ongoing at the same time, and you can't just pull the rug from under everyone who has an active project or even a legacy site. I won't be able to sell the idea that I have to re-do work to my existing clients, because my tech stack decided to drop support for their file over night. .. Maybe release the previous plugin as a legacy so we can still use it and move over to the new plugin with the new file as we start new projects, otherwise all of us can land in some legal trouble
Adrian T. Understood. Lots of internal talks right now. I don't know which path we'll go but rest assured that we're looking into it. Having a legacy plugin is likely not the first thing that happens, if it happens at all as this creates a rippling effect of undesired issues but its still on the table. We'll do better in the future. Truly appreciate any grace you can show us during this as we work to come up with a solution.
Hi, is there any news/updates on the export to figma issue? I have the same problem as Adrian
Adrian T. Yoshimizu we've provided backwards compatibility to previous projects using older figma kits. The only exception is if you brought screens into an "empty" file - so you did not start your project using the figma kit. Which I'm hoping you did use a figma kit. We've brought back the paste button for older kits as well as being able to import sitemap/wireframes (but not style guides).
