Hey Everyone,My name is Geoffrey McIntyre. I am the lead AEM developer for a large company in Australia. I look forward to seeing the community grow and hopefully become a great resource for the occasional pains we all have.RegardsGeoff

I am getting the exact same issue (behaviour and JS error).AEM 6.2 SP1 - Touch UI

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?

I actually solved this just before going away for the weekend. The issue was that I was referencing the class directly (data-sly-use.headjava="Head") and instead had to include the package (data-sly-use.headjava="apps.site.components.page2017.global.head.Head").I am unsure at this point as to why I ...

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...

Does anyone know why a HTL template would be working fine on Author but on Publisher it throws the error "Arguments cannot be null"? The publisher has no issues running JSP templates.Is there any way that I can get a bit more information i.e. a Publisher error log?Edit 1: I have further narrowed thi...

I just copied the second template component which doesn't work into the same directory as the one that does work. I then copied the template of the one that doesn't work to the same directory as the rest and pointed it at the new copy of the template component and it works fine.It is definitely some...

I completely agree that it shouldn't be a div in the head. This was just the last template from example sites I tried before figuring out the fact that it is having issues with the template component being in a sub-directory. Both templates are the same except for the directory their component is in...

It is really basic, two templates in the template directory (/apps/site/templates), two components in the component page directory (/apps/site/components/page) but one is in a sub-directory. (/apps/site/components/page/2017). The components have resourceSuperType: wcm/foundation/components/page and ...

Awesome, making progress. So now this allows one of my template components in the directory (/apps/site/components/page/) to continually be updated with no issues. My other template in (/apps/site/components/page/2017/) though won't compile and when I do try to update and compile it, it also causes ...