Hello,

I've just come across your CMS yesterday, so I'm very green.

Here are some questions off the bat:

1. Possible to structure the URLs to match the tree in the CMS? i.e domain.com/parent/child/ vs domain.com/child/

2. Possible to edit tiny_mce to include other plugins and such? I'd like to add the div tag to the drop down select, as well as add a css class/id drop down.

3. Possible to use tiny_mce on the blog module? I don't like how it uses bbcode. When I set this up for clients, I need to make this as easy to use as possible. I'd like them to be able to insert images and format using the tiny_mce tools like the rest of the site.

4. How much extra load/memory usage does it add to use a bunch of "if inSection" tags on my template? I prefer to use one main template, then target certain sections to add a bit off specific page elements. I don't like having separate templates unless I have to.

Think that's it for now. I'm looking for a new CMS to use for all my client sites. I've narrowed it down to this, and one other, so I'm trying to evaluate both of them the best I can, before switching over.

Do you know which files I'd have to edit to modify the tiny_mce installation? I'm a designer first, programmer...barley ;) And if anybody has an answer to the blog module question, that would be great.

In response to your question about my template setup, it depends on how much code there is. I like to have one main template and setup a bunch of 'if section' type tags, for small minor things. For example, I have a simple banner that is only displayed on a few pages. I'd rather just write "if section = blah then img src=" vs duplicating the whole template again. For more serious modifications, then obviously I'd use a fresh template.

I run a design business where I'm constantly setting up client sites with a CMS they can use to manage their site. I look for ease of use and the template engine as my number one reason for using a CMS. I really want to lean towards using SilverStripe because I absolutely love the backend UI, but it doesn't seem as polished in terms of features as the other one I'm looking at. It lacks a few things like a mature blog engine, a URL sub sections as outlined in my first post, a better template system - mainly just having it all online in the backend vs FTPing .ss files. There are also some memory issues I see around here which concerns me, even though I'm not on shared hosting, and a few other things.

Overall I really love this CMS and the direction it is going in. Just not sure if it's ready for me to use yet.

In response to your blog question, with the current SVN trunk, it is possible to enable WYSIWYG editing by either setting the static variable to true, or subclassing and doing the same, depending on if you wish to be able to post using BBCode as well.

Though you can't use both BBCode and WYSIWYG in a post.

In the trunk code for BlogHolder.php, (blog/code/BlogHolder.php), there is a line:

static $allow_wysiwyg_editing = false;

Changing false to true will allow you to use the WYSIWYG editor.