backslash getting converted to forwardslash in Visual Format Editor

We ran into an issue with the VFE and links where it's converting all backslashes in the link to forwardslashes. This is an issue because our publishers are inserting javascript code into the href attribute. Is there a configuration setting in VFE to tell it not to automatically convert backslashes to forwardslashes? I've looked through the manual and have come up empty there and searching both this forum and the knowledge base was a bust as well.

Thanks

Windows 2003
TeamSite 6.7.1 SP1

Find more posts tagged with

Comments

Adam Stoller

We ran into an issue with the VFE and links where it's converting all backslashes in the link to forwardslashes. This is an issue because our publishers are inserting javascript code into the href attribute. Is there a configuration setting in VFE to tell it not to automatically convert backslashes to forwardslashes? I've looked through the manual and have come up empty there and searching both this forum and the knowledge base was a bust as well.

Thanks

Windows 2003
TeamSite 6.7.1 SP1

Can you post an example of the HTML / javascript code that displays the problem you are trying to resolve (please make sure to wrap the code within [html]...[/html] tags to prevent the code from being interpreted by the Forum software)

Adam Stoller

We ran into an issue with the VFE and links where it's converting all backslashes in the link to forwardslashes. This is an issue because our publishers are inserting javascript code into the href attribute. Is there a configuration setting in VFE to tell it not to automatically convert backslashes to forwardslashes? I've looked through the manual and have come up empty there and searching both this forum and the knowledge base was a bust as well.

Thanks

Windows 2003
TeamSite 6.7.1 SP1

Please do not cross-post. Choose one forum or another - and close the other thread.

Jamik

Please do not cross-post. Choose one forum or another - and close the other thread.

cross posting?! I only posted this once and only to this particular topic thread since this topic thread deals formspublisher and more specifically with the VFE wherever else you see this thread at I most certainly did not post it.

That aside a better explaination perhaps is a user creates a new templated file or edits an existing one and they go to a form field that uses the Visual Format Editor(VFE) and they enter a url that contains javascript like href="javascript&colon;functioncall('variableone', 'variable to with \'backslashes\'');". When the VFE runs it's cleanup code it converts the href to this href="javascript&colon;functioncall('variableone', 'variable to with /'backslashes/'');". (notice the backslashes are now forwardslashes) I can recreate this easy by just going into html source view of the VFE and adding a href with backslashes and when i switch to wysiwyg view and then back to source view they are now forwardslashes.

I've also included the specific config file for the VFE. The configuration for the cleanup in the VFE is set to xhtml which it needs to remain as. We just need to get the VFE to stop changing those backslashes in the href.

Adam Stoller

cross posting?! I only posted this once and only to this particular topic thread since this topic thread deals formspublisher and more specifically with the VFE wherever else you see this thread at I most certainly did not post it.

Sorry about that - this morning, after I made my first response I saw the original post again (without my response) and thought that I must have responded in another forum - hence my request about the cross-posting - again, sorry about that.

That aside a better explaination perhaps is a user creates a new templated file or edits an existing one and they go to a form field that uses the Visual Format Editor(VFE) and they enter a url that contains javascript like href="javascript&colon;functioncall('variableone', 'variable to with \'backslashes\'');". When the VFE runs it's cleanup code it converts the href to this href="javascript&colon;functioncall('variableone', 'variable to with /'backslashes/'');". (notice the backslashes are now forwardslashes) I can recreate this easy by just going into html source view of the VFE and adding a href with backslashes and when i switch to wysiwyg view and then back to source view they are now forwardslashes.

I've also included the specific config file for the VFE. The configuration for the cleanup in the VFE is set to xhtml which it needs to remain as. We just need to get the VFE to stop changing those backslashes in the href.

Okay - now I understand the problem better, I think there are two ways to deal with this - neither of which is necessarily "elegant":

generating an output file from it.Hope that helps.

gzevin

Sorry about that - this morning, after I made my first response I saw the original post again (without my response) and thought that I must have responded in another forum - hence my request about the cross-posting - again, sorry about that.Okay - now I understand the problem better, I think there are two ways to deal with this - neither of which is necessarily "elegant":
FormAPI code - either onItemChange or onSaveValid (or both) that parses the value of the textarea field and re-backslashes the double-quotes within such references
PT code that does essentially the same thing - before outputting the contents of the textarea field
The latter may be easier to code (perl is, IMO, better at doing that kind of parsing), but the former ensures that the code is correct in the DCR (which would be important if you're deploying the DCR itself or pushing the contents of the DCR into a DB instead of [or in addition to] generating an output file from it.

Hope that helps.

most likely this is another exhibition of the Ektron issue in 6.7.1 SP1 that I reported some time ago. It disfigures links and brings it to the format it thinks is appropriate.

I am afraid that even 6.7.2 did not resolve this paricular issue and the resort would be to use TinyMCE instead