reading that, I wonder if the parameter is misnamed.
WHen i am doing an inplace upgrade from AEM 6.1 to 6.3 is there any guidance on how to move. Should i remove the ACS AEM Commons - Ensure Oak Index set up on 6.1 ConfigMgr before i do the inplace upgrade. Also should i remove the ACS Commons Page root provider and site map servlet set up before i do the inplace upgrade
@mediathugs_twitter in the general case, you shouldn’t need to remove anything — just install the latest 3.x package. in the specific case of Ensure Oak Index, you will likely want to review the OOTB index configuration and validate that your Ensure Oak Index configurations are still doing what you want to accomplish.
@mediathugs_twitter I would always suggest to get the application running on a plain 6.3 instance (for aem version compatibility testing of application and configuration) before performing the actual inplace upgrade. That way you should identify any necessary configuration adjustments and application adjustments to be performed along with the AEM inplace upgrade
Installing ACS common tool on prod is good idear?
@Anurag Mishra - I stalling ACS COmmons on prod is fine; just make sure you only turn on the features you want to use of course
Hello, Image drag and drop in dialog is not working if we uses ACS Commons multifield Is there any way to make it work or is it a bug?
Any target date for the release of 3.14? Especially concerning #1204. @justinedelson@davidjgonzalez
Hi I'm just setting up vanity urls in an aem instance (getting the vanity urls package from adobe, reconfiguring dispatcher version 4). Then I started thinking should I package up the vanity-urls in our code project to save admin time...? I remembered seeing a vanity paths feature in ACS commons, if we are doing redirection in our project via sling:Mapping and sling:internalRedirects is the ACS commons vanity stuff relevant or useful (will it save me some effort - we are already using some of the acs commons features)?
Can I use the ACS commons feature if the AEM 6 vanity Urls package is not installed (presumably not)?
Can anyone advise me if I can grab the vanity Urls zip package to include as a maven build time dependency (e.g. as a subpackage managed by the jcr vault maven plugin) ?
Does any one has faced issue , NullPointerException while selecting multiple pages in sites and click on properties AEM 6.3 service pack 1
Any lead would be appreciated
Hi, I have created an acl package to migrate user groups permission from aem 6.0 instance to aem 6.3 instance, i have selected Package ACL handling as "merge" but the permissions are never carried over from source to destination. Can someone help with this.
what are you trying to do?
just shift an access control file?
just create a package to the right place, and make sure the nodes are in there
its just part of the JCR
i have created a package and tried to install i was getting oakconstraint voilation so i i tried with ACL packager
Not sure what you could be doing that would create the violation... Anyone have other thoughts on this? As far as I know you could even replicate the same ACL policies per node / place using the useradmin interfact...
and btw, 6.0 ----> 6.3 is like.. jumping a few compatibility fences haha
so I do imagine you might have some problems...
A technical person who undertands the systems would break down your problem into "what needs what ACL policies set?" "can we break down the requirements into node manipulations that are system independent / able to be handled"?
Also.. It woudl be strange to think that theres no version control to manage something of this sort.. so I would recommend Github + Maven :)
but someone much wiser than me would be able to answer if there are any compatibility issues with ACL migrations from 6.0 -> 6.3, and im too busy to check / test that right now haha.. but don't over coplicate yourself.. just read through the nodes on the 6.0 in the user admin, and try to understand what its doing
i have a problem
when i upload acs-aem-coomons, have a problem
who know this error.
i need how to solve problem
does anybody know who to contact to get the new version (3.14.0) set up in a maven repo? 3.13.0 was, and it was great to just declare it in the pom versus installing the package.
Please disregard my post above asking about 3.14.0 acs-aem-commons being added to a maven repo. I just checked and it's available. Thanks to whoever takes care of that. My project is now building successfully with 3.14.0.
@nesreb for complicated reasons, it takes a day or two after the release is made before it is available on repo.adobe.com. generally, we don’t update the website until after this is done, but you will see the new release on the GitHub Releases page before it is available on repo.adobe.com
How to Generate Image renditions by using acs-commons ?
@mohankumar_m_twitter can you post your OSGi configurations (that enable Named Image Transform Servlet as well as define your transforms), along w the URL youre using to request the image resoruce to transform?
@chengxintuan need more info that that screenshot; what ACS Commons page are you trying to install and on what version of AEM; and confirming you have not made ANY changes to the acs commons package (you downloaded it from our Github releases)
acs-commons-nested I added this property still authored data is not saved in json format
@imharunpathan_twitter can you provide some more context?
Hi, I am in process of upgrading my AEM version from 6.1 to 6.3 and also updated the ACS commons package i.e. acs-aem-commons-content-3.14.0.zip