I'm experiencing a pretty substantial bug with the Webflow site importer. No matter what action I take, the importer ALWAYS tries to import the ENTIRE site. I'm just trying to add a page, or even just a new component to an existing page.
I’ve seen that too after the new folder updates
Interesting! Caleb P. Would you mind sharing a read-only link with Matt J.? We'll look into this for you. Very strange And thanks for letting us know guys! cc Michael R.
Yeah sure thing! I can share one this weekend.
Caleb P. thanks for sharing the read-only. I'll have to do some additional testing to verify the bug and go from there. My suspicion at the moment is that its because its an edited style guide which complicates the import significantly but your use case is not what I would consider an edge case either.
Yeah I found it strange that it would try to import ALL pages. I can understand the duplicate classes or even replacing all content on that single page, but like adding a "Contact" page shouldn't touch the "Home" imo
Sure thing! I'll DM one to you guys now. I can check it out this afternoon and let you know how if the bug still exists!
Hey peeps, I'm trying to get the bottom of this but really struggling to reproduce it. If you're able to, can you please send me a screen recording (loom or whatever) as well as a read-only link to the webflow design you've being importing pages into.
Yeah let me see if I can replicate it now!
Thanks mate! We've heard sporadic reports of similar stuff but never been able to get to the bottom of it … would love to solve this if we can.
Ok it seems like it's working ok-ish.
"ish"? Hahaha
What it did this time was first to switch the active page to "Home" and then back to the page I was previously working on, then adds the content correctly to that page
No other site content seems to have been impacted by the little "blip", so I think it's working? 😅
It did create a duplicate of every classname instead of just using the existing ones, but maybe that's expected, as well?
🤨 That I'm not sure of…
Will double check what the expected behaviour is meant to be
Ok sweet! Well at least one main issue is resolved now!!