Hi,
We are trying to migrate from static templates to editable templates. After migration we are facing issue.
Like when you open the page properties from migrated page you get below warning in error.log file and the page properties doesn't opens up
29.10.2020 16:14:52.409 *WARN* [212.61.155.154 [1603988092406] GET /editor.html/content/mysite/en/undefined.html/content/mysite/en/foo HTTP/1.1] com.adobe.cq.xf.impl.servlet.rendercondition.EditorRenderCondition Page at path /content/mysite/en/undefined.html/content/mysite/en/foo doesn't have a jcr:content node
But the page contains the jcr:content node.
And when we open the page from site.html it throws below error.
29.10.2020 16:17:34.385 *ERROR* [212.61.155.154 [1603988254358] GET /mnt/overlay/wcm/core/content/sites/properties.html HTTP/1.1] libs.granite.ui.components.shell.propertiespage Unable to render properties page correctly
org.apache.sling.api.scripting.ScriptEvaluationException:
at org.apache.sling.scripting.core.impl.DefaultSlingScript.call(DefaultSlingScript.java:416) [org.apache.sling.scripting.core:2.0.56]
at org.apache.sling.scripting.core.impl.DefaultSlingScript.eval(DefaultSlingScript.java:184) [org.apache.sling.scripting.core:2.0.56]
at org.apache.sling.scripting.core.impl.DefaultSlingScript.service(DefaultSlingScript.java:491) [org.apache.sling.scripting.core:2.0.56]
at org.apache.sling.engine.impl.request.RequestData.service(RequestData.java:552) [org.apache.sling.engine:2.7.2]
at org.apache.sling.engine.impl.filter.SlingComponentFilterChain.render(SlingComponentFilterChain.java:44) [org.apache.sling.engine:2.7.2]
at org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:82) [org.apache.sling.engine:2.7.2]
at com.day.cq.wcm.core.impl.WCMDeveloperModeFilter.doFilter(WCMDeveloperModeFilter.java:119) [com.day.cq.wcm.cq-wcm-core:5.12.124.CQ655-B0001]
at org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:72) [org.apache.sling.engine:2.7.2]
at com.day.cq.wcm.core.impl.WCMDebugFilter.doFilter(WCMDebugFilter.java:156) [com.day.cq.wcm.cq-wcm-core:5.12.124.CQ655-B0001]
at org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:72) [org.apache.sling.engine:2.7.2]
at com.day.cq.wcm.core.impl.WCMComponentFilter.filterRootInclude(WCMComponentFilter.java:375) [com.day.cq.wcm.cq-wcm-core:5.12.124.CQ655-B0001]
at com.day.cq.wcm.core.impl.WCMComponentFilter.doFilter(WCMComponentFilter.java:190) [com.day.cq.wcm.cq-wcm-core:5.12.124.CQ655-B0001]
at org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:72) [org.apache.sling.engine:2.7.2]
at com.day.cq.wcm.core.impl.page.PageLockFilter.doFilter(PageLockFilter.java:91) [com.day.cq.wcm.cq-wcm-core:5.12.124.CQ655-B0001]
at org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:72) [org.apache.sling.engine:2.7.2]
at com.day.cq.personalization.impl.TargetComponentFilter.doFilter(TargetComponentFilter.java:94) [com.day.cq.cq-personalization:5.12.40]
at org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:72) [org.apache.sling.engine:2.7.2]
at com.adobe.granite.csrf.impl.CSRFFilter.doFilter(CSRFFilter.java:217) [com.adobe.granite.csrf:1.0.20.CQ650-B0002]
at org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:72) [org.apache.sling.engine:2.7.2]
at org.apache.sling.engine.impl.SlingRequestProcessorImpl.processComponent(SlingRequestProcessorImpl.java:283) [org.apache.sling.engine:2.7.2]
at org.apache.sling.engine.impl.SlingRequestProcessorImpl.dispatchRequest(SlingRequestProcessorImpl.java:323) [org.apache.sling.engine:2.7.2]
Has anyone faced this issue
Solved! Go to Solution.
Views
Replies
Total Likes
The issue was caused by the modernizer tool which is used to update the static templates to editable templates. The tool moves the cq:BlueprintSyncConfig/cq:LiveSyncConfig inside the root node(responsivegrid) which causes the issue. In general the cq:BlueprintSyncConfig/cq:LiveSyncConfig should be inside the jcr:content node. Moving cq:BlueprintSyncConfig/cq:LiveSyncConfig outside root node fixed the issue.
Could you check the missing jcr:content node that the error is specifying?
Also for the pages that are showing error can you describe the node structure?
eg content/mysite/en/home/mypage/jcr:content/root/responsivegrid/mycomp
Are we able to create a new page with the editable template? If so we can compare the node structure of the new page and migrated page
Hi,
can you please post the complete stacktrace? There should be additional "caused by" blocks at the bottom of it, which give a much better insight into what the problem actually is. The part of the stacktrace you posted is not very helpful when it comes to diagnose the issue.
Thanks,
Jörg
please add the complete log this doesnt give complete info
The issue was caused by the modernizer tool which is used to update the static templates to editable templates. The tool moves the cq:BlueprintSyncConfig/cq:LiveSyncConfig inside the root node(responsivegrid) which causes the issue. In general the cq:BlueprintSyncConfig/cq:LiveSyncConfig should be inside the jcr:content node. Moving cq:BlueprintSyncConfig/cq:LiveSyncConfig outside root node fixed the issue.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies