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; } } }

Rendering URLs correctly in Livesite from a DCR

Matias

Hello,
We are using the OOTB tinyMCE editor to DCRs, and those are used by LS components.
The problem is that the editor adds images or links to the DCR without the URL_PREFIX token (or the PAGE_LINK token).
The src attribute of the DCR looks like this:
src="/images/test.jpg"

where it should look like:
src="$URL_PREFIX/images/test.jpg"

This breaks the links or images when the pages are displayed.
The OOTB basic content component works differently where these prefix are added.
Has anyone else run into the same issue? I've had a case opened with IW for months with no response.

Find more posts tagged with

Comments

Garth McMillan

We altered our component to add the $URL_PREFIX if it doesn't exist.

Rick Poulin

We altered our component to add the $URL_PREFIX if it doesn't exist.

That only works when you're using non-RTE fields. I doubt you want to be trying to search+replace this kind of thing in XSL.

Which version of TS are you on? I could have sworn the $URL_PREFIX and $PAGE_LINK tokens were automatically added-in by Iwov's customized link and img plugins. If you're on an older version, you can just customize those plugins yourself if they're not doing it on their own.

Matias

Hi rpoulin,
I agree with you. I'm in 7.2.1. I also thought that the customization was included as well.

Bowker

We've found that the $URL_PREFIX is added on Items where you use Browser to select a piece of content. Not in free-form fields.

Matias

Strange... for us it doesnt even work there.. When I use the browse button to pick a link, I end up with this value:

/sites/TestSite/test.page

Rick Poulin

Have you customized the TinyMCE toolbar? If you're using the advlink provided OOTB, that plugin should automatically switch out such an example with $PAGE_LINK[test]. Same with the advimage.

If you went through an upgrade as opposed to a clean install, it's possible that you didn't get the updates (or that previous customizations are overwriting the new code).

nipper

There is a known issue where TinyMCE prepends hostname to image URL's. If happens when you try to insert an image using TinyMCE. You would get the window and fill in the URL manually instead of browsing (ie. /htdocs/images/test.gif). When you click "OK" and then look at the resulting html source, it prepends the hostname. You can also see this if you view source of the .page file.

Is this the same issue ?

Bhargav Coca

There is a known issue where TinyMCE prepends hostname to image URL's. If happens when you try to insert an image using TinyMCE. You would get the window and fill in the URL manually instead of browsing (ie. /htdocs/images/test.gif). When you click "OK" and then look at the resulting html source, it prepends the hostname. You can also see this if you view source of the .page file.

Is this the same issue ?

Is there any quick fix for this issue Andy? I know that it can be resolved by customization. Let me know if it is different from this.

Thank You