We’ve got a big update for you today. This build includes a host of fixes to keep everything running smoothly, introduces the brand-new Tree Nav component for building structured navigation, and adds a selection of new Templates to help you kick-start your next project.
Here’s a quick (and speedy talkin’) video highlighting the new menu templates. Enjoy!
What’s New in Elements 1.3.0?
Added new Tree menu component
Added Tree menu template
Added “Fixed Menu” template
Added more SVG assets to Core Resources
Added option to show/hide Accordion content in edit mode
Improved server compatibility for Form component
Improved the drop zone for Gallery and Slider components
Possible fix for the modal not closing under certain situations
Fixed an issue where the Form logs folder was not uploaded to the server
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.
I think it’s an excellent feature with a lot of potential applications. I have a question about its integration: Is it possible to use both a standard menu and the Tree menu to manage the visibility (hide/show) of certain pages?
@dan The new Tree component is incredible; it is going to be very handy.
But as you probably anticipated, I do have a few enhancements I would like to see added.
Support for menu icons in LINKS, I create in-page navigation links as sub-items to a page, and it would be handy to be able to have their icons visible as well.
It would also be nice if the icons could be controlled at different levels. For example, I might not want them at the root level, but rather in the sub-menus. Although as a workaround I can just delete the ones I do not want to see displayed. The key missing feature is displaying them for LINKS in the tree, not just pages.
Borders, I immediately wanted to use borders on my items in the tree, and was somewhat disappointed to find that these are not available. It would be nice to see them added, as there is a lot that could be done to enhance the visuals in the tree using borders.
Finally, I would like to see support for more control over the SVG that is used to display the state of a dropdown, as the current support does not give us any control over the transformation of the SVG. Color properties for the SVG would also be handy. Or, at the very least, it should use the same color settings as for the item. If there is a hover color, the SVG should also use it. Currently, it is always BLACK regardless of how the item text is set. This is even more important when using a hover background on an item.
Sorry to be so demanding, but the potential for this new component is enormous, and I want to be able to leverage it to the fullest extent, as it means I can eliminate a lot of custom in-page navigation I had to create.
I want to add that I really appreciate the addition of this component; it is going to make a significant difference.
Fatal error: Uncaught Error: Failed opening required '/Users/UlrichThiess/Library/Containers/com.realmacsoftware.rapidweaverelements/Data/tmp/RapidWeaver/52780/RWDocumentPagePreview/document-C19361BC-3AA7-48F5-B0F5-874AECC1959E/artikel/../../rw/elements/com.realmac.corepack/api/vendor/autoload.php' (include_path='.:') in /Users/UlrichThiess/Library/Containers/com.realmacsoftware.rapidweaverelements/Data/tmp/RapidWeaver/52780/RWDocumentPagePreview/document-C19361BC-3AA7-48F5-B0F5-874AECC1959E/artikel/index.php:4 Stack trace: #0 /Applications/RapidWeaver Elements.app/Contents/Resources/RWWebServerLaunch.php(189): include() #1 {main} thrown in /Users/UlrichThiess/Library/Containers/com.realmacsoftware.rapidweaverelements/Data/tmp/RapidWeaver/52780/RWDocumentPagePreview/document-C19361BC-3AA7-48F5-B0F5-874AECC1959E/artikel/index.php on line 4
This works with version 1.2.5
now we have /../../rw/elements it should be /../rw/elements
index.php correct (version 1.2.5):
<?php
// Ensure Composer autoload is included for dependency management
if (!isset($GLOBALS['__composer_autoload_files'])) {
require_once __DIR__ . '/../rw/elements/com.realmac.corepack/api/vendor/autoload.php';
}
// Ensure the CMS helper functions are available
if (!function_exists('cms')) {
require_once __DIR__ . '/../rw/elements/com.realmac.corepack/api/cms.php';
}
// Include centralized Twig setup
require_once __DIR__ . '/../rw/elements/com.realmac.corepack/api/twig-setup.php';
?>
We do have border support, just not for individual items
I’m not sold on adding border support to individual menu items, I’m not sure anyway (apart from you?) would use it…
We match the text colour. If it’s not working for you it probably means your SVG is not setup correctly. You need to ensure your SVG is using “currentColor” for the fill in the code.
Here’s an example of it working:
Phew, okay, so… If we add support for icons on all levels, will that be enough to get the Tree component working well enough for you?
I go to great lengths to ensure all of my SVG icons are using “currentColor”, but of course, the one that I used was the only one in my collection that I had NOT cleaned up, sigh! So now it is working as expected.
Don’t get me wrong, I will be using the tree even without the support for icons at the different levels, it just won’t be consistent with how I have been using the icons in the past.
I think you are referring to the “clicking left side of open modal doesn’t close the modal”, right?
If so, we had to revert the change to the Modal as it caused too many unforeseen issues. At this time we are not able to provide a robust fix for that specific issue, and we have unfortunately had to file this one as “that’s how it works”, at least for now.
If this is a different issue, please provide me with more details and a sample project file so I can investigate it. Thanks
more than welcome!
