Today’s build fixes a range of reported bugs, adds more items into Core Templates, and lays the groundwork for app-wide Publishing Bookmarks. All in all, a solid update.
What’s New in Elements 1.2.3?
Started work on app-wide Publishing Bookmarks
Added new Scaffolding items to Core Templates
Added support for Remote mp4 Thumbnails
Resources dropwell now uses mp4 icon if it’s not possible to generate a preview frame
Fixed a Preview caching issue related to the unique ID of documents
Improved sorting of alphabetical items in Resources
Fix forward slashes and improve validation when overriding website address
Audio component will now pause other playing audio components on the same page
New Projects window now handles unknown addons gracefully
Elements should prompt you while it’s running to let you know there’s an update. If it doesn’t, you can select the “Check for Updates…” menu option from the “Elements” app menu.
If you are running a licensed copy of Elements, please post all feedback in the Feedback Forum. You can use the Elements > Send Feedback… menu item to automatically pre-fill the build number into a new topic.
Hello,
I have just updated to this new version and tried to import my Classic project. Thank you for trying to make it possible. I am currently in trial mode. Unfortunately, the current outcome is unsatisfactory. Even some HTML links to files on my server are not imported and I see a lot Latin looking junk text insetad of my text (is because of the trial mode?). Even in basic HTML Stacks all the formatting is lost. Markdown Stacks are imported as pure Markdown and when I preview, I see the Markdown code instead of its conversion. So, do I need to conclude that we cannot use Markdown in Elements? Sorry, I am just starting to play with Elements to see if I can switch without too much hassle. I was very happy with RW for my tasks, and I find the switch a downgrade (even if the lighter and quicker code for my webpages would not have a negative effect). However, I am not a company that wins its bread by creating websites. I only maintain my academic website and will not have a lot of time to convert it to Elements.
It’s worth noting that the importer will migrate all pages and site settings but page content is trickier, especially when it comes to Stacks. We retain as much of the text and images as we can along with the page structure. However, most of the styling will be lost. You can find more information here Importing Projects | RapidWeaver Elements Docs