I am experiencing an issue with a Global Navigation component in Elements and am wondering if anyone has encountered something similar.
I have approximately 72 pages on my website. The navigation is built using a Global so that changes can be made centrally. Most pages update correctly when I modify the navigation structure, but about 6 pages do not.
For example, if I rename a page, change a folder name, or move a page within the site structure, the Global Navigation correctly displays the updated page name and menu position. However, after publishing, some of the generated links still point to the old URL rather than the new one, resulting in 404 errors.
The strange part is that the navigation appears visually correct, but the underlying links seem to retain outdated paths on a handful of pages.
Has anyone seen this behaviour before? Could this be related to Globals, cached links, page IDs, publishing settings, or something else within Elements?
It appears that some folder names I previously removed were still being retained somewhere in the system, preventing the old URLs from being fully cleared. To restore functionality, I recreated the folder names, which allowed the affected URLs to work again.
Although the website is now functioning, I remain concerned that the issue may be related to the use of Globals within my navigation structure. My concern is that outdated paths or references may be persisting behind the scenes, potentially causing future URL or navigation problems.
Reading your post one thing comes in my mind. Are you really sure your Globals are erverywhere the same. It sounds a bit you have changed (probably accidentially) a Global on a page by selecting Global Overrides. Then later on you copied this one.
I would renew the navigation from the originial on one of the pages and see if this helps. I also would publish my page again by using re-publish all files.
I had wondered if that might be the cause. I used Integrity Pro to track down the URL issues, and it identified the specific links that were generating errors.
From what I can tell, the original Navigation Global contained folders that were later removed. However, even after deleting those folders, their names continued to appear in the published URLs. It seemed as though some of the old folder references were still being retained somewhere within the project.
The issue now appears to be resolved using the workaround I implemented, but I still do not fully understand what caused the behavior in the first place.
Thank you for your suggestion and for taking the time to help investigate this.