Relume Community Icon

Relume Community

Need Help: Issues with Import Settings Reverting in Project Redo | Relume Community

Need Help: Issues with Import Settings Reverting in Project Redo

·

·

Matt J. Hey I need your help, I've DMed you @ early afternoon but it seems that it has gotten lost in your list of DMs. I am encountering different import settings once again. Older thread: https://relumecommunity.slack.com/archives/C02MS2V0FSP/p1745877057429169 Image #1-3 -- seems the import setting has reverted back to previous system -- based on page names & section titles. After seeing this, I've decided to redo the project (this was like my third time redo-ing the project and this project is a BIG project) to streamline the improved version with variable modes & better class naming classifications. I jotted down the new system for Relume wireframe, Webflow class naming (folders), and finally Webflow component labels. I've tested the imports several times this afternoon and it was consistent. Then, to my despair, after completing all components & halfway to completing the entire wireframe, I decided to test if importing the new components will work, and unfortunately, it did not and had reverted back to different import settings - header#, etc -- not based off page & section titles.

29 comments

Eric B.
·
·
Adding another screenshot to vouch two different import settings - this matches Image #1-3 -- in a different webflow project & relume wireframe
Eric B.
·
·
I am going to see if I can screenrecord this
Eric B.
·
·
OK, yes, I finally identified the main culprit 😰 -- captured everything in a video Editing now -- to display three different videos
1.
Wireframe #1 (Test) & Import System #1 -- shows what import system looks like
2.
Wireframe #2 (Actual WIP Wireframe) & Import System #2 -- different system
3.
Wireframe #2 (Same wireframe above) & What I did differently this time, after realizing what I did & not did on first two imports... Style Guide. and BOOM, the culprit!
Eric B.
·
·
Matt J.
·
·
Eric B. you're right - I was out to lunch, read your messages, and forgot to come back to them. Thank you for bumping this back up. We have not intentionally changed this naming convention - this is a bug I've raised with the team. Appreciate you taking the time to troubleshoot what the issues may be there. I noticed in one of your screenshots somewhere that you have the Finsweet Folders extension - if you are using that, why would it take 5-10 hours to rename classes - just curious. Wanting to make sure we're considering all context/use cases for solutions that we recommend.
❤️1
Eric B.
·
·
Really, it would be much easier if you put aside what we've discussed weeks ago and look at the videos. The videos highlight the bug -- when I import with styleguide & without styleguide -- it affects the class naming. You can directly compare video #2 and video #3 -- both uses same relume project, and only have one import setting difference -- with & without styleguide import
Eric B.
·
·
By recognizing this bug, it resolves all issues because I was initially confused with the origin of bug, and I've finally found it Something has gone wrong during the import process when you import the relume project into webflow with its styleguide -- classes don't get named but components do (in its webflow project library)
Eric B.
·
·
I strongly believe -- happening to have two different class naming systems due to importation of styleguide is an unintended bug/feature
Matt J.
·
·
yeah, thats what I said - that it is a bug that I've filed with the team
👍1
Matt J.
·
·
discovered in my weekly QA about 3 weeks ago
❤️1
Eric B.
·
·
Once this bug gets resolved, everything will be resolved 🙂 because I will not need to rely on finsweet folders for in-depth class naming -- it'd be ready & go after import
Eric B.
·
·
when & wheres your weekly QA though? curious
Matt J.
·
·
every Tuesday
Matt J.
·
·
where? at my desk haha
😂1
Matt J.
·
·
idk what you mean, I run 500 point test on all plugins and the entire ecosystem every Tuesday
Eric B.
·
·
Oh, in your physical office 😂 gotcha
Matt J.
·
·
yeah
Matt J.
·
·
as for finsweet folders - and the naming conventions, personally I found the names that the import tool was coming up with to be too literal of the page names and sections that were created and once they are renamed that way, its actually impossible to rename them at all - there's a few use cases where having them named on import works great but in my experience, I'd rather do it myself and have only found that it maybe takes 30-60 mins with the finsweet folders feature and I can name things more clearly. I think there are some solutions that could be implemented but as you can see, we've got some bugs to resolve first.
💯1
Matt J.
·
·
maybe this was you I had this convo with weeks ago (hence your reference) - I can't recall to be honest, apologies. A few hundred lumers a week will do that to a guy's memory.
‼️1
Eric B.
·
·
yeah it was me 😁 https://relumecommunity.slack.com/archives/C02MS2V0FSP/p1745877057429169
Matt J.
·
·
ah roger that
Matt J.
·
·
good times
😂1
Matt J.
·
·
🫠🙃
Matt J.
·
·
I promise my personal bias is not swaying whether this bug gets fixed
Matt J.
·
·
I am the voice of the community and I know a lot of Lumers love this feature and I think it makes the process from Relume to Webflow far easier if the classes name correctly
❤️1
Matt J.
·
·
so I'll be sure to follow up with the engineers soon, really appreciate you taking the time to record those videos and the additional context that you've found - I'll add this to the bug ticket to help the engineer get up to speed quicker with where to look
🙌1
Eric B.
·
·
Haha totally understandable! So to comment on the duration of using finsweet folders -- if you import without using a styleguide, yeah, 30-60 minutes or so if the website is not complex imo -- or it'd be additional hour or smth If you import with a styleguide, it will complicate everything by x10 because you dont know which layout is, compared to being able to find and identify based on page/section names -- quicker that way and you can also cross-check your relume wireframe project But again, personal preferences, and by resolving this bug, as you've said, "will make the process from Relume to Webflow far easier if the classes name correctly" Looking forward 🙏 -- for now, I will be not using styleguides until this gets fixed, and I think this should be also communicated with Lumers so they can be in the loop as it is super impactful to everyone's works and it can be super agitating & confusing
Matt J.
·
·
agreed
Eric B.
·
·
Doing an all nighter with breaks to deliver first draft to the client -- I've discovered a new workaround; and I think it is possible that the engineers did this when they built the styleguide
1.
Import wireframe without importing a new styleguide from relume - just use default one
2.
Apply changes to component & class (folder) names (15-60 mins)
3.
Import a blank page, but this time, import the new styleguide
a.
That is where the engineers stop there, I believe
4.
Make several adjustments to variables (I am currently exploring & falling in love with variable modes
a.
Note: Additional modes wouldn't be overrode by the new styleguide import however the initial base color scheme variables will be overrode so need to reset it back to the original setting if you apply changes to variables before importing new styleguide
5.
Viola