"page has no template assigned" error on publish instance | Community
Skip to main content
wizard04wsu
Level 2
May 20, 2022 5:42 PM UTC
Solved

"page has no template assigned" error on publish instance

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.
wizard04wsuAccepted solution
Level 2
May 23, 2022 6:06 PM UTC

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.

View reply

11 replies

wizard04wsuAuthorAccepted solution
Level 2
May 23, 2022 6:06 PM UTC

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.

Translate
    Bhuwan_B
    Bhuwan_B
    New Participant
    May 23, 2022 11:15 AM UTC

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

    Translate
      wizard04wsuAuthor
      Level 2
      May 23, 2022 12:41 PM UTC

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

      Translate
        Bhuwan_B
        Bhuwan_B
        New Participant
        May 23, 2022 12:58 PM UTC

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

        Translate
          B_Sravan
          B_Sravan
          New Participant
          May 21, 2022 9:33 AM UTC

          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

           

          Translate
            wizard04wsuAuthor
            Level 2
            May 23, 2022 1:54 PM UTC

            That didn't seem to have an effect.

            Translate
              RajaShankar
              RajaShankar
              New Participant
              May 20, 2022 6:43 PM UTC

              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

              Translate
                wizard04wsuAuthor
                Level 2
                May 20, 2022 6:51 PM UTC

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

                Translate
                  DEBAL_DAS
                  DEBAL_DAS
                  New Participant
                  May 20, 2022 6:24 PM UTC

                  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.

                  Translate
                    wizard04wsuAuthor
                    Level 2
                    May 20, 2022 6:48 PM UTC

                    Going directly to the header/footer experience fragment works.

                    Translate
                      Terms & ConditionsAccessibility statement

                      Loading footer...