CODEWITHSUNDEEP
aem
user2003007
user2003007

Reputation:

Issue with publishing a new page in CQ5

I have installed both author and publish instances of CQ5.5 on my PC. But when I add a new page and publish it, it does not appear in the publish instance. Only a blank page is rendered.

I have tried activating it both from the siteadmin and from the Replication page in Tools. Only the navigation item appears in the Publish instance.

I checked the Request logs also. But it only gives a 

200 response(OK)

Can someone please help me on this ?

Upvotes: 4

Views: 4753

Answers (3)

gsquare20
gsquare20

Reputation: 21

You have to build the code to both the environments (author as well as publish). This way both the environments will have the same copy of source code installed in the form of cq5 packages and felix bundles. Then if you create a new page or drop any component on any existing page, it will appear the same on publish environment after activating the same either through 'Activate Page' link in sidekick or through replication tree activation page.

Upvotes: 0

kfaerber
kfaerber

Reputation: 1327

You need to activate/replicate your /apps/site folder where all of your templates and components are located to push it from your author instance to your publish instance. Activating a page doesn't automatically activate the components and templates it uses.

Go to:

http://localhost:4502/etc/replication/treeactivation.html
  • Browse to or type /apps/[your site] in the path field
  • Set the check boxes to fit what you want to activate (Unchecking all will make everything under the selected path activate)
  • Click 'Dry Run' to see what will get activated without actually activating. (This is more of an informative step to help ensure you don't activate something not intended in a production setting)
  • Click 'Activate' to activate.

You can then check your publish instance to see your templates and code are there.

It is easy to miss activating your apps folder as there is no ui like the website admin for pages where you can activate.

Activating a page/folder/asset does not activate sub-pages/folders/assets. This can cause confusion especially when working with folders.

Generally if you need to activate a tree the best way is to use the tree activation utility

Upvotes: 8

Antony Hutchison
Antony Hutchison

Reputation: 2991

The only time I've ever seen this is when the code is not installed. That would be the first thing that I'd check. Go to (assuming you have your publisher on port 4503)

http://localhost:4503/crx/de

You should have your the code in /apps and you should be able to find the content page in /content too.

The reason this happens is that the sling:resourceType property points to a component that doesn't exist so it uses the default which is an empty output.

Upvotes: 2

Related Questions