nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

URL_PREFIX not appearing in generated HTML

raeovine

I have a .page file with a with an image link using a path like $URL_PREFIX/assets/images/common/header_logo.jpg. When I generate HTML for this page, it shows the link as /assets/images/common/header_logo.jpg without the http information I defined when creating the site.

Any ideas?

Find more posts tagged with

Comments

vpatel

I have a .page file with a with an image link using a path like $URL_PREFIX/assets/images/common/header_logo.jpg. When I generate HTML for this page, it shows the link as /assets/images/common/header_logo.jpg without the http information I defined when creating the site.

Any ideas?

When you generate static page, I believe, it'll be set to an area relative path. What http info are you talking about?

raeovine

I am not getting any data for $URL_PREFIX. Where does SitePublisher get the information to populate in this variable? I would think it would be some combination of Site Addresses and Directory when we are in Step 1 of setting up the site initially. I'm not seeing that information in my generated HTML page.

vpatel

I am not getting any data for $URL_PREFIX. Where does SitePublisher get the information to populate in this variable? I would think it would be some combination of Site Addresses and Directory when we are in Step 1 of setting up the site initially. I'm not seeing that information in my generated HTML page.

It does not get anything from the site addrress or directory. It simply resolves the correct URLs in preview (where you may have /iw-mount/default/main/.......) and production (where you don't have the /iw-mount/..... injection).

raeovine

I am planning to deploy the HTML that is produced via the SitePublisher -> Generate HTML operation. That operation is not putting any value into $URL_PATH. Therefore, when I deploy to production, that path will not be correct. I don't understand what would be in this value and how it is controlled in SitePublisher.

wscott

The HTML generated uses a relative path so that images and so forth will be displayed correctly during preview.

If you want a custom path, you can add a step to your workflow deployment to modify the image URLs. This way your HTML pages still display correctly in preview, but will have whatever URL prefix they need in production.