Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

Blog Module

Discuss the Blog Module.

Moderators: martimiz, Sean, biapar, Willr, Ingo, swaiba, simon_w

Main blog post being served from TinyMCE full of escape characters


Reply

4 Posts   1835 Views

Avatar
domperignon

4 February 2010 at 12:37pm (Last edited: 25 February 2010 10:55am), Community Member, 5 Posts

Hello,

I'm building my first site with silverstripe and, in general, I'm very impressed with it. I'd be grateful for advice with a problem I've just encountered.

Running SS 2.3.5, I have installed 0.2.1 of the blog module and enabled WYSIWYG editing according to http://www.silverstripe.org/archive/show/185873#post185873. Although my [url=http://romseychoir.dbrenton.com/news-and-events/]blog front page[/url] is showing text rendered as it should be, SS is serving the full post using escape characters, so that my headings are showing as marked-up plain text rather than in properly rendered styles.

How can I correct this, please?

Avatar
domperignon

25 February 2010 at 10:58am Community Member, 5 Posts

[Three weeks later] Could somebody spare a minute to shed any light on this?

Many thanks.

Avatar
Juanitou

25 February 2010 at 12:37pm (Last edited: 25 February 2010 12:38pm), Community Member, 323 Posts

Hi!

Your BlogEntry.ss template must have something like this, check it:

<% if IsWYSIWYGEnabled %>
   $Content
<% else %>
   $ParsedContent
<% end_if %>

In any case, you must simply call $Content.

In the BlogHolder, it’s normal that you see the url tag, since it’s not HTML.

Also, I don’t see NEW entries, have you tested it? Default entries are borne to be badly displayed, since they use BBCode.

Hope it helps,
Juan

Avatar
domperignon

6 March 2010 at 11:02am Community Member, 5 Posts

Hi Juan

Many thanks for responding. Apologies for not getting back to you. I did have the code you mention in my BlogEntry.ss file but, owing to this issue, have decided not to pursue using the blog module at least until the production release of 2.4 and a compatible blog module that, I hope, will resolve this issue.

All the best,

Dominic