Thank you. I will have a look at this AEM Jenkins plugin.

hi Jörg,Thank you for the help and for pointing me in the correct direction. I found the problem and it is what you have mentioned related to having the right permissions. The group everyone was not having the read permissions for the editable templates, and this is the reason why the page looked go...

Hi Jörg, Thank you for your answer. You are right, I am not logged in in CRX on the system where I see the problem. So what I realise now is that I do not even need to recompile JSPs. As soon as I log in into CRX the site looks fine. If I log out of it, the header of the page is gone.So I am with ad...

I am using the admin user. And definitely I am accessing the same address in both browsers (I use copy paste for both the address and for CRX). I still can see the same differences in CRX.

I am debugging for the source of the problem using 2 browsers. In one I run the recompile all JSPs and everything is fine, in the other one not, and header is not displayed.A strange thing I realised is when I log in CRX with both browsers. The one when everything is running looks fine and has all t...

After the deployment the problem appears, and it does not get fixed with a publish of a page.If I do a recompile JSP in that browser the site works correctly. If I do some changes to the content and publish them, the header is again not visible, and in the logs again the *INFO* and *WARN* messages f...

We are not in an early phase of the project so a switch now to AEM 6.4 is not an immediate option. Of course we want to migrate it also to 6.4 but we want to do with without the time pressure that we currently have for the implementation. I had a look to the logs of the publish instance, and I see f...

Hi all,Our company is developing the first AEM project with the AEM 6.3 version of Adobe Experience Manager. We created our project based on the Maven archetype version 12.We encounter a problem on our test machine. We deploy the project on both author and publish instances via a Jenkins job (that j...