badvision on Renovator_bugfixes
#1737 - Added additional asset … (compare)
masterthat I am waiting for. I have decide whether I create my own build of
masteror wait. There is a milestone 4.2.2 but is has no release date yet and only 4 of 10 tickets are done for that milestone. I don't want to push, just would like to know so that I can plan our sprint :)
I am an AEM support consultant and I am working on an issue raised by WYNDHAM WORLDWIDE OPERATIONS, INC.
They are trying to publish some property-overview pages to Preview environment by using Bulk Workflow Manager, but they are not getting the updated content on Preview environment and also would like to see whether the content structure is created on Preview publisher environment or not.
Can you please let me know how they can get this issue addressed by the ACS team?
I'm new to using ACS Commons in a project and was wondering if there's way I can restrict/filter what I want to install from ACS Commons.
For example, I want to install the OSGi bundle & certain resources under '/var/acs-commons/reports', but not other resources such as : '/apps/cq/core/content/nav/tools/acs-commons'. Is there a way to do this?
I'm installing ACS Commons via maven as a subpackage. I think the best would be if such filters could be added under the maven POM tag where one can specify what to path(s) to install from the subpackage. Kind of like a way to override the filters specified in the ACS Commons package itself.
I migrated the project I'm working on from version 6.2 to version 6.5 of AEM. So I installed the the acs commons v. 4.3.2, previously v. 3.6.2.
Unfortunately, I found a bug in saving and showing the data of the multifield fields of type acs-commons-nested = "JSON_STORE" in page properties.
Do you also find bugs in this regard? In case what you did to solve them?
@sathish-git Hello Sathish, apologies for my late response.
There are certain things installed with ACs Commons package that effects the UI, for example : '/apps/cq/core/content/nav/tools/acs-commons'. This adds new options for authors/admins who don't need to have access to such options(in the current project at least).
I guess for this specific scenario I could remove read rights for the user groups that shouldn't be able access the mentioned options, but there could be more things like this that gets installed with ACS Commons that I might not be aware of.
Yeah, modifying filters & building ACS Commons separately does seem like a 'hacky' way, probably better to not go that way. :)