Return to Jive Software

Skip navigation
Up to Discussions in Support
816 Views 8 Replies Last post: Nov 4, 2008 6:26 AM by todd.west RSS
robertly Novice
robertly
25 posts since
Jul 28, 2008
Currently Being Moderated

Sep 5, 2008 12:04 PM

Turning off filtering of HTML document created with web service

My html gets filtered and has <pre class="jive_text_macro jive_macro_code" jivemacro="code" ___default_attr="html"> added to it. All the < and > gets changed to &lt; and &gt;. How do I prevent this from happening? It makes my HTML look badly formatted. When I use the HTML editor and change everything back to < and > and remove the <pre> tag, everything looks good again.

todd.west Jive Employee
todd.west
15,926 posts since
Jul 14, 2008
Currently Being Moderated
Sep 5, 2008 4:18 PM in response to: Robert Ly
Re: Turning off filtering of HTML document created with web service

Hi Robert,

 

After some extensive testing, it seems to me that this is a bug with our webservices implementation. It seems that the problem is that the html parser looks for a body and p tag and if it doesn't find it, it tries to fix it and ends up escaping the original HTML. I have filed a bug for this issue in our JIRA Database (JIRA ID#: CS-8807). Please let me know if you need anything else. Thanks!

 

-Todd

robertly Novice
robertly
25 posts since
Jul 28, 2008
Currently Being Moderated
Sep 6, 2008 7:35 PM in response to: Todd West
Re: Turning off filtering of HTML document created with web service

ok, thanks for the info. would the course of action for now be wrap all my HTML in a body p tag?

todd.west Jive Employee
todd.west
15,926 posts since
Jul 14, 2008
Currently Being Moderated
Sep 8, 2008 7:58 AM in response to: Robert Ly
Re: Turning off filtering of HTML document created with web service

If possible, that would probably do the trick but that seems to get stripped out as well. Unfortunately it looks like this isn't possible until there is a fix. If you find a workaround please let me now. Thanks!

 

-Todd

robertly Novice
robertly
25 posts since
Jul 28, 2008
Currently Being Moderated
Sep 9, 2008 12:36 PM in response to: Todd West
Re: Turning off filtering of HTML document created with web service

wrapping everything in just <body></body> fixes it.

robertly Novice
robertly
25 posts since
Jul 28, 2008
Currently Being Moderated
Sep 9, 2008 1:33 PM in response to: Robert Ly
Re: Turning off filtering of HTML document created with web service

Ignore that last statement. A SOAPFault is returned if you try to create an HTML document that uses the pre tag within the body tag. If you remove the body tag, the pre tag is preserved but then the HTML gets encapsulated in the pre code block mentioned in the first post. If you add the body tag, everything gets rendered as expected, but if it has a pre tag, the error is returned.

todd.west Jive Employee
todd.west
15,926 posts since
Jul 14, 2008
Currently Being Moderated
Sep 9, 2008 1:31 PM in response to: Robert Ly
Re: Turning off filtering of HTML document created with web service

Hi Robert,

 

Yes this is the same issue I ran into, which was a big reason for filing a bug report/feature request. Thanks!

 

-Todd

robertly Novice
robertly
25 posts since
Jul 28, 2008
Currently Being Moderated
Nov 3, 2008 5:19 PM in response to: Todd West
Re: Turning off filtering of HTML document created with web service

Hi Todd, did this get resolved? I'm not sure how I can check the JIRA database to see or if that is even possible for an outsider.

todd.west Jive Employee
todd.west
15,926 posts since
Jul 14, 2008
Currently Being Moderated
Nov 4, 2008 6:26 AM in response to: Robert Ly
Re: Turning off filtering of HTML document created with web service

Hi Robert,

 

The JIRA database is an internal only system. I just checked on this bug for you and I can confirm that it has been fixed in 2.5.3. Thanks!

 

-Todd

More Like This

  • Retrieving data ...

Bookmarked By (0)

Case Product Issues

Loading Jira issues

Loading related product issues for this case
To better serve our customers we have included functionality to automatically follow up on a case after it has been idle for more than 5 days, and then auto close after an additional 3 days of inactivity. Choose No to acknowledge that this case will remain idle for longer than 5 days.
Making cases public allows other customers to learn from the solution of the case. It can also be used to gain feedback from others in the community. Ask our Support Engineers for more info, but we encourage you to make your cases public.