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

Visual Format not only inserts hostname into relative links

gzevin

I want to add to my previous thread, but this is a new one, I guess. In addition to the fact that new Visual Format (Ektron) inserts TeamSite server hostname into links, we have disciovered that it also removes relative links.

E.g.

[font=Arial]/media/flag.gif or

[/font]

[font=Arial]../media/flag.gif or

[/font]

[font=Arial]../../media/flag.gif

[/font]

[font=Arial]all links will be replaced with http://hostname/media/flag.gif

[/font]

DON'T YOU LOVE IT????????

I would like to ask IWOV - when this will be fixed? It goes through support as well, but I just want the rest of our community to have a heads up, when they move to 6.7.1 SP1, as they will be forced to redo possibly hundreds and even thousands of DCRs.

Find more posts tagged with

Comments

LooseCannon

When you view the source, are the links absolute to the teamsite hostname or relative?

I have an open ticket with support where the href (when looking at the source) is relative but behaves as if it were absolute and always resolves to the teamsite server when clicked via the browser. Not a good situation.

What happens is VF inserts a [base href="teamsite.company.com"] tag into the VF field anytime erroneous code is encountered. This code then makes its way into the generated html and causes relative links or images to resolve to the base href value.

As a workaround a regex was added to the tpls to remove the tag.

gzevin

When you view the source, are the links absolute to the teamsite hostname or relative?

I have an open ticket with support where the href (when looking at the source) is relative but behaves as if it were absolute and always resolves to the teamsite server when clicked via the browser. Not a good situation.

What happens is VF inserts a [base href="teamsite.company.com"] tag into the VF field anytime erroneous code is encountered. This code then makes its way into the generated html and causes relative links or images to resolve to the base href value.

As a workaround a regex was added to the tpls to remove the tag.

it turns the relative links into absolute ones. for good. Literally disfigures the links.

Yes, we handle the removal of the teamsite hostname with regexes, but the situation is really bad. The KB that supposedly fixes this is hard top follow, allegedly doesn't provide the answer, and, what's more, the solution is subject of being wiped out in the future by a patch or something.

I guess there are not that many people on SP1. Just wait for the avalanche of wrath to come.

IWOV keeps silence so far, support is suggesting the KB article.

nipper

I guess there are not that many people on SP1. Just wait for the avalanche of wrath to come.

I am on SP1, but we do not use VFE. I have written some very flexible templates instead.

Valentine

I believe the same is happening in TinyMCE with SP1, and I've been told that IWOV got a black patch, they still did not provide it.

gzevin

I believe the same is happening in TinyMCE with SP1, and I've been told that IWOV got a black patch, they still did not provide it.

tinyMCE seems to be Ok on SP1?. I am actualy moving the branches with relative links usage into tinyMCE, if I can.

gzevin

I am on SP1, but we do not use VFE. I have written some very flexible templates instead.

how does this help? the fact they are flexible? no rich text fields at all?

gzevin

I believe the same is happening in TinyMCE with SP1, and I've been told that IWOV got a black patch, they still did not provide it.

with tinyMCE I have another story, that probably deserves a separate thread. When the DCT duplicates tinyMCE fields and disables the preview and generation.

nipper

yep, no rich text fields at all. In fact, I strip out all HTML from my textareas. I am so mean. I only allow links with images or in bullet points and build the HTML for the user.

LooseCannon

something else to check...

[resolvemethod value="local"/]

[viewas publish="xhtml"]

[standard publish="xhtml"]

gzevin

yep, no rich text fields at all. In fact, I strip out all HTML from my textareas. I am so mean. I only allow links with images or in bullet points and build the HTML for the user.

You are probably still using 4.2 SP1. that's why!!!!! Smiley Happy

but yes, if I could I would too.

scandorph

with tinyMCE I have another story, that probably deserves a separate thread. When the DCT duplicates tinyMCE fields and disables the preview and generation.

Which version of TeamSite are you on?

gzevin

Which version of TeamSite are you on?

it's mentioned in my first posting Smiley Happy

6.7.1 SP1 on Linux.

rahulindia

I am also facting same issue. Any updates on this ?
Env. Teamsite 6.7.1 sp1 windows 2003

gzevin

I am also facting same issue. Any updates on this ?
Env. Teamsite 6.7.1 sp1 windows 2003

move to tinyMCE, if you like it

Bjorn

The KB that supposedly fixes this is hard top follow, allegedly doesn't provide the answer, and, what's more, the solution is subject of being wiped out in the future by a patch or something.

I guess there are not that many people on SP1. Just wait for the avalanche of wrath to come.

Yeah - I'm part of the avalanche. What a joke.

FWIW, the KB Greg mentions above is "Allowing for Absolute and Virtual paths in Visualformat Editor in TeamSite 6.7.1 SP1", Knowledge Base Article: https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=60388 .

And yes, it really is a subpar writeup and process. Greg was generous to call it hard to follow.

Oh - by the way, my workaround for this right now is FormAPI based. Something like:

//use this in your initialization method
IWEventRegistry.addFormHandler("onSave", saveHandler);

function saveHandler(button) {
 var item = IWDatacapture.getItem("/YOURPATHWITHINDCRHERE");
 var itemValue = item.getValue();
        itemValue = itemValue.replace(/YOURREGEXHERE/g,"");  
 item.setValue(itemValue);
 return true;
}

(Obviously, you'll need to modify the code to meet your needs.)

gzevin

Yeah - I'm part of the avalanche. What a joke.

FWIW, the KB Greg mentions above is "Allowing for Absolute and Virtual paths in Visualformat Editor in TeamSite 6.7.1 SP1", Knowledge Base Article: https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=60388 .

And yes, it really is a subpar writeup and process. Greg was generous to call it hard to follow.

Oh - by the way, my workaround for this right now is FormAPI based. Something like:
//use this in your initialization method
IWEventRegistry.addFormHandler("onSave", saveHandler);

function saveHandler(button) {
 var item = IWDatacapture.getItem("/YOURPATHWITHINDCRHERE");
 var itemValue = item.getValue();
        itemValue = itemValue.replace(/YOURREGEXHERE/g,"");  
 item.setValue(itemValue);
 return true;
}
(Obviously, you'll need to modify the code to meet your needs.)

actually, I was thinking about the formAPI handler as well - in our case the amount of work was SO big, adding the handler to every DCT was something beyond us. But for the new forms I think this is the best thing one could do, actually. It does not help with absolute/relative links fiasco though Smiley Happy

jbonifaci

We faced this same issue when we upgraded earlier this year. I believe all I did to fix it was to use the out of the box VFE config file and re-add our custimizations into it. Once I did that, instead of using our outdated VFE config, it resolved the issue.

Something you may want to consider trying.

~Jeff

gzevin

We faced this same issue when we upgraded earlier this year. I believe all I did to fix it was to use the out of the box VFE config file and re-add our custimizations into it. Once I did that, instead of using our outdated VFE config, it resolved the issue.

Something you may want to consider trying.

~Jeff

I hope we are talking about the same things. Because neither support nor senior figures from product management nor KB articles nor OOTB configs could fix this issue

jbonifaci

I hope we are talking about the same things. Because neither support nor senior figures from product management nor KB articles nor OOTB configs could fix this issue

I probably didn't read the entire thread closely, but the issue I was referring to was the issue in the first post. VFE converting relative links to fully qualified links.

We dealt with this a while back now, so the details are a bit fuzzy, but we got it resolved. I believe the main thing that helped with this was using the OOTB VFE config and then adding our customizations back in. We may have made some other tweaks as well, but I remember that being key.

If I misunderstood what the issue was, please let me know. Otherwise, I'd be willing to help troubleshoot this wonderful "feature". Please post the erroneous VFE config and a sample of the HTML that is being "cleaned" improperly and I will see if I can help.

~Jeff

gzevin

I probably didn't read the entire thread closely, but the issue I was referring to was the issue in the first post. VFE converting relative links to fully qualified links.

We dealt with this a while back now, so the details are a bit fuzzy, but we got it resolved. I believe the main thing that helped with this was using the OOTB VFE config and then adding our customizations back in. We may have made some other tweaks as well, but I remember that being key.

If I misunderstood what the issue was, please let me know. Otherwise, I'd be willing to help troubleshoot this wonderful "feature". Please post the erroneous VFE config and a sample of the HTML that is being "cleaned" improperly and I will see if I can help.

~Jeff

Jeff, even IWOV admits that this is the 'feature' introduced by the new Ektron and it cannot be fully resolved at the moment. The issue also is that the KB article describes only 1 level of relative links to preserve, wehereas I need to be able to simply retain the existing, pre-SP1 functionality.

Another issue is the teamsite hostname in the links. How did you get rid of it - what VFE settings did you touch?

jbonifaci

Jeff, even IWOV admits that this is the 'feature' introduced by the new Ektron and it cannot be fully resolved at the moment. The issue also is that the KB article describes only 1 level of relative links to preserve, wehereas I need to be able to simply retain the existing, pre-SP1 functionality.

Another issue is the teamsite hostname in the links. How did you get rid of it - what VFE settings did you touch?

Greg, we simply followed the changes in the KB article:

https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=60388

Our server admin performed steps 5-8.

As far as steps 1-4 are concerned, they didn't work using outdated VFE config files. We had to use the OOTB VFE config and make updates. The OOTB VFE config already had those changes, but there were obviously other things it had as well that we needed.

All of our links stay as the user enters them now, whether relative or fully qualified.

~Jeff

Brett Sargeant

according to support this issue has been resolved in 6.7.2

Yeming

We ran into the similar problem of issue in 6.7.1 SP1. We found it appears when user copies the content from Microsoft word or other source.
Following the article about this issue.
https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=62396

Migrateduser

We are using TeamSite 6.7.2 on Solaris (eWebEditPro 5.1) and still have this issue. Is there a status update on this? I have created templates for a website that conforms to html 4.01 doctype. I don't want xhml tags on the page. I also don't want the vulnerability of having the links corrupted if someone correctly inputs html per this doctype.