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 problem before?
dan
(Dan)
28 September 2025 20:20
2
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
Hi,
Thank you for your response.
Here is the link to a simple project where the problem occurs : elementsapp://downloadDocument/lo3QxhThrgFP
dan
(Dan)
29 September 2025 08:25
4
Thanks for the project, we’re looking into this now. Will get back to you soon, to let you know what’s going on.
Thanks for looking into it.
Did you find an explanation to this problem ?
dan
(Dan)
30 September 2025 20:20
7
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”.
However, the good news is we’ve now fixed this in Elements. The fix will be available in the next build (due tomorrow).
Thank you.
I have checked my Classic project. It was not “Relative to Docroot” but “relative to website Address”.
I don’t remember why I had changed this parameter.
dan
(Dan)
1 October 2025 16:26
9
The latest build of Elements should have this issue fixed now
Hello again,
Another update to keep the refinements coming while we work on some bigger things…
What’s New in Elements 1.3.4?
Updated Core Templates with improvements and refinements
Fixed Classic Project Import so it now works correctly with the CMS
Fixed Video Lightbox scaling issue
Removed date from the emails banner
Fixed an issue where the Badge image would sometimes not appear
Purchase a License
You can visit the elementsapp.io website to purchase a license.
Get the Update
Elements sh…
YES, Problem solved. Thank you.