Esta conversación ha sido bloqueada debido a la inactividad. Cree una nueva publicación.
Nivel 1
Nivel 2
Iniciar sesión en la comunidad
Iniciar sesión para ver todas las insignias
Esta conversación ha sido bloqueada debido a la inactividad. Cree una nueva publicación.
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.
¡Resuelto! Ir a solución.
Vistas
Respuestas
Total de me gusta
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.
Vistas
Respuestas
Total de me gusta
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.
Vistas
Respuestas
Total de me gusta
Going directly to the header/footer experience fragment works.
Vistas
Respuestas
Total de me gusta
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
Vistas
Respuestas
Total de me gusta
How do I check that? CRX only shows /content on the publish instance.
Vistas
Respuestas
Total de me gusta
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
Vistas
Respuestas
Total de me gusta
That didn't seem to have an effect.
Vistas
Respuestas
Total de me gusta
@wizard04wsu Can you check if cq:allowedTemplates' is defined on root with proper value like /conf/<root>/settings/wcm/templates/.*
Vistas
Respuestas
Total de me gusta
The value I have there is like /conf/<root>/settings/wcm/templates/page-(.*)
Vistas
Respuestas
Total de me gusta
@wizard04wsu Check if it is configured the same in publish as Author instance, if something is missing please add and validate.
Vistas
Respuestas
Total de me gusta
Root configuration is the same on both instances.
Vistas
Respuestas
Total de me gusta
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.
Vistas
Respuestas
Total de me gusta
Vistas
me gusta
Respuestas
Vistas
me gusta
Respuestas
Vistas
me gusta
Respuestas