Issue
Removing a "Go To First Child" content object from a page does not take effect right away.
Cause
Mura uses a re-direct to "route" users to the first child element of the site. When the re-direct is removed, the information remains cached in the user's browser.
Solution
Clear the cache from the browser and reload the offending page.
Environment
Details
Mura has a handy feature that allows a page to re-direct out to a child item. Clearing the "Go To First Child" content object however, may be problematic since the browser caches the re-direct. This means for example, that if a top-level page loads another top-level page, but the feature is ever removed via the Mura administration, the page will continue to load the second page.
Assume a scenario like this. A site has a Home section and a News section. Ignoring the reasons why a site might be implemented this way, assume that loading the Home page actually loads the News section instead. At some point the site owners decide that users will load the Home page instead. The re-direct is removed from the Home page, but users are still loading the News page.
The re-direct Mura issues is being cached by the user's browser, so a clearing of the local cache does the "trick." The assumption is that Mura employs a time-to-live to be associated with the cache, otherwise this could be quite troublesome to get each user to clear their cache.
Removing a "Go To First Child" content object from a page does not take effect right away.
Cause
Mura uses a re-direct to "route" users to the first child element of the site. When the re-direct is removed, the information remains cached in the user's browser.
Solution
Clear the cache from the browser and reload the offending page.
Environment
| Version | Mura Version 5.6 |
| OS | Any |
| Browser | Any |
Details
Mura has a handy feature that allows a page to re-direct out to a child item. Clearing the "Go To First Child" content object however, may be problematic since the browser caches the re-direct. This means for example, that if a top-level page loads another top-level page, but the feature is ever removed via the Mura administration, the page will continue to load the second page.
Assume a scenario like this. A site has a Home section and a News section. Ignoring the reasons why a site might be implemented this way, assume that loading the Home page actually loads the News section instead. At some point the site owners decide that users will load the Home page instead. The re-direct is removed from the Home page, but users are still loading the News page.
The re-direct Mura issues is being cached by the user's browser, so a clearing of the local cache does the "trick." The assumption is that Mura employs a time-to-live to be associated with the cache, otherwise this could be quite troublesome to get each user to clear their cache.
Comments
Post a Comment