Hi @sandeepm744005The issue is normally due to one of following 3 reasons:- tmpdir does not have enough space- tmpdir does not exist.- AEM service user does not have proper permission to tmpdirBack your case, I think it is because of permission issue. Solve it by:- Check owner and permission of tmpdir: # ls -ls- May need to update ownership to tmpdir: # sudo chown -R aem:aem $tmpdir- And may need to update read+write permission: # sudo chmod +rw $tmpdirRegards,Thanh

Customize/Hook to AEM copy-paste component flow John_Ky - Adobe Experience Manager

Hi,Anyone know how to hook to the copy-paste event in AEM? I want to create a custom code which listens to the paste event in order to modify all the children nodes' names. Appreciate if anyone know where is the client-side js and server-side for the copy-paste flow. Thanh

Re: Query issues after migrating from CQ 5.5 to AEM 6.1 John_Ky - Adobe Experience Manager

Hi,Sorry my mistake, it is not because the SP2. Actually, It was happening before the upgrading but only the log level is different after the upgrade.Before upgrade (only *WARN* throws in log):*WARN* [10.43.32.6 [1500385837727] HEAD /content/.../.html HTTP/1.1] com.day.cq.search.impl.builder.QueryImpl no PredicateEvaluator found for 'jcr:created'After upgrade (WARN and ERROR throws in log):*WARN* [10.43.32.6 [1500385837727] HEAD /content/.../.html HTTP/1.1] com.day.cq.search.impl.builder.QueryIm...

Re: Query issues after migrating from CQ 5.5 to AEM 6.1 John_Ky - Adobe Experience Manager

Error fixed. I just updated from "orderby=jcr:created" to "orderby=@jcr:created". I am not sure why it was working before the upgraded AEM 6.1 SP2.Regards.

Re: Query issues after migrating from CQ 5.5 to AEM 6.1 John_Ky - Adobe Experience Manager

I did try to create some customize oak:index for field "jcr:created", such as "ordered", "property", "lucene" but not working.

Re: Query issues after migrating from CQ 5.5 to AEM 6.1 John_Ky - Adobe Experience Manager

I am facing the same issue.Here is query details:And it throws following exception:""20.07.2017 16:15:23.699 *ERROR* [10.0.2.2 [1500531323686] GET /libs/cq/search/content/querydebug.html HTTP/1.1] com.day.cq.search.impl.builder.QueryBuilderImpl Unable to get PredicateEvaluator instance: jcr:created""It happened when I upgraded to AEM 6.1 SP2.Any solution?Regards,Thanh

Re: Update expired time for login-token cookie John_Ky - Adobe Experience Manager

Hi, My solution: Because “login-token” cookie is from OTB Token Login Module of AEM, we cannot edit the Expired/Max-age from AEM site unless creating new login module. The easiest way is using Apache Http mod_header to override the “SetCookie login-token” of “Response header” of “authentication request”. Area 1: Using Apache Http Mod_Header rewrite setcooke header of authentication response. Add this line of code to apache configuration:Header edit Set-Cookie ^(login-token.*)$ $1;max-age=9999999...

Re: Update expired time for login-token cookie John_Ky - Adobe Experience Manager

Hi Kautuk,Thanks for your answer, those of your references were talking only about token configuration at server site. but My question was about client site cookie "login-token" (Session ID).The authentication process is, AEM uses a cookie name "login-token" as a session ID which is stored on user's browser (Client site). For subsequent requests, AEM will use that cookie "session id" to query the session object under "/home/users//.token". Therefore "session expired time" is a property of node "...

Update expired time for login-token cookie John_Ky - Adobe Experience Manager

Hi,I am using AEM 6.1 and having a problem which login-token cookie is a session cookie and will automatically be cleaned when browser closed.My question is, could we update the expired time for that cookie so it will be retaining for a period of time on client site. I did a lot of searches but they were only mentioning to how to configure the server site token (under "/home/users/usernode").Furthermore, if my thing is possible to do, does it cause any security problem?Is it a good practise to d...

Re: Strange error sometimes after install a large package (embedded ACS common) John_Ky - Adobe Experience Manager

Hi,The issue can be resolved for now. Please refer the following link:https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/739"""justinedelson commented 27 minutes ago@thanhnk it sounds like you need to increase the "Number of Calls per Request" property of the Sling Main Servlet. This can happen if your project is especially large. It could just be that the component added by ACS AEM Commons pushes you over the default limit.

Re: Strange error sometimes after install a large package (embedded ACS common) John_Ky - Adobe Experience Manager

https://drive.google.com/open?id=0Bz2_P4anPfhONGRYOFpXVmI3Y0k

Re: Strange error sometimes after install a large package (embedded ACS common) John_Ky - Adobe Experience Manager

Thanks Steve Cave, kautuksahniThe strange is that if I install only my package or only acs-aem-commons-content-3.1.0.zip, the system will be OK. But when I install my package and then install acs-aem-commons-content-3.1.0.zip (order of installation doesn't impact) then the issue happened.Or If I embed the acs-aem-commons-content-3.1.0.zip in my package, error also happen.Note: The issue is on AEM 6.2 with acs-aem 3.1(AEM 6.1 with acs-aem 2.x works well).

Strange error sometimes after install a large package (embedded ACS common) John_Ky - Adobe Experience Manager

Hi,Any body got this issue(attached image) when go to localhost:4502/editor.html/somepage

Re: Sling Model API update to v1.2.2 (AEM 6.2) Not support @Inject anymore John_Ky - Adobe Experience Manager

Thanks for your answer.Sling Model API version 1.2.2 have removed the package "javax.inject" so that is the reason my code does not work any more.I just tried to add: javax.inject javax.inject and it works well now.

Sling Model API update to v1.2.2 (AEM 6.2) Not support @Inject anymore John_Ky - Adobe Experience Manager

AEM 6.2 uses Sling Model API 1.2.2, but this bundle seems not include @Inject annotation. So how to I inject some of sightly object inside Sling Model?Old version look like: @Model(adaptables = Resource.class) public class HelloWorldModel { @Inject private SlingSettingsService settings; @Inject @Named("sling:resourceType") @Default(values = "No resourceType") protected String resourceType; private String message; @PostConstruct protected void init() { message = "\tHello World!\n"; message += "\t...

Re: How to add multiple groups at Participant Step. John_Ky - Adobe Experience Manager Forms

Hi,I found a simple solution,Only create a container group which contain multiple groups after that assign the container group into participant step.Thanks anyway.

How to add multiple groups at Participant Step. John_Ky - Adobe Experience Manager Forms

Hi,I wonder in case that I have more than one approver groups, only one of them do the approve can lead the workflow go to the next step. But in Participant Step, I only can set 1 group/user.Is there any way to reach that spec? (I have also tried to use "And Split" for multiple Participant Step, but it has to get all the participant approval before move to next step.)Thank you.John

Re: Purge users under /home and copy protected nodes John_Ky - Adobe Experience Manager

Thanks so much for your help.I will try to suggest the client try to not use email as the username.Best regards,John

Re: Purge users under /home and copy protected nodes John_Ky - Adobe Experience Manager

Hi samthadhani Below is my original question, is it similar to yours?Thank you samthadhani . """" How to change login username with carry all relevant data of that user?Currently I want to allow the users can update their username (default is email), but when tried to research for some documents and forum topics I have not find out yet how to implement it.The adobe CQ system do use the username for creating a node under /home/users/** and other places under /content/usergenerated/**.Programmatic...