Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

geoffreym935937
geoffreym935937
Offline

Badges

Badges
9

Accepted Solutions

Accepted Solutions
1

Likes

Likes
2

Posts

Posts
13

Discussions

Discussions
11

Questions

Questions
2

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by geoffreym935937
Customize the badges you want to showcase on your profile
Re: [New] Welcome to AEM Community! Please Introduce Yourself
Avatar
Give Back 10
Level 2
geoffreym935937
Level 2

Likes

2 likes

Total Posts

13 posts

Correct reply

1 solution
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Ignite 3
View profile
geoffreym935937
- Adobe Experience Manager
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

Views

13.8K

Like

1

Replies

0
Re: touch ui page not getting refreshed on adding new component
Avatar
Give Back 10
Level 2
geoffreym935937
Level 2

Likes

2 likes

Total Posts

13 posts

Correct reply

1 solution
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Ignite 3
View profile
geoffreym935937
- Adobe Experience Manager
I am getting the exact same issue (behaviour and JS error).AEM 6.2 SP1 - Touch UI

Views

8.3K

Like

1

Replies

0
Possible to use components in sub-folders of the components directory?
Avatar
Give Back 10
Level 2
geoffreym935937
Level 2

Likes

2 likes

Total Posts

13 posts

Correct reply

1 solution
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Ignite 3
View profile
geoffreym935937
- Adobe Experience Manager
Is it possible to use components in sub-folders of the components directory? /apps/site/components/newComponents/sampleComponentWhen I try to drop a component that is located anywhere other than directly in the components folder (/apps/site/components/sampleComponent), it causes the browser tab to lock-up and the page will continue to lock up until I remove the component from the par on that page using crxde.

Views

393

Likes

0

Replies

2
Re: HTL/Sightly templates (page) and components not compiling/rendering
Avatar
Give Back 10
Level 2
geoffreym935937
Level 2

Likes

2 likes

Total Posts

13 posts

Correct reply

1 solution
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Ignite 3
View profile
geoffreym935937
- Adobe Experience Manager
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?

Views

569

Likes

0

Replies

0
Re: HTL Template on Publisher throws error "Arguments cannot be null"
Avatar
Give Back 10
Level 2
geoffreym935937
Level 2

Likes

2 likes

Total Posts

13 posts

Correct reply

1 solution
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Ignite 3
View profile
geoffreym935937
- Adobe Experience Manager
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 need this reference on Publisher and not on Author, do you know what would be missing on the Publisher to cause this?Also, as I said in my original question "Is there any way that I can get a bit more...

Views

363

Likes

0

Replies

0
Re: HTL/Sightly templates (page) and components not compiling/rendering
Avatar
Give Back 10
Level 2
geoffreym935937
Level 2

Likes

2 likes

Total Posts

13 posts

Correct reply

1 solution
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Ignite 3
View profile
geoffreym935937
- Adobe Experience Manager
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).

Views

569

Likes

0

Replies

2
HTL Template on Publisher throws error "Arguments cannot be null"
Avatar
Give Back 10
Level 2
geoffreym935937
Level 2

Likes

2 likes

Total Posts

13 posts

Correct reply

1 solution
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Ignite 3
View profile
geoffreym935937
- Adobe Experience Manager
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 this down to the inclusion of a Java file in my template component. The file can be empty and it still throws the error.

Views

428

Likes

0

Replies

2
Re: HTL/Sightly templates (page) and components not compiling/rendering
Avatar
Give Back 10
Level 2
geoffreym935937
Level 2

Likes

2 likes

Total Posts

13 posts

Correct reply

1 solution
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Ignite 3
View profile
geoffreym935937
- Adobe Experience Manager
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 something to do with having a page component in (/apps/site/components/page) vs (/apps/site/components/page/2017).

Views

1.9K

Likes

0

Replies

0
Re: HTL/Sightly templates (page) and components not compiling/rendering
Avatar
Give Back 10
Level 2
geoffreym935937
Level 2

Likes

2 likes

Total Posts

13 posts

Correct reply

1 solution
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Ignite 3
View profile
geoffreym935937
- Adobe Experience Manager
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, but only one of them works. I made the suggested change and it is the same result.

Views

1.9K

Likes

0

Replies

0
Re: HTL/Sightly templates (page) and components not compiling/rendering
Avatar
Give Back 10
Level 2
geoffreym935937
Level 2

Likes

2 likes

Total Posts

13 posts

Correct reply

1 solution
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Ignite 3
View profile
geoffreym935937
- Adobe Experience Manager
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 the templates are pointing to their corresponding component.Both template components are basic HTL: Simple Page Component Using Sightly 20 You can add components below I can reproduce this in a f...

Views

1.9K

Likes

0

Replies

3
Re: HTL/Sightly templates (page) and components not compiling/rendering
Avatar
Give Back 10
Level 2
geoffreym935937
Level 2

Likes

2 likes

Total Posts

13 posts

Correct reply

1 solution
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Ignite 3
View profile
geoffreym935937
- Adobe Experience Manager
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 the other template to stop compiling.Upon further investigation it is definitely being caused by having the template component in a sub-directory of page.

Views

1.9K

Likes

0

Replies

5
Re: HTL/Sightly templates (page) and components not compiling/rendering
Avatar
Give Back 10
Level 2
geoffreym935937
Level 2

Likes

2 likes

Total Posts

13 posts

Correct reply

1 solution
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Ignite 3
View profile
geoffreym935937
- Adobe Experience Manager
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.

Views

1.9K

Likes

0

Replies

7
HTL/Sightly templates (page) and components not compiling/rendering
Avatar
Give Back 10
Level 2
geoffreym935937
Level 2

Likes

2 likes

Total Posts

13 posts

Correct reply

1 solution
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Ignite 3
View profile
geoffreym935937
- Adobe Experience Manager
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?

Views

2.8K

Likes

0

Replies

12
Likes from