@kautuk_sahni Sorry, i should have more clear. The rollout doesn't update the language master links if they are inside an RTE. I think that is still a common use case and remains un addressed. Can you or @Bimmi_Soi confirm this please? I can create a custom rollout action to address this but i just...
@Bimmi_Soi @kautuk_sahni Is this fixed in AEM as cloud service. Somehow i still the issue with AEM as cloud OCT 2024 SDK. Can you please confirm this with engineering ? Thanks
@kautuk_sahni Any idea why when we can expect this feature? The current permissions interface/mechanism is too complicated and there isn't detailed enough documentation to support the current way of permissions management.
My 2 cents on this topic @kautuk_sahni , @cbunchjr From a performance perspective, this might be a no-go as sorting nodes adds extra overhead and if you have a very large tree, then it may even cause the whole process to fail.
@BrianKasingli We ran into this sometime back and ended up creating a custom rollout config that updates the references inside XFs.
@Jagpreet_Singh_ It would add great value if this can be made available OOTB.
@kautuk_sahni , while this is something that can be done by overlaying the relevant jsp and customizing it, I would like to check if making this available OOTB makes sense. Please let me know. Thanks.
Request for Feature Enhancement (RFE) Summary:Enable Component level inheritance status OOTB without the need to overlay Use-case:
As a content author, MSM roll-outs is a key content authoring activity. When a content author performs a roll-out of the content from the language master to the related ...
@jeremylanssiers If you have ACS commons installed in your environment, I suggest you install/upgrade to version 6.1.0
We have added a bulk tagging feature for content pages in this milestone and that should solve your problem.
If your need is immediate, you can just head over to the ACS commons pul...
@Himanshu_Jain , you might want to add number of unused assets to above listed metrics. That will give the content team some opportunity to clean up any obsolete or junk assets sitting in the DAM.
I saw this listed as another idea as well.