You don't need to use CUG here, as they are for pages that need login. You can use AccessControlUtils.getAccessControlList(adminSession, path) to get the ACL instead. //Create your adminSession using a mapped service user Map<String, Object> param = new HashMap<String, Object>(); param.put(ResourceR...

Refer to comment above for a fix.

@srig786, did you get this working?

Hi guys,We've done an in-place upgrade from AEM6.4 to AEM6.5. We've seen a problem with not being able to create a new page. We see this when using the create page wizard:Error:java.lang.UnsupportedOperationException: create 'content' at /mnt/overlay/wcm/core/content/sites/createpagewizardAnd here's...

I tried purging these workflows from the JMX console but the console does not give you a success message, so I doubt it worked. When we tried again and used the correct model ID for the workflow and did the purge, the pageInfo.json started showing and the Pages became editable. So the solution is to...

I tried purging these workflows from the JMX console but the console does not give you a success message, so I doubt it worked. When we tried again and used the correct model ID for the workflow and did the purge, the pageInfo.json started showing and the Pages became editable. So the solution is to...

We did an in-place upgrade to 6.5 from 6.4.2. The pages are now not edit-able (even as an admin). I'm seeing this error:Internal Server ErrorCannot serve request to /libs/wcm/core/content/pageinfo.json in com.day.cq.wcm.core.impl.servlets.PageInfoServletException:java.lang.NullPointerExceptionThis i...

Hi @anurag-wyndham / @sreedobe , I'm seeing the same issue after an in-place upgrade to AEM6.5. Do either of you remember what you did to fix it?

Thanks Arun, I gave that a try. It didn't help. javax.servlet.jsp is still using org.apache.sling.scripting.jsp-api.

AEM 6.5 has two OSGi bundles (A and B). A = org.apache.sling.scripting.jspB = org.apache.sling.scripting.jsp-api My project bundle has a Java class that uses:import javax.servlet.jsp.PageContext;   I want this imported package to use OSGI bundle A, not B. In AEM 6.4, this was our imported packages l...