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

Issue with Visual Formatter

RHEGDE

Hi,
We have migrated from TeamSite 6.5 SP2 to TeamSite 6.7.1 SP1. We are facing problem with Visual Formatter. When we insert a PDF link it is inserting character Â(Â) before and after hyperlink. Please help me to solve this problem.

I have attached my visual formatter configuration file also.

Thanks

Find more posts tagged with

Comments

nico

Since we have upgraded to ts 671 sp1 we get the same prob but almost but randomly peppered in our content.

Let me know if you find a solution.

Antharix

Are you facing the problem only with PDF files?

sasikumarg

what is the version of ewebeditpro ..are you using VF5.1?

since the version is changed,if you are using the same config.xml in previous version,it may throw some strange errors in 671 in various cases.

check the ektron forum,you will definitely get the solution.check the new developer guide too.Let me know if you are facing some other issues with VF

nico

Are you facing the problem only with PDF files?

No it's happening on all templated pages, and it's killing me.

nico

what is the version of ewebeditpro ..are you using VF5.1?

since the version is changed,if you are using the same config.xml in previous version,it may throw some strange errors in 671 in various cases.

check the ektron forum,you will definitely get the solution.check the new developer guide too.Let me know if you are facing some other issues with VF

When you upgrade to the latest version of Teamsite it updates VF, does that update your vf xml file too?

XAxisSortWithOptionalGrouping.zip

Antharix

"http://devnet.interwoven.com/forums_vb/showthread.php?t=24091&forumid=13 "

discusses the same / similar issue!

nico

"http://devnet.interwoven.com/forums_vb/showthread.php?t=24091&forumid=13 "
discusses the same / similar issue!

Yeah note the last post on that thread is from me asking what the solution is cause (correct me if i'm wrong) I don't see it. HELP!

Nico

nico

not confirmed yet but so far so good, I've set our clean charencode = charref and this seems to have fixed things.