AEM 5.6.1 currentPage object is null on publish server.

[Damian_Manifold]

Hi,

I hope you can help.

We are currently in the middle of upgrading from 5.4 to 5.6.1 and its all gone quite smoothly with the testing in the authoring environment. However, when the components are deployed to the publish server there are a lot of exceptions thrown. On referring back to the code all the lines in question seem to be using currentPage in some way.

Has anybody had an experience like this? Or know why currentPage appears to be null.

Regards

Damian.

[Feike_Visser1]

Are you using getTemplate()?

[Damian_Manifold]

Yes, it seems to complain about that in most cases. However it does seem to complain about pageHelper.getClasses(currentPage). Which is why i moved my investigation from templates to the currentPage object.

[Feike_Visser1 · Accepted solution]

Yes, getTemplate() shouldn't be used anymore on publish since 5.5...

use getProperties().get("cq:template","")

[Damian_Manifold]

Thanks, I'll update that. It does work in our auth environment though, and there is the other issue so I'm not sure it's the root cause.

[Sham_HC]

That is the cause & agree with Feike.  http://blogs.adobe.com/livecycle/2012/06/developers-faq-on-cq5-5.html

[Damian_Manifold]

Ahh, I see its down to being an anonymous user which explains why it works in auth.

Thanks alot guys.