RapidWeaver Elements 1.3.3 (23871) I’ve encountered a problem with a project imported using the “[BETA] Import Classic Project” feature. The CMS doesn’t seem to work (“No item found”), although it works fine in a blank project created directly with Elements. Have you come across this kind of prob…

Yes, sorry for the delay. It seems your project was an imported Classic project and was using an option that Elements doesn’t support, something like “Relative to Docroot”. [CleanShot 2025-09-30 at 9 .18.17@2x] However, the good news is we’ve now fixed this in Elements. The fix will be available …

No, but it’s probably just not set up quite right. If you share your project we can take a quick look and let you know what the issue it :slight_smile:

Hi, Thank you for your response. Here is the link to a simple project where the problem occurs : elementsapp://downloadDocument/lo3QxhThrgFP

Thanks for the project, we’re looking into this now. Will get back to you soon, to let you know what’s going on.

Did you find an explanation to this problem ?

Thank you. I have checked my Classic project. It was not “Relative to Docroot” but “relative to website Address”. [advanced] I don’t remember why I had changed this parameter.

The latest build of Elements should have this issue fixed now :slight_smile: [image] Elements 1.3.4 (23875) optical_diskBuilds Hello again, Another update to keep the refinements coming while we work on some bigger things… What’s New in Elements 1.3.4? Upda…

YES, Problem solved. Thank you.

CMS not working in project imported from Classic

Elements CMS

dan (Dan) October 1, 2025, 4:26pm 9

The latest build of Elements should have this issue fixed now