520 Posts in 248 Topics by 263 members
|Go to End|
5 January 2010 at 6:44pm
My name is Arun, I am new to the Silverstripe CMS. I have setup a site using this CMS. But now i am facing an issue that is regarding the tiny mce editor.
consider if this is the code i have put with in the tiny mce editor, after saving it will look like
Anybody have idea why this happend...?
Any help would be very much appreciated.
5 January 2010 at 8:35pm
Hi Arun, welcome to SilverStripe
There are several topics discussing this matter, just search the forum.
These might give you some pointers:
6 January 2010 at 7:19pm
Nice to meet you.
Thanks and Kind Regards,
15 January 2010 at 4:51pm Last edited: 15 January 2010 4:53pm
I did the silverstrip extended_valid_element mods and although the editor still left the script tags in, it removed the contents unless they were commented out.
I have noticed that some people struggle with tinymce and this issue because tinymce are such purists. So, for those of you also wrangling over this please read the following from sourceforge:
I used the information there telling me that the patches in minor version 2.6 were commented by WEBPOWER to retrofit the mods to the older tinymce.src in Silverstripe 2.3.4 (minor version 2.0.2)
The calls in your _config.php
HtmlEditorConfig::get('cms')->setOption('verify_html', 'false'); // turn off html validation
Do not need to be made after this mod.
Can we have FCKEDITOR for Silverstripe please!!!!???
15 January 2010 at 7:41pm
Well, I for one like an editor that
a) creates valid xhtml
b) does not allow my content editors to put in any garbage they find
16 January 2010 at 10:02am
It only worked like that after I did the _config alterations specified and the comments were not quite right. The whole lot was suspicious.
It not that I REALLY want inline JS it just that sometimes it is the easiest solution (say for a quick and dirty googlemap or whatever). I simply think the option should be allowed and not removed. The script is valid inline markup.
I am trying Silverstripe from Modx which I have used a lot (and I live in Enzed). In modx creating the extra field is as easy as creating a template variable in the cms. In fact almost everything is done within the cms including the templates. This is its beauty (and its danger I suppose) Where modx fails is the multiple pass snippet parsing which can get slow (in V1).
So, how does one create this extra field? Where are the docs. I love having extra fields.
In modx I use a yaml template with several tinymce content fields. The system tests for their use and sets the columns up accordingly without the user even knowing about it. It would be nice to do that here.
16 January 2010 at 11:04pm
I'm a former MODx user myself. But when I discovered SilverStripe, there was no going back for me. I'm not going to elaborate on the reasons why (who cares anyway).
To add new fields to pages, you edit your Page-Class (add the fields to the $db array) or Subclasses thereof.
All this stuff is basically covered in Tutorial 1 and 2, so you're probably best of starting there:
|Go to Top|