"page has no template assigned" error on publish instance | Community
Skip to main content
New Participant
May 20, 2022
Solved

"page has no template assigned" error on publish instance

  • May 20, 2022
  • 5 replies
  • 2824 views

I'm using editable templates with the header and footer as experience fragments. On author this works as expected, but on publish the header and footer are missing. In the publish log, I see this:

19.05.2022 17:01:30.302 *INFO* [127.0.0.1 [1652994090260] GET /home HTTP/1.1] com.day.cq.wcm.foundation.TemplatedContainer page has no template assigned 19.05.2022 17:01:30.302 *WARN* [127.0.0.1 [1652994090260] GET /home HTTP/1.1] com.day.cq.wcm.foundation.TemplatedContainer template has no structure support

I believe the template permissions are set up so that 'everyone' has read privileges, but I must be missing something.

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

SOLVED:

My template at "/conf/<root>/settings/wcm/templates/page-basic/initial" was missing the fragmentVariationPath property on the experience fragments. I'm not sure why it still worked on the author instance, though.

 

Thanks for your suggestions.

5 replies

wizard04wsuAuthorAccepted solution
New Participant
May 23, 2022

SOLVED:

My template at "/conf/<root>/settings/wcm/templates/page-basic/initial" was missing the fragmentVariationPath property on the experience fragments. I'm not sure why it still worked on the author instance, though.

 

Thanks for your suggestions.

Bhuwan_B
New Participant
May 23, 2022

@wizard04wsu Can you check if cq:allowedTemplates' is defined on root with proper value like /conf/<root>/settings/wcm/templates/.*

New Participant
May 23, 2022

The value I have there is like /conf/<root>/settings/wcm/templates/page-(.*)

Bhuwan_B
New Participant
May 23, 2022

@wizard04wsu Check if it is configured the same in publish as Author instance, if something is missing please add and validate.

B_Sravan
New Participant
May 21, 2022

Check these.

1. Replicate your content tree and as well as the conf from the distribution.

2. If issue still exists, please install your content package which has the conf filter.

3. if you already have a content package on author, please replicate the package

 

New Participant
May 23, 2022

That didn't seem to have an effect.

RajaShankar
New Participant
May 20, 2022

Hi @wizard04wsu 

Could you please check whether your editable template with policy has got replicated to publisher properly. 

I had faced same kind of issue when my latest editable template policy didnt get replicated properly to publisher.

 

Regards,

Rajashankar.R

New Participant
May 20, 2022

How do I check that? CRX only shows /content on the publish instance.

DEBAL_DAS
New Participant
May 20, 2022

As you have implemented header and footer using experience fragments, could you please give a try to access header and footer specific experience fragments directly from publish instance and check the response.

New Participant
May 20, 2022

Going directly to the header/footer experience fragment works.