Hi every one
I have doing a project migrate a content from AEM 6.1 to 6.5. According to best practice we have moved the libraries from etc to apps, but we meet some issue, we cannot find the templates created at 6.1, and we and cannot find the component when edit the old content page at edit mode.
any one meet this issue?
Please check the upgrade.log to make sure the upgrade was success and there was no issue after upgrade.
Refer the below article to identify the post upgrade checks:
the old content is look good and can publish to the publish server, that mean this old content pages can find the component at 6.5, but when you want create a new page, you will find no template can be selected
@josieqqiu If the templates are not visible to create new page, please ensure that you have the cq:allowedTemplates are configured with the new path referencing to /conf.
I believe you have already migrated from static to editable template.
<?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0" jcr:primaryType="cq:Template" jcr:title="RWD Generic Page with Key Visual" allowedPaths="[/content/xxx/abc(/.*)?]"> <jcr:content cq:designPath="/apps/abc/clientlibs/pws/common/rwd-templates/rwd-genericPage-withKeyVisual" cq:deviceGroup="[mobile/groups/responsive]" jcr:primaryType="cq:PageContent" sling:resourceType="/apps/abc/pws/common/components/structure/rwd-genericPage"> <keyVisual jcr:primaryType="nt:unstructured" sling:resourceType="foundation/components/parsys"/> <Content jcr:primaryType="nt:unstructured" sling:resourceType="foundation/components/parsys"/> </jcr:content> </jcr:root>
@josieqqiu I see the allowedPath property is set to
allowedPaths="[/content/xxx/abc(/.*)?]" which will allow the template to be available only under /content/xxx/abc.
It is better to use the cq:allowedTemplates property which can be added directly on the root page jcr:content node under which you wanto your template to be available or you can open the root page and go to the page properties section under "Advanced" tab you will find the Template setting where you can allow the static template to be available. Just configure the path of your template from apps folder and it will appear in the page creation wizard.
@josieqqiu Are you trying to say you are not able to see your components which all are part of your component group?
If that is what you meant then you will need to go to design mode of the page and then enable the component group to see the components available on the parsys. Please note that the design mode is only available for the static template in AEM 6.5 and it will not be avaialble for editable template as it will be managed by template policy.
Please refer the adobe link here:
Hope this helps!
@josieqqiu The above response is for static template only 🙂
you will need to go to design mode of the page and then enable the component group to see the components available on the parsys.
but one thing is really: before libraries is put at etc, these component can search at contentpage , after move to apps , the component cannot search.