Preview not displaying image content assets from the Content Hub

2025/05/27 9:17 AM

Hi there

Our CMS environment isn't displaying images in the page builder or preview mode. However if I right click on the asset in the browser inspector and open in new tab then then image displays. There is an error in the log displaying "Relative path hash validation has failed". I have made sure the CMSHashStringSalt matches that of the Project info in the SaaS portal dashboard and I have even tried re-signing the macros. I've not worked much with the SaaS environment before so not sure if there is something I have missed with regards to that which might account for the issue.

Environment

Tags:
Page Builder Xperience Administration v30.5.0

Answers

2025/05/27 11:12 PM
  1. Does this happen in all environments?
  2. How are you generating URLs for images rendered in your website channels?
  3. If this is a production environment issue, are you using a custom domain?
  4. If you go to the Xperience Portal dashboard and click the "show" button in the Project info panel you can see the hash string salt used for the project. You should be using that locally.
  5. Are you deploying website pages and content items through CD deployment packages or authoring them in your SaaS environments?
2025/05/28 7:08 AM

Hi Sean, let me address those questions...

  1. Yes this occurs on all environments, locally, QA, UAT, PROD
  2. We are simply obtaining the Url of the asset retrieved similar to...
    https://docs.kentico.com/developers-and-admins/development/content-retrieval/retrieve-content-items#retrieve-assets
  3. Its across all environments
  4. Yeah, that is where I obtained the hash string salt value I am using
  5. We're not deploying the website and content item through CD deployment. We are authoring them on each respective environment
2025/05/28 9:17 AM
Answer

Thanks Sean - I have sorted. Appears the tilde in the path was causing the issue but only for the preview.

2025/05/28 7:40 PM

I also have had HashValidation errors in the event log and it seems to be related to misformed/poorly formed image links

To answer this question, you have to login first.