Hi guys,
I've created some landing pages for a campaign using CQ5.6. These are using a custom canvas page template and are sitting underneath a campaign in /content/campaigns.
The Landing Page documentation says that "You can publish the landing page and all its dependencies just like publishing a normal page. ". But I am experiencing issues with that. We've discovered that while you do actually publish the page the created page component (under /apps/CampaignName ) is not published and the only way to do so is via “Activate Tree”. This is not ideal since we want our client to manage this end to end by themselves.
Is there another way to publish a landing page or should I be going about this in another way?
Any help is very much appreciated!
Thanks :)
Alex
Solved! Go to Solution.
That's not the expected behavior according to the documentation on landing pages: http://dev.day.com/docs/en/cq/5-6/wcm/campaigns/landingpages.html#Publishing a landing page
In fact in the particular case of the landing page implementation I'd expect that an automated workflow will trigger off the back of the ZIP extraction to push all the required nodes (from both under /apps/.../components/canvaspage/* and under /etc/designs/canvaspage/content/campaigns/*). Otherwise it's a very misleading functionality which would expect campaign managers to either understand the process of deploying packages or having them talking to someone that can do that for them which, to be honest, defeats the purpose
Views
Replies
Total Likes
In addition to publishing the pages, the application/component that renders the page content must also be deployed to the publish instance. As Sham indicates, publishing apps are done using packages:
http://dev.day.com/docs/en/cq/current/administering/package_manager.html
scott
Views
Replies
Total Likes
anything below /apps published generally through packages as a best practice.
That's not the expected behavior according to the documentation on landing pages: http://dev.day.com/docs/en/cq/5-6/wcm/campaigns/landingpages.html#Publishing a landing page
In fact in the particular case of the landing page implementation I'd expect that an automated workflow will trigger off the back of the ZIP extraction to push all the required nodes (from both under /apps/.../components/canvaspage/* and under /etc/designs/canvaspage/content/campaigns/*). Otherwise it's a very misleading functionality which would expect campaign managers to either understand the process of deploying packages or having them talking to someone that can do that for them which, to be honest, defeats the purpose
Views
Replies
Total Likes