This is not a big deal, and not sure if this is a sudden bug, or a sudden fix. For the last couple of years that I have worked on this particular project, my menu items used dmx-bind:href but they also had a regular href tag like so:
This worked fine until yesterday when some extension updates appeared and I installed them. I did not download 7 beta, just the extensions that showed up as having an update. So now, if the href="#" is combined with dmx-bind:href="!url?varBaseUrl.value+url_name:url" the regular tag takes precedent and the link doesn't work. Which is expected when an href tag uses a hashtag.
Only reason I bring it up is in case someone else suddenly has this issue and was stumped for a little bit as to why their menus suddenly stopped working. Like I said, perhaps the intention is for the regular tag to take preference over the dmx-bind. The only reason those regular tags were on there anyway, was probably my lack of experience with Wappler when I started this project or I copied and pasted them from somewhere that did use the hashtag and I didn't remove them after adding dmx-bind. They aren't needed.
Anyway, that was a very long explanation just to let you know what the fix is if you have both on a link....haha
The dynamic property should always override the static property, if it doesn't then it is a bug. Does this happen on all links or on specific routing links?
Ok @mebeingken, I take it back about it not being a big deal, it wasn't so much when I thought it was just href tags, but input name tags are real gotchas if they are in a repeat like so.
