John_Ky

Re: "package file parameter missing" in package manager - Adobe Experience Manager 17-07-2019

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

4.9K

Customize/Hook to AEM copy-paste component flow - Adobe Experience Manager 27-09-2017

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

3.8K

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

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...

810

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

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.

757

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

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

754

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

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

750

Re: Update expired time for login-token cookie - Adobe Experience Manager 13-07-2017

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...

1.8K

Re: Update expired time for login-token cookie - Adobe Experience Manager 09-07-2017

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 "...

1.9K

Update expired time for login-token cookie - Adobe Experience Manager 07-07-2017

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...

5.8K

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

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.

1.8K

Likes given to

User

Count

Likes from

User

Count

Learn

Documentation

Community

Support

Resources

Adobe account

Adobe