CMSMS 2.0 (say what now?!)

Anastasis · **Posted:** Thu Apr 05, 2007 7:19 am

Ted wrote:

Yup, totally agreed. Users, groups, permissions (including viewing) will all work in the frontend as well as the backend. It won't be as powerful as FEU is now, but we'll have some way to extending the users to have the same power as FEU in the future with modules.

Sorry, I have obviously missed something - what is FEU? Sorry to be dim.

cyberman · **Posted:** Thu Apr 05, 2007 7:38 am

Anastasis wrote:

what is FEU?

Means existing FrontEndUsers module

...

Anastasis · **Posted:** Thu Apr 05, 2007 10:54 am

cyberman wrote:

Anastasis wrote:

what is FEU?

Means existing FrontEndUsers module

...

Aha! Should have realised - sorry. Another TLA in the bag!

pgoneill · **Joined:** Wed Apr 19, 2006 2:37 pm **Posts:** 101

Ted wrote:

Yup, totally agreed. Users, groups, permissions (including viewing) will all work in the frontend as well as the backend. It won't be as powerful as FEU is now, but we'll have some way to extending the users to have the same power as FEU in the future with modules.

This is great to hear. Keep up the good work, Ted and everyone!

aozuas · **Joined:** Mon Dec 04, 2006 8:26 pm **Posts:** 120

Ted, I just wanted to say that CMSMS is marvelous and I am really excited with the 2.0 release near coming.
After try almost every CMS out there I simple fell in love with CMSMS.
I am using it in almost all sites I had made in the few months, and this include the following:
http://www.las.ufsc.br
http://www.dzo.com.br
http://www.yogashanti.pro.br
http://www.drsamirhaje.com
http://www.renatotapado.com

And others.

I keep the credits in all sites in this line of code:

Code:

<meta name="Generator" content="CMS Made Simple - Copyright (C) 2004-6 Ted Kulp. All rights reserved." />

The PHP5 will be a problem to me in release 2, but I agree that is very important!

Keep the good work and thank you (and all the community) for this great and magic peace of code.

Just to finish: somebody suggested and I agree that include something like http://codepress.org/ in CMSMS is a good idea!

From Brazil,

Aleph
www.ciberarte.com.br

Anastasis · **Posted:** Fri Apr 06, 2007 11:14 pm

aozuas

Congratulations on some excellent websites. As someone who is just beginning to experiment with CMSMS and have not yet built my first site with it, these are very encouraging to me to show what CMSMS can do no matter what the style of site on the outside.

Thanks for sharing them.

cyberman · **Posted:** Wed Apr 11, 2007 9:56 am

Ted wrote:

all the things mentioned in the 1.1 thread apply... including being PHP5 only.

If we get a PHP5 only system why not make a real break?

PHP 5.1 has included PDO support. Via PDO we can get access to mysql, postgres and sqlite.

If we would using this we don't need a performance eating database layer like adodb anymore

...

Milhaus · **Posted:** Wed Apr 11, 2007 10:15 am

cyberman wrote:

Ted wrote:

all the things mentioned in the 1.1 thread apply... including being PHP5 only.

If we get a PHP5 only system why not make a real break?

PHP 5.1 has included PDO support. Via PDO we can get access to mysql, postgres and sqlite.

If we would using this we don't need a performance eating database layer like adodb anymore

...

Agree. Most hosts who have PHP 5+ have PHP 5.1+. I think it would be great if new CMSMS will be really "future" CMS. PHP4 is becoming history. In the meantime, maybe it will be necessary to keep 1.x version secure for unfortunates.

Pierre M. · **Posted:** Wed Apr 11, 2007 1:22 pm

Hello,

cyberman wrote:

PHP 5.1 has included PDO support. Via PDO we can get access to mysql, postgres and sqlite.

If we would using this we don't need a performance eating database layer like adodb anymore

...

Database engine agnosticism ? Drop of another performance eater ?
Yeehoo! You have two strong points.
Pierre M.

cyberman · **Posted:** Fri Apr 13, 2007 10:11 am

If we will use AdoDB (not lite) furthermore there's another solution.

AdoDB has his own cache mechanism so we can also eliminate Static HTML Generation as well.

Please read this tutorial

http://www.phpfreaks.com/tutorials/110/1.php

Pierre M. · **Posted:** Fri Apr 13, 2007 12:23 pm

Thank you for the link. I've just read one page.
This adodb caching mechanism can empower MySQL for sure. But NOT "so we can also eliminate Static HTML Generation as well" IMHO. I think full static HTML/CSS page caching is better : not only it doesn't need db access, it doesn't need PHP CPU/mem as well.
Pierre M.

cyberman · **Posted:** Sun Apr 15, 2007 9:58 am

Pierre M. wrote:

But NOT "so we can also eliminate Static HTML Generation as well"

Sorry, this was a quote from tutorials page

...

styson · **Joined:** Fri Apr 06, 2007 9:46 pm **Posts:** 56

Ted wrote:

Yup, totally agreed. Users, groups, permissions (including viewing) will all work in the frontend as well as the backend. It won't be as powerful as FEU is now, but we'll have some way to extending the users to have the same power as FEU in the future with modules.

When you integrate the users into both front and back, I hope you design it so the Front end users can be local in CMSms OR in another system (LDAP, Acitve Directory, custom). Obviously the bridge for authentication to the other system would be a custom module developmed by those who need it first

I say this because tomorrow I'm recommending to a client that we use CMSms and I'll be modifying the FEU module to authenticate users against another system. How easy/hard this will be only time will tell but architecting the core so it can accept this in the future would be awesome.

What I see for the next release is great as well.

Foden · **Joined:** Mon Jan 08, 2007 10:26 am **Posts:** 30

About the user / group handling...

Will it be made so that you can assign ownership of a set of pages to a group? And then add editors to that group, instead of adding them to each page?

That feature could be nice

/ Thomas

styson · **Joined:** Fri Apr 06, 2007 9:46 pm **Posts:** 56

Foden wrote:

About the user / group handling...

Will it be made so that you can assign ownership of a set of pages to a group? And then add editors to that group, instead of adding them to each page?

That feature could be nice

/ Thomas

And be able to secure content based upon groups, including shopwing/hiding navigtation.

CMSMS 2.0 (say what now?!)

Who is online