All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
- Fixed an issue where the sites for which a nav was enabled wasn't checked against the sites a user could edit
- Fixed an issue where active state checking would only on PHP 8 or higher
- The Node classes field now be filled with predefined values, more information can be found in the readme (#57).
- Navigation items are now automatically disabled when the related element is deleted, and enabled when the element should be restored (#39).
- Fixed amNav upgrade migration
- Fixed an error that occured when changing the name of a heading
- Fixed some issues in the amNav upgrade migration
- Fixed an issue with active states when the url included query parameters (#54)
- Fixed an issue with dragging node with children to the top of a navigation tree (#56)
- Fixed an small issue with active states on similar urls
- Fixed an error on navigation detail cause in 2.7.2
- Plugin now installs with Composer 2.0 #51
- Fixed an issue where removing SuperTable elements would crash on our after delete event.
- Added the option to disable caching on the plugin side entirely. (#43)
- More persmission fixes for sites with 1 navigation
- Fixed a small issue with the editable sites redirect when only 1 site was enabled
navigate.getRaw
now has the option to take a siteId as a second optional argument (#47)- Added
hasChildren
andlistClasses
functions to make migration from amNav easier (#46)
- Fixed an installation issue for Postgresql users (#44)
- Fixed a crash on installs that run Craft versions before 3.2 (#45)
- Fixed an issue that causes navigations with multilple levels to crash in the CP (#42)
- Added a 'Navigation' field that lists all navigations, so you can customize navigations per entry when needed (#41)
- Navigations are not cached when
devMode
is on. - Urls with
token
params are not cached (#38) - Nodes are linked based on their site id in the CP (#40)
- The entries select modal now also show a sites menu you you can link entries from other sites (#35)
- Fixed the active state check for url type nodes (#36)
- Fixed an issues with navigation persmissions for installs with only 1 site
- Removed an unused migration that caused upgrade issues after 2.4.0
- Checked a couple of issues with excisting navigations after upgrading to 2.4.0
- Node urls are now displayed on the overview to better differentiate between entries with the same name (#34).
- Navigations now be enabled/disabled per sitegroup for a better multsite author experience
- The sitegroup is now also listed in the sites dropdown
- Menu headings can now be added, making it easier to work build larger multi-level or multi column menus (#29)
- Full upgrade support for sites that used amNav on Craft 2
- Disabled nodes on level 1 or deeper are visible in the CP again
- Fixed an issue with linking to an asset
- Added support for
project-config/rebuild
- plugin now requires Craft 3.1.20
- Last of the caching update/fixes? Hopefully 🙂 - Fixed an issue where navigation cache wasn't being cleared correctly
- Fixed a regression error where we stopped clearing Blitz cache in 2.1.1
- Fixed an issue with caching where, after moving them, nodes wouldn't show up on the frontend anymore
- Blitz ⚡️ support! Updating your navigations will now also clear & warm Blitz's cache if it's installed (requires Blitz 2.0.1)
- Navigation caches can now be cleared from the CP, under utilities/clear-caches.
- Fixed an issue where a disabled element would still be included in the frontend query (#21)
- Fixed an issue where editing a navigaation would always link to the default site navigation (#23)
- Show only editable sites in the edit screen dropdown (#23)
- The site selection dropdown is no longer shown in the entries/assets/categories modal (#23)
- URL nodes are now also parsed for variables from your .env file
- Fixed an issue where disabled child nodes would be included in site querries
- Craft 3.1 is here! Navigate is fully compatible and now support Craft's "project config", allowing you to include navigations in your project.yaml
- Project config support! Adding, changing settings and removing navigations is now done through Craft's project config.
- More performance tweaks: navigations are only queried once if they appear on a page multiple times.
- Better logging when moving or editing nodes in the CP goes wrong, or when building the cache goes wrong
- The category node label now fits on one line #15
- Fixed an issue where IE11 users could not move nodes
- URL nodes are now also parsed for variables from your
config/general.php
- Fixed an issue with rebuilding navigation caches after making changes in the CP
- URL nodes can now contain Craft aliases like
@web
or your own custom aliases. #18
- Greatly improved querries for pages with multiple navigations filled with elements
- Fixed an issue where removing a node from a navigation would not refresh the cache
- Added missing use statement
- Fixed an issue with caching nodes for diferent sites.
- Fixed a crashing issue with fresh installs where defaultNodeType would still be in the database
- Added some big performance improvments, especially for sites using lots of different navigations per page. Navigations are now cached and updated on change.
- Fixed an issue with active states with the same word would occur twice in a url(#14)
- Fixed an error with getting the edit url for an category that doesn't excist anymore (#13)
- Fixed an error with getting the edit url for an entry that doesn't excist anymore (#13)
- Fixed an error when a navigation contained an element that doesn't excist anymore (#11)
- Node are now active when on a child url that is not in the navigation (#10)
- Added Dutch (NL) translations (#5)
- Node title now links to the entry's edit page or show the edit modal for url nodes (#2)
- The "Default Node Type" setting wasn't used for anything so this update removes it
- Opening the URL modal now moves focus to the name field, so you can start typing right away (#7)
- Sites in the multisite dropdown now stay in the same order (#6)
- Styling issue with node type in Chrome and Firefox (#8)
- Initial release