Skip to main content

Mura KB: Pages continue to re-direct after removing 'Go To First Child' content object

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

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

Popular posts from this blog

Remove control of Chrome being managed by organization on personal devices

Chrome may indicate that it's being managed by a user's organization. This warning is provided by the Chrome Policies feature of the browser. To know if an instance of Chrome is managed by an organization, there will be an entry at the bottom of the browser’s hamburger menu (three dot menu), on the right side of the browser window that reads, "Managed by your organization." This is likely due to an entry in the Chrome Policies listing, which can be found by loading this page in the browser: chrome://policy The policies listed in this section are stored in the computer's file system in one of the following locations as JSON files. /usr/share/chromium/policies/managed /usr/share/chromium/policies/recommended Remove the offending JSON files, and click the Reload policies button. The Managed by your organization entry in the browser menu should be gone. A notice like this on instances of Chrome for work, school, library, or other devices that belong to an organizati...
Post a Comment
Read more

Allow Windows authentication using SQL Server driver with DBeaver

DBeaver will allow Microsoft Windows single sign on access when connecting to Microsoft SQL Server using the SQL Server driver (rather than jTDS ).  From the driver properties settings, set the integratedSecurity flag to true . Open the Connection configuration panel and choose the Driver properties section. Set the integratedSecurity flag to true . A subtle, but important step is to not provide username and password credentials to the connection.
7 comments
Read more

Connecting to SQL Server with jTDS using Windows Authentication

UPDATE:   At one point the tip in this article to set the USENTLV2 flag to true was accurate, but it appears it is no longer necessary, at least as far as DBeaver 's use of the driver is concerned.  If it solves an authentication problem, then great.  The expectation is that, an update in one of the packages that make this sort of connection possible has resolved the issue that at one time made this flag necessary. Connecting to Microsoft SQL Server using jTDS with a username and password that's managed by the database manager is pretty straightforward.  It may become a little more problematic however, when trying to use Windows authentication when connecting from a Windows machine. Do not supply a username and password. Set the USENTLMV2 property to true. NOTE:   Step 1 assumes a connection being made from a Windows machine.  If the connection is being made from something else, user credentials may actually be necessary. If the connect...
7 comments
Read more