You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The anchor/querystring data is not loaded into the editor after saving, and it's not included in the data on the front end. I haven't looked in any detail but it seems like this is because that field is missing from the class definitions for MeganavItem and MeganavEntity.
Steps to reproduce:
In a new or existing Meganav content item, click the Add button to add a link to the navigation
When the link Settings panel opens, enter a link URL and title, or select a page from the content tree
Enter "#test" (or any other string) in the Anchor / querystring fields of the Settings
Click Save on the settings panel
Click Save and publish on the Meganav content item
Hit your browser's refresh button
Click the settings for the item you just added. When the settings panel opens, notice the Anchor / querystring field is blank. (If you open the front end of a page loading that navigation item's content, you'll see that the MeganavItem in the data has no Anchor or Querystring property, or any other property containing the data)
The text was updated successfully, but these errors were encountered:
Should this be handled the same way in Meganav (combining the Url and QueryString in MeganavItem.Url), or does it make more sense to keep them separate? (There's also a third, albeit messy option to use one property for just the URL, one for just the QueryString, and one for the combined URL/QueryString.)
The anchor/querystring data is not loaded into the editor after saving, and it's not included in the data on the front end. I haven't looked in any detail but it seems like this is because that field is missing from the class definitions for
MeganavItem
andMeganavEntity
.Steps to reproduce:
The text was updated successfully, but these errors were encountered: