$PAGE_LINK question

ChrisNichols

We're using Site Publisher, but not LiveSite.

I need to change my link paths in inline components (no DCR) and I'm hoping someone might know how to do it. I have a Rich Text Editor component using Tiny MCE. When users browse to .page file to make a link, it generates this code:

    <a href="$PAGE_LINK[test/test]">

When I generate the html, I get this:

    <a href="/html/FRS-SitePub/test/test.html?">Content...</a>

However, my published files go to a different root directory. I need to change the link to remove "/html/FRS-SitePub", like this:

    <a href="/test/test.html?">Content...</a>

Also, why does it add a question mark at the end of the url?

On some different sites, I may need to change all the extensions as well, say to .cfm, like this:

    <a href="/test/test.cfm?">Content...</a>

Any ideas?

Rick Poulin

Perhaps use a PERL script to "fix" your links by regex as part of your deployment process?

I haven't personally been able to get the HTML generation bit to be very flexible. I just get around it with workflow. For preview purposes within TS, you can usually get the iwproxy to redirect your internal users to the right place.