Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Publishstyles="false" still inserting styles
teal001
I am trying to import a new stylesheet into our VisualFormatter for one of our templates. Right now, publishstyles are set to false. However, it is still publishing the styles:
span class="text-body-large" style="FONT-WEIGHT: normal; FONT-SIZE: 28pt; COLOR: #000; FONT-STYLE: normal; FONT-FAMILY: Verdana, Arial, Helvetica, sans-serif"
Does anyone know what else could be going on? I attached my code for the Visual Formatter.
Find more posts tagged with
Comments
John742
Post your DCT
teal001
Here is my DCT.
John742
This appears to be your presentation.tpl. I need the DCT that calls the VFE that you are writing custom config for.
teal001
Here...........
Migrateduser
generally the publishstyles is for whether or not to populate the styles dropdown, as opposed to stripping styles out of the VFE field content when you save it, which is done with the autocleaning...
which one is not doing what you want it to?
if you recently changed either of these, the VFE field settings might be cached for users...try changing the interface "name" value to force a reload...
cheers,
-R
teal001
Well according to the Teamsite manual:
Below is an example of the html text of a saved line when
publishstyles is set to true.
p align="center" style="BOTTOM: 0px; FILTER:; FONT-FAMILY: 'Times New Roman'; FONT-SIZE:
12pt; MARGIN: 0in 0in 0pt"> VARs benefits and features
Here is the same line when publishstyles is set to false.
p> VARs benefits and features
Migrateduser
stripping out a style from a tag is different than removing
tags...
if you want to remove the
tags, use the clean functionality with the remove element...
cheers,
-Rori
teal001
I don't want to remove tags, I just want them to be hidden, which is what publishstyles=false is supposed to do.
teal001
Update: We have tested everything and determined that it is our stylesheet that is causing the problem. Our master stylesheet was substituted and there was no problem.
TestReport.rptdesign