HTL/Sightly templates (page) and components not compiling/rendering | Community
Skip to main content
geoffreym935937
geoffreym935937
Level 2
February 22, 2017

HTL/Sightly templates (page) and components not compiling/rendering

  • February 22, 2017
  • 2 replies
  • 5357 views

When I create a new HTL template (page)/component or edit an existing one, it does not compile/render. The page just gets stuck perpetually loading. Switching to "Development Mode" in "Apache Sling Scripting Sightly Engine Configuration" worked to render it once, but not again.

Does anyone know why this would be occurring?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
February 22, 2017

Any error in error.log or browser console?

~kautuk

Kautuk Sahni
geoffreym935937
geoffreym935937Author
Level 2
February 22, 2017

I can't see anything in the error.log and there is nothing in console.

I came in this morning and both test templates compiled. I made a change to one which it compiled again, and then I made another change to it and it stopped compiling.

Var
Var
Level 4
February 23, 2017

Geoffrey McIntyre wrote...

I can't see anything in the error.log and there is nothing in console.

I came in this morning and both test templates compiled. I made a change to one which it compiled again, and then I made another change to it and it stopped compiling.

 

can you try restarting Apache Sling Scripting Sightly Engine (org.apache.sling.scripting.sightly) bundle.?

~ VAr

geoffreym935937
geoffreym935937Author
Level 2
March 16, 2017

This was not solved, creating a sub-directory "2017" in the component sub-directory "page" (/apps/site/components/page/2017) still causes the compiler to crash.

I simply worked around this issue by creating a new single level component sub-directory for my components "page2017" (/apps/site/components/page2017).

Feike_Visser1
Adobe Employee
Feike_Visser1Adobe Employee
Adobe Employee
March 17, 2017

Are you using AEM6.1 or AEM6.2?

Can share you a code-package where we can see the issue?

geoffreym935937
geoffreym935937Author
Level 2
March 20, 2017

I am using AEM 6.2. I will make a package as soon as I get a chance, but I assume that means you cannot reproduce it simply by having the template component two sub-directories deep in the components directory, as described above?

Terms & ConditionsAccessibility statement

Loading footer...