When a package with JS and CSS code is built and deployed, and then a page requested from the website, it contains links to JS and CSS files processed by AEM (with additional name parts and possibly minified), e.g.: Generally, when a new version of the package is installed, new JS and CSS file names are generated; and, when they are requested, the new code is served. However, from time to time we notice that, right after deployment, pages already contain links to files with new names but those links serve old code, which often breaks important functionality, as old code is invalid for the new markup. These invalid JS and CSS files are then cached in visitors' browsers, and even when Publishers start serving the new code, it does not help, as the scripts' names are the same and client browsers get them from cache. The only way to fix it is to deploy a new build so file names are updated. But this takes hours to arrange and perform, and all this time the site is partially broken. Looks like the issue is reproduced for only a short time after deployment: we have never managed to obtain the broken JS or CSS from a Publisher manually, but still, it was cached on Dispatchers, so some visitor managed to get it. What can be the cause of this behavior? Regards,Alexander

Hi all, In one of our page type's properties, we have a pathfield with pickersrc="/mnt/overlay/granite/ui/content/coral/foundation/form/pathfield/picker.html" and root path set to a folder in DAM. The initial dialog is displayed without issues, but if you search for some keyword, the results contain some internal nodes of the assets, in addition to assets themselves: How to configure pathfield so that it only displays assets in search?

Hello all, We manage our company's website in AEM, and there are two teams on which I'd like to focus here: content managers and developers. Developers create new templates and components, and content managers use both developed and out-of-the-box components ti create and update pages. Both teams use localization strings via AEM Translator: content managers manage them in the production instance, developers on dev and test ones. To minimize issues in newly developed code, developers would like a...