Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Local publish can't see published content from author

wkk52586
Level 2
Level 2

I downloaded the latest AEM SDK aem-sdk-2021.11.6023.20211111T113531Z-211000.zip,  and rename the jar package to to aem-author-p4502.jar and aem-publish-p4503.jar, both the author and publish is able to run successfully. And I enabled the replication  agent.

wkk52586_1-1637844229421.png

 

Then I successfully build the sample code(https://github.com/adobe/aem-guides-wknd) and deploy to local author.

I published the changes in author, but  can't see anything in local publish environment. Any suggestion? Thanks

wkk52586_2-1637844415648.png

And when I try to check http://localhost:4503/content/wknd/us/en.html, it's a blank page

wkk52586_0-1637845556321.png

 

 

1 Accepted Solution
kishorekumar14
Correct answer by
Level 9
Level 9

We have to do mapping configs for redirects. Please refer below article to get some idea.

 

https://www.albinsblog.com/2020/07/configure-sling-mapping-for-resource-resolution-in-adobe-experien... 

 

and JFYI the reason you are redirecting to localhost:4503/content.html if you hit localhot:4503 is due to config of default root mapping of publisher.

 

Go to 

http://localhost:4503/system/console/configMgr

check for "Day CQ Root Mapping" property.

 

kishorekumar14_0-1637979908340.png

 

Similarly for author instance if you hit localhost:4502 it will redirect to localhot:4502/aem/start.html

 

 

View solution in original post

7 Replies
SivaPrasadReddyS
Level 8
Level 8

@wkk52586 one quick question, did you also deploy the code to publisher instance? 

In order to see the page content on publisher, make sure both author & publisher has same code based installed. 

 

 

Kiran_Vedantam
Community Advisor
Community Advisor

Hi @wkk52586 

 

What is the error thats coming in the logs?

Can you confirm if the same page is working in author?

Can you confirm if all the bundles are installed and active in publisher?

 

Thanks,

Kiran Vedantam.

wkk52586
Level 2
Level 2

@Kiran_Vedantam  @SivaPrasadReddyS  I'm a green hand for AEM. After installing the author and publish and run them up. Setup the configuration and test successfully.

wkk52586_0-1637889034249.png

 

Then I just followed the guide in https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-wknd-tutorial-devel...

Generated the project and ran the command

mvn clean install -PautoInstallSinglePackage

The WKND projects deployed to local author:

wkk52586_2-1637889226142.png

Then I made some changes for en and publish that,

wkk52586_3-1637889339735.png

But in local publisher ,it's a blank page

wkk52586_4-1637889401371.png

 

Any suggestion? Thank you!

 

kishorekumar14
Level 9
Level 9

Hi @wkk52586 

 

Run below command to deploy in publisher instance and then check please.

 

mvn clean install -PautoInstallPackagePublish
wkk52586
Level 2
Level 2

@kishorekumar14Thank you.

Now I can see the content with URL

http://localhost:4503/content/wknd/us/en.html

wkk52586_0-1637935796855.png

But I can't see the content directly with URL http://localhost:4503/

wkk52586_1-1637935854208.png

 

Any more suggestion? thanks

 

kishorekumar14
Correct answer by
Level 9
Level 9

We have to do mapping configs for redirects. Please refer below article to get some idea.

 

https://www.albinsblog.com/2020/07/configure-sling-mapping-for-resource-resolution-in-adobe-experien... 

 

and JFYI the reason you are redirecting to localhost:4503/content.html if you hit localhot:4503 is due to config of default root mapping of publisher.

 

Go to 

http://localhost:4503/system/console/configMgr

check for "Day CQ Root Mapping" property.

 

kishorekumar14_0-1637979908340.png

 

Similarly for author instance if you hit localhost:4502 it will redirect to localhot:4502/aem/start.html

 

 

View solution in original post

Arun_Patidar
Community Advisor
Community Advisor

On the publishers /content is the default page.

You see 404 because /content node is not a type of page but a folder.

you can ignore this and make sure content in your project rendered properly.