AEM 6.3 | MSM Extended | JCR Properties Rollout


AEM OOB excludes certain properties like jcr:title, jcr:description, cq:designPath in live copy content rollout and update. These properties are configured and controlled by OSGi configuration and can be modified accordingly. 

 Step 1: Go to Configuration Manager
Search for CQ MSM Content Update Action

 Step 2: Open the OSGI configuration and it is as below snapshot.
com.day.cq.wcm.msm.impl.actions.ContentUpdateActionFactory

Step 3: Override in application level OSGi folders(runmodes) as below.
com.day.cq.wcm.msm.impl.actions.ContentUpdateActionFactory.config and do the modifications as needed in Excluded Page Properties.

 Ex: By default jcr:.* is excluded and if a requirement is to enable jcr title and description, we have below expression to be 
jcr:(?!(title|description)$).*

                     

Step 4: Content ready for Rollout.

Comments

Post a Comment

Popular posts from this blog

AEM 6.3 | Apache Sling Content Disposition Filter | Hosting Static HTML in JCR

Image
In AEM 6.2 and 6.3, when we attempt to hit the static content such as (/content/site/static-page.html), it is treated as a binary download and does the same for all other file types(pdf,css, js, images) where r esponse header shows Content-Disposition as an attachment. In previous versions of AEM (6.1 and below),  com.day.cq.dam.core.impl.servlet.SafeBinaryGetServlet  was there to control response header to render page instead of download.  However from 6.2, this component is  deprecated and t he reason is Apache Sling Content Disposition Filter(org.apache.sling.security.impl.ContentDispositionFilter) took precedence and an intended change made in product from AEM 6.2 onward and was introduced as part of Sling Security Fix. Here we have steps to render static pages: Apache Sling Content Disposition Filter Configuration where static files needs to be added to meet requirements. Configuration can be reverted back to render static pages without adding it manually in OSGI by u
Read more

Image Component Customization - Image Size Restriction - Drag/Drop - Touch UI

Image
Customization of Image component or file upload resource type drag and drop from content/asset finder and restrict it to 1 MB or to any size. Step 1 : Create a AEM Image Component or use file upload resource type to drag and drop images in Touch UI dialog. Step 2 : Create Client library in your project application structure or inside component. Use categories as  cq.authoring.dialog or add extra clientlibs as needed . Step 3: Create a js file and add below piece of code which talks about file upload functions and accommodate for drag and drop behavior for coral classes from Content/Asset finder. As the page div for drag and drop creates on run time and becomes messy to retrieve the image size, hence a ajax call is used to get the image size post adapting resource to Asset. (function($, $document, ns) {     var FILE_UPLOAD_SELECTOR = ".cq-dialog .cq-FileUpload"; function imageSizeValidation(widget, elementName, imageSize, operation) {         if (widget &
Read more

ACS Commons Sitemap Servlet extension to support Multiple Languages Domain

Image
ACS Commons provides OSGI Sitemap config service to generate sitemap xml file which is used by web crawler to optimize web search results. The provided sitemap servlet takes input from externalizer configuration which acts as domain to the list of content pages. This hosted configuration would have a root domain to the list of locales available for an application. This remains constant for applications having more than one domain and the purpose of multiples domains is not achieved. This can be achieved via switching externalizer domain config to page properties values. Example shown below: From externalizer setting : Code from :  String loc = externalizer.externalLink(resolver, externalizerDomain,  String.format("%s.html", page.getPath()));  writeElement(stream, "loc", loc);        New Page properties Config value to be taken from each country landing page:    Code to :               Resource resource = request.getResource();      
Read more