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

AEM assets Publish URL

Avatar

Level 3

Hello Team,

I am using AEM 6.5

 

On my PROD author, I am not able to see the "Publish URL" of assets even when my asset is published and "Copy Publish URL" button is available. On clicking of button it opens empty box.

Screenshot 2021-07-05 at 12.38.08.png

On STAGE environment, it is working fine. I checked the externalizer config files for PROD and STAGE ad they are identical.

 

Can someone please suggest what can be the problem for this?

 

Thanks in advance

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @harsingh91 

   It seems there is some issue with this feature

Refer this open issue details : https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/2534

Unfortunately this is still in open state.

 

Thanks

Dipti

View solution in original post

0 Replies

Avatar

Community Advisor

1. Try manually creating the Publish URL once to make sure the asset was published correctly to linked publisher. 

Example: 

Author URL: <server:port>/assets.html/content/dam/abc.jpg

Published URL: <server:port>/content/dam/abc.jpg

2. Please refer to the following article to verify that the configurations are setup correctly: https://adobe-consulting-services.github.io/acs-aem-commons/features/assets-components/copy-publish-...

Avatar

Level 3

Hello Diksha,

Thank you for your answer.

I tried "<server:port>/content/dam/abc.jpg" , it is working fine and my asset is getting downloaded.

 

Also, configuration seems fine in configMgr.

 

Avatar

Community Advisor
Which version of ACS Commons are you using? Is the publish externalizer domain added in osgi config (should be different than stage env)?

Avatar

Level 3

@diksha_mishra , acs-commons version 4.8.4

and externalizer config is correctly set.

 

<? xml  version "1.0"  encoding "UTF-8" ?>
jcr: root xmlns: sling http://sling.apache.org/jcr/sling/1.0 " xmlns: jcr http://www.jcp.org/jcr/1.0 "  
jcr: primaryType "sling: OsgiConfig"
externalizer.domains "[clientName https: //author-client-prod.adobecqms.net,publish https: //client-prod.adobecqms.net,local https: //author-client-prod.adobecqms.net,author https://author-client-prod.adobecqms.net ] "
externalizer.host ""
externalizer.contextpath ""
externalizer.encodedpath "{Boolean} false" />

Avatar

Community Advisor

@harsingh91The externalizer config for PROD should have the PROD domain and not be identical with Stage. Please check if the correct domain is configured.

You can also rebuild the clientlibraries: http://<host>:<port>/libs/granite/ui/content/dumplibs.rebuild.html?invalidate=true

 

Please also check the browser console for any errors, that would help debug/ fix the issue.

 

Avatar

Level 3

Hello @shelly-goel,

Thanks for your answer.

My externalizer config for PROD looks fine. Please check

 

<? xml  version = "1.0"  encoding = "UTF-8" ?>
< jcr: root xmlns: sling = " http://sling.apache.org/jcr/sling/1.0 " xmlns: jcr = " http://www.jcp.org/jcr/1.0 "  
jcr: primaryType = "sling: OsgiConfig"
externalizer.domains = "[clientName https: //author-client-prod.adobecqms.net,publish https: //client-prod.adobecqms.net,local https: //author-client-prod.adobecqms.net,author https://author-client-prod.adobecqms.net ] "
externalizer.host = ""
externalizer.contextpath = ""
externalizer.encodedpath = "{Boolean} false" />

Avatar

Correct answer by
Community Advisor

Hi @harsingh91 

   It seems there is some issue with this feature

Refer this open issue details : https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/2534

Unfortunately this is still in open state.

 

Thanks

Dipti

Avatar

Level 3

Thanks Dipti, Yes I saw this post also.

Hoping to get a solution in sometime.