What increases the attribute of modification?

Question

In %TRIDION_HOME%\web\WebUI\WebRoot\Configuration\System.config we can increase the value of the modification attribute to force Content Manager to force items to load.

This option is mentioned in the PowerTools talk , as well as in the section Profiling skins in Content Manager in SDL Live Content.

<server version="6.1.0.55920" modification="7">

Alternatives to updating CME include flushing the browser cache (CTRL + Shift + Delete in Chrome) or adjusting cache settings for each user.

Question

Should I use this for any changes on the CM side, such as GUI extensions, schema or schema changes associated with templates? Or is this only applicable to certain parts of the Content Manager Explorer?

In other words, after changing the schema and template, what is the best way to get users to get the latest components, drop-down lists of schemas and templates?

Answer 1

The values ​​of the modification and version attributes become part of the URL of each CSS and JavaScript file that the Tridion UI generates / merges from many static (images) files too. So the urls look like this: edit_v.6.1.0.55920.7.aspx?mode=css . Since the browser sees this as a new URL, it cannot possibly have a file in the cache. And thus, it will always download files from the server, instead of using (possibly outdated) files from the local cache.

This is a method of entering some version information into a URL called a “URL fingerprint”. Google typically enters the hash value of a file in the URL, ensuring that a fingerprint occurs without requiring developers to manually increase the version number. But depending on what type of fingerprint is used, this method is a pretty effective way to ensure that all browsers download the latest version of your code.

If you are developing a GUI extension, you can really get the same effect by clearing your browser’s cache or even completely disabling it (for the Tridion domain). But as soon as you deploy the extension to the server without development, changing the modification attribute is the most specific way to ensure that all of your users receive the latest JavaScript / CSS changes without each of them, to clear their cache manually.

URL filtering in Tridion only affects CSS, JavaScript, and image files. Actual CMS data (such as Schemas and components) are loaded using XMLHttpRequests and thus not affected by the modification attribute.

Answer 2

As far as I know,

 <server version="6.1.0.55920" modification="7"> 

This only clears JS and CSS caching. When a user accesses the CM, the CM transfers all files, including the latest copies.

Should I use this for any changes on the CM side, such as GUI extensions, schema changes, or schema-related changes? Or is this only applicable to certain parts of the Content Manager Explorer?

For this line, the answer is No. Because when the user ever makes any changes to the schema, the changes should be updated in all publications. This is not currently happening in the browser.

Hope this can be fixed in future versions.

In other words, after changing the schema and template, what is the best way to get users to get the latest components, drop-down lists of schemas and templates?

The user must now make a strong update to get updated information on all publications.

Answer 3

CMS Interface SDL Tridion caches CMS elements to provide faster viewing and loading of its own interface. This means that sometimes:

• Custom GUI Extensions May Not Display Latest File Versions
• Newly created or changed CMS elements may not display or show the latest version.

This is why sometimes a new keyword is not displayed in the component field, or when trying to add a component page, a new component template is not displayed.

Increasing the modification number in the node will cause all CMS elements to show the latest versions to CMS users (users). You will see if this value is used to reference the CSS and JS files used by the CMS GUI.

As a developer, I also disabled my Firefox cache (I prefer firefox for the firebug extension, which is great for working with GUI extensions), since it means you don't have to go and change this value, a simple browser update seems to always do the trick. Disabling the cache is explained here: https://superuser.com/questions/23134/how-to-turn-off-the-firefox-cache