Page is blank in edit mode | Community
Skip to main content
J
janhavi_singh
Level 3
September 10, 2021
Solved

Page is blank in edit mode

  • September 10, 2021
  • 5 replies
  • 5661 views

Hello to all the AEM community members

 

I am working on my own site in aem and inside the particular site, whenever I try to open the child pages in editor the page appears to be blank.

Additionally, when I tried to inspect the page, I found that the body tag has components inside it, but these components are not getting rendered on the page.

I have already checked the error log file and got this error:Probably misconfigured as it ends with '/settings' , I have searched for this error but could not find ways to solve it.

 

 

Can anyone help me with this problem?

Thank you!!

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Rohit-Negi

Hi @janhavi_singh ,

 

Your editable template doesn't seems to be configured properly. Try creating a new template from scratch and check. Try following this link:http://www.sgaemsolutions.com/2017/09/dynamic-editable-templates-in-aem-63.html

 

The error you are highlighting is a warning but not an error and there was jira open for this https://issues.apache.org/jira/browse/SLING-8637 so that won't be any issue.

 

Thanks

5 replies

K
KirtiA
Level 2
September 10, 2021

Hi @janhavi_singh ,
Could you please check the editable template structure again for this page and make sure policies and other configurations are good.
Please check below article :
https://experienceleague.adobe.com/docs/experience-manager-65/developing/platform/templates/page-templates-editable.html?lang=en

Hope it helps!

Thank you

    Rohit-Negi
    Rohit-NegiAccepted solution
    Level 3
    September 10, 2021

    Hi @janhavi_singh ,

     

    Your editable template doesn't seems to be configured properly. Try creating a new template from scratch and check. Try following this link:http://www.sgaemsolutions.com/2017/09/dynamic-editable-templates-in-aem-63.html

     

    The error you are highlighting is a warning but not an error and there was jira open for this https://issues.apache.org/jira/browse/SLING-8637 so that won't be any issue.

     

    Thanks

      Anny0505
      Community Advisor
      Anny0505Community Advisor
      Community Advisor
      September 10, 2021

      @janhavi_singh,

      1. First check would be your template. Please navigate to templates and view/Edit the template that you have used to create a page. When you open the template in Edit mode, it should list container and any added components. Then add allowed components and configure policies correctly.  You could refer we-retail templates in case if you have any doubts and also follow documentation to create a templates as mentioned in below posts.

      2. Re-Create a page and add OOTB components  first and see how things are working.

      3. Then add your custom component and see how things working.

       

       

       

        Asutosh_Jena_
        Community Advisor
        Asutosh_Jena_Community Advisor
        Community Advisor
        September 10, 2021

        Hi @janhavi_singh 

         

        The issue is in the next line in ERROR log where it says no renderer found with html extension.

         

         

         

        I believe you are running AEM 6.5.X version with Java 11.

         

        So for this you need to ensure you have the below line added into the sling.properties file.

         

        Look for sling.bootdelegation.sun=sun.*,com.sun.* and replace it with 

        sling.bootdelegation.sun=sun.*,com.sun.*,jdk.internal.reflect,jdk.internal.reflect.*
         
        Now start the instance and you should be able to see all the content and all the pages will render perfectly fine.
         
        Here is an article talks about the same:
         
        Thanks!
          Manu_Mathew_
          Community Advisor
          Manu_Mathew_Community Advisor
          Community Advisor
          September 12, 2021


          Hi  @janhavi_singh 

           

          Might be the component you are using is probably overlayed which was moved or removed after installing service pack.

          Please check your overlays in apps and sync to the changes done by SP in libs.

           

           

           
            Terms & ConditionsAccessibility statement

            Loading footer...