bugs in 0.10 or ???

[ploc]

Hello Wishy and others !

First, I've installed cmsms 0.10 for my website, I had no problem installing this version, and no problem updating the website. Then I saw the new admin interface, although is it skinnable, the default one is really nice, I don't think I will need to change it for a moment ! To sum up, this new version seems great.

A few bugs I think I've found :

1/ when I delete a template, css/template associations seem not to be deleted; the consequence is that I can't delete the css after that... This is confirmed by the fact that when I delete the css via phpMyAdmin (this is the only solution as I can't "see" the association via the web interface), I can now delete the css.

2/ I've created a limited user that can only create pages. It appears that, once logged in, the aser can also modify the existing pages (I did not try to validate the form when modifying the page, but I think this would haev worked).

3/ The same limited user as above cannot modify his personal preferences in the website.

Let me know if I can give some more pieces of information !

And to finish, I have two suggestions for you :

1/ I think it would be great to have a database analysis tool, a tool used to diagnose the database. As you can see in bug #1, it could be helpful to display and deleted orphan elements (association linked to an non-existant css or template, comment linked to a non-existant I-don't-know-what and all these broken associations). It would help to keep the database clean. What do you think ? I know that in a perfect world (without bug), the cms should guarantee that the database is consistent. But in that perfect world, I think we can be interested to get statistic about the website (how many templates, css, pages, comments, news...). To sum up, this tool would check some basic things (orphans and other things) displaying an alert if needed, then display statistics about the website. What do you think of this suggestion ?

2/ when you'll have some time you should definetly update the demo version to 0.10. The demo version is now 0.8.2, and so much work has been done since these old times !

Anyway, great job folks, it is a real pleasure to use cmsm !

Ploc

[Ted]

Thanks for the kind words.

The first thing is definatly a bug.  It's fixed in svn.

Number 2, i don't think is really a bug.  A user automatically has permission to edit a page if they created it (they are they owner).  Though, reading it again, it sounds like you mean other pages as well (as in, they are owned by admin).  I just did some quick tests and it looks like it works as advertised.  Only the pages owned by my test user show up in the list...

Number 3 is fixed, also.

Thanks again!

[ploc]

Hello wishy !

For bug #2, you're right, it's not a bug, all my pages are owned by the limited user, so everything is ok...

Bug #3 is fixed in svn ? If yes, I think I'll get it when 1.0 will be available, this summer ?

And to finish, I have four suggestions for you :

1/ I think it would be great to have a database analysis tool, a tool used to diagnose the database. As you can see in bug #1, it could be helpful to display and deleted orphan elements (association linked to an non-existant css or template, comment linked to a non-existant I-don't-know-what and all these broken associations). It would help to keep the database clean. What do you think ? I know that in a perfect world (without bug), the cms should guarantee that the database is consistent. But in that perfect world, I think we can be interested to get statistic about the website (how many templates, css, pages, comments, news...). To sum up, this tool would check some basic things (orphans and other things) displaying an alert if needed, then display statistics about the website. What do you think of this suggestion ?

2/ Considering the group permission interface, why not simplify the interface :

instead of

add x        X
add y        X
modify x    O
modify y    X
remove x  O
remove y  O

we could have

        add      modify        remove
x        X            O              O
y        X            X              O

It would be simpler to have this interface, no ?

3/ When you'll have some time you should definetly update the demo version to 0.10. The demo version is now 0.8.2, and so much work has been done since these old times !

4/ You should also update the roadmap on the website, it not really up to date any more !

Ploc

[Ted]

There will probably be 0.10.1 and 0.10.2 bug fix releases before 1.0 comes out, so you should be ok.

1. I agree that this is a pretty good idea.  Can you post a feature request to mantis and I'll see what I can come up with?

2. Actually, this is a pretty good idea.  Not quite as simple as it looks, though.  Permissions are completely dynamic in nature, with modules and other things being able to create their own permissios schemes to use.  I'm sure I could come up with something to make this look a little better, though.  How about a feature request for this also (it keeps me organized when feature requests/bugs are in one plaace)?

3. For the demo, I'm probably going to remove it and just point people to the demo on opensourcecms.com, since they're much better at maintaining the demos I am.

4. Agreed.  I'll try to get to that very soon.

Thanks!

[ploc]

One more bug : when setting global preferences, the textareas are always empty even if there were set to a non-null value before.

And one last : the maintenance message does not seem to be using the template.

And whishy, I wanted to submit the two feature request in mantis but I never received the confirmation mail from the user registration procedure... (as you can guess, my mantis username is ... ploc !).

See you,

Ploc

[Ted]

Oh shoot...  there is a problem with some mail servers not excepting mail because of a lack of reverse DNS.  Lemme try to enable the account.

Make bugs for them as well, if you can.  Thanks.