Expand my Community achievements bar.

Enhance your AEM Assets & Boost Your Development: [AEM Gems | June 19, 2024] Improving the Developer Experience with New APIs and Events
SOLVED

Publish Login

Avatar

Level 7

Hi,

As per the documentation in the URL, ( ~~https://docs.adobe.com/docs/en/aem/6-1/administer/communities/overview/geo-tour.html),

I want to access Forms Moderation console. (

       •browse to http://localhost:4503
       •sign in with username 'admin' and password 'admin'
       • browse to moderation console )

When I logged into my freshly installed AEM 6.1  publish instance, it is taking me to the following URL.

http://localhost:4503/content/geometrixx-outdoors/en.html

From here, I am not able to navigate to the moderation console (In fact any other pages of publish).

Please suggest.

Appreciate your support.

Thanks,

Rama.


 

1 Accepted Solution

Avatar

Correct answer by
Administrator

Hi Rama Nyshadham

Please have a look at following actions :-

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

 

If things dose not work, please have a look at the following links, if you are also facing same problem:

1. http://stackoverflow.com/questions/16472090/cq5-permissions-problems-viewing-content-on-publish

//You can set "read" permissions for the group "everyone". Ultimately, you will want to put a dispatcher in front of your publishers, and prevent public access to your publish instances directly (preferably sitting behind a VPN).

This means that your dispatcher will be denying access to /apps anyway, and your instances will still be secure, and the ACL for the publisher won't really matter as long as an anonymous user can render the page under /content

 

2. https://forums.adobe.com/thread/974597

// The issue was that after creating a new site on an author instance, when viewing it on the publish site the page was not rendering correclty.  The visible symptom was that initial HTML tags (for HTML, HEAD, META, and BODY) were being generated, but the content was not be filled in. 

 

I did Activate my content properly, however, because it was a new site, and I had generated new components and site templates which resided in the "apps" folder and assets in the "etc" folder, they were not available to be rendered and so the HTML page was blank (because they could not be found on the publish instance).  What I did was use the "Activate Tree" under the Tools section to publish content in /content/mysite.  What I missed was using the Activate Tree to publish items I had created in /etc/designs/mysite and /apps/mysite.

 

I hope this would help you.

Thanks and Regards

Kautuk Sahni



Kautuk Sahni

View solution in original post

1 Reply

Avatar

Correct answer by
Administrator

Hi Rama Nyshadham

Please have a look at following actions :-

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

 

If things dose not work, please have a look at the following links, if you are also facing same problem:

1. http://stackoverflow.com/questions/16472090/cq5-permissions-problems-viewing-content-on-publish

//You can set "read" permissions for the group "everyone". Ultimately, you will want to put a dispatcher in front of your publishers, and prevent public access to your publish instances directly (preferably sitting behind a VPN).

This means that your dispatcher will be denying access to /apps anyway, and your instances will still be secure, and the ACL for the publisher won't really matter as long as an anonymous user can render the page under /content

 

2. https://forums.adobe.com/thread/974597

// The issue was that after creating a new site on an author instance, when viewing it on the publish site the page was not rendering correclty.  The visible symptom was that initial HTML tags (for HTML, HEAD, META, and BODY) were being generated, but the content was not be filled in. 

 

I did Activate my content properly, however, because it was a new site, and I had generated new components and site templates which resided in the "apps" folder and assets in the "etc" folder, they were not available to be rendered and so the HTML page was blank (because they could not be found on the publish instance).  What I did was use the "Activate Tree" under the Tools section to publish content in /content/mysite.  What I missed was using the Activate Tree to publish items I had created in /etc/designs/mysite and /apps/mysite.

 

I hope this would help you.

Thanks and Regards

Kautuk Sahni



Kautuk Sahni