Hi @grandhip ,   I don't believe it's possible. In MSM, you have the option to break the inheritance of a specific page property in live copies to prevent it from being updated during the rollout of the master copy and its page properties. However, rolling out individual properties is not feasible. ...

Hi all,   For the input image, we are generating a CMYK Tif DM rendition. The following image presets are created for this purpose.   It's all working fine. However, DM is reducing the rendition's width and height.   Is there a way we can preserve the original width and height? Can anyone tell me ...

After an extensive process of debugging and thorough searching, I'm Concluding this matter with a resolution. Enabling the download attribute isn't feasible, as it was being removed on Google SMTP's end. The available options are to either utilize an alternative SMTP service or directly rename files...

I have already checked, including testing on various browsers and email platforms such as Outlook and Gmail. It appears that the removal of the download attribute might be occurring at the SMTP level.

Hi   We are using asset share commons default email template     and EmailShareServiceImpl.java for sending assets links for download.   However, after sharing an asset via email, the download attribute within the anchor tag links is being eliminated. But other attributes like href, alt are allowe...

[FIXED]   The problem has been solved by adding a resource map configuration within /etc/map.publish.dev for the secondary development environment.

Hi,   I am reaching out regarding an issue we are experiencing with sending assets via email. Unfortunately, we are encountering a CORS problem in console, which prevents us from successfully mailing the assets. We are using asset share commons for assets management but in author email service is wo...

Hello everyone,  [FIXED] Above issue is resolved. For local we dont need to use any scheme. <unique-name> [scheme://]server[:port][/contextpath] Instead of local $[env:AEM_EXTERNALIZER_LOCAL;default=http://localhost:4502] we can directly use local http://localhost:4502        

Hi @James_shan ,   Seems the port is already in used. You can try this command to kill the port lsof -t -i tcp:4502 | xargs kill -9  

Seems it is not properly registered. Could you pleas check the required bundle or package containing the com.day.cq.replication.ReplicationTransaction interface is correctly installed and active in your AEM instance. You can also try obtaining a reference to the ReplicationTransaction service using ...