1.1 Development Thoughts

[brady]

This is kind of a weird period in development.  I know that I'm breaking backwards compatibilty with some things as it is.  Should I continue down that road and make some big (though no doubt beneficial) changes?

I think that if you are going to break backwards compatibility you should do it all at once. Make the hard decisions now, so that modules and tags will have a stable API to work with for as long as possible.

[spraek]

I'd like to stress a lot of improvements to the Group Permissions system.

http://forum.cmsmadesimple.org/index.ph ... l#msg44559

Better cram in the basic CMS functionality before adding more.. 

[Ted]

Yes, I agree. Calguy will getting on this at some point in the near future, and is scheduled to be in 1.1.  No idea how we're going to possibly upgrade that, though...

[cyberman]

The rest of the dev team is going to handling the other aspects of 1.1 and have good ideas as to what is going to show.

Would be nice, if the rest of the dev team can tell us something about direction / progress too  ...

[ELVIS]

Hello Ted. I tried a lot of CMS systems (Nucleus CMS, Joomla, Drupal, Typo3, AtLeap, even commercial Bitrix in user mode) and found that they are absolutely inconvenient and too slow to run and hard to maintain. I really want to use CMS Made Simple but it's current multilanguage support is not what I looking for (I mean CMSMS Multilanguage Edition).

In my opinion Multilanguage support should do:
1. Translate content and all strings (even module strings).
2. All translation should do in a same place.
3. Easy look 'what's changed', because I don't translate the content myself but it do my translators.
4. Notify some users (translators) when content had changed (via some complex notify system).

That's the main think that I really see in CMSMS. Thanks for the good begginings! I hope to hear you back.

[cyberman]

Yeah, you're probably right about the adding functions to template lite idea.  The maintenance could become an issue but as long as we're extending existing classes, it's probably not an issue.  I've already had to extend smarty to do some of my bidding as far as plugins that don't cache go...  maybe we can continue by extending Template Lite to add that one function (I don't think I need any of the others).

From http://templatelite.sourceforge.net/

  The release of Template Lite 2.10 - January 4, 2007

I have added support for the use of template resources. The syntax for register_resource is the same as Smarty

[Ted]

Yes, I'm very happy about this fact.  It's most definitely something to look at for 2.0.  I'll probably be testing it in the next week or two to see.

[cyberman]

Hi Ted,

I'll probably be testing it in the next week or two to see.

Any results (I know, I'm nerved  )?

[Ted]

I did get it working on a basic level a little bit ago.  The problem is that I have hacked up smarty so much to get plugins that don't cache their output.  Template lite acts the same way, so I'd have to recreate that hack again.

I didn't see a ton of memory reduction as I played with it, so I'm not totally convinced that it's worth the trouble yet.  I'll dig a little further then I get back into 2.0 development...  which will be in a couple of weeks.

[cyberman]

The problem is that I have hacked up smarty so much to get plugins that don't cache their output.

Hmm, maybe we should found a way back to original so every user can update smarty by himself  ...

I didn't see a ton of memory reduction

Template Engine Memory Usage under PHP 4.4.1

Template Lite 2.10

    * class.template.php - 148,344 bytes
    * class.compiler.php - 175,580 bytes

total 323.924 bytes

Smarty 2.6.13

    * Smarty.class.php - 193,020 bytes
    * Smarty_Compiler.class.php* - 417,532 bytes

total 610.552 bytes

Means a difference of 286.628 bytes so it's interesting for future releases - many pennys makes a dollar  .

[cyberman]

...Perhaps also permission system should be moved to a module

Nice idea, because it rocks KISS. Each feature only once and inside a specific place...

Made many pages with CMSms and need never a cron job. And in my daily support I see many users they dont understand the power of this option. Maybe EventManager should/can be moved from core to a module too (for a better performance).

Yes, you will say, not every time the (same) speed discussion. I know - I'm nerved . But I see performance of CMSms and I see performance of Piratos CMSms fork. There's a (too) big difference for now.

And I like to see CMSms for the best  .

[Pierre M.]

I agree there is currently a too big difference (even without having tried the fork).
But I'm confident the dev team is still doing a nice work toward 2.0 and its full page caching top feature. It will squash performance problems once forever.

Meanwhile your caching module or any reverse caching proxy like Apache's mod_cache can do the job with 1.0.
There are more and more international users, translations, modules, releases, support threads, wiki improvments, hints, show off demos... CMSMS is gaining momentum.

Pierre M.

[cyberman]

Meanwhile your caching module

It cache only content and css so I'll try to use this technologie for a modified index.php ...

[ZYV]

I can't believe I will live up to the moment when the true multilingual system will see the day Remember, that it should permit the user to add an arbitrary number of translations in different languages to each page while keeping the option to leave some of them completely untranslated (so the structure of the site in different languages might be 1:1 identical or completely different). Otherwise it won't be anyhow better than the menu and content block hacks.

[skypanther]

Probably too late for a 1.1 addition, but perhaps for version 1.2 or 2.0: can we get some sort of super-admin capability. I use CMSMS for customer or friend's sites and I want to guarantee my ability to log on as admin after handing over control of the site to them. Right now, if I give them permissions to edit back end users, they can delete or lock out my admin account. It would be great if I could set up a super-admin account (preferrably hidden in the admin UI) to prevent that.

See http://forum.cmsmadesimple.org/index.ph ... cseen.html for another person who could probably use this feature.

Thanks,
Tim