CMS Made Simple Forums

Very nice work.
In the new version, could you also incorporate the long-awaited multi-lingual support (in official release)?

Thanks

hi there
please add multilingual support. i know you've decided not to do that, cause for 90% of the users the system will become more difficult wihtout any use, but i think this should be a standard feature of a modern cms. i want to suggest you a possible solution for this dilemma, why not design a single-lingual version and besides that a multi-lingual one? so everyone should be satisfied... or you can solve this problem by a multilang-module for example?
greets
christian

Hello,

NashBridges wrote: i want to suggest you a possible solution for this dilemma, why not design a single-lingual version and besides that a multi-lingual one?

Do you mean CMSms 1.x and CMSms 2.x ? It has been existing for ...years ? Do you like this "solution" ?

Pierre M.

Where can i join the testers list?

ironblaze94 wrote: Where can i join the testers list?

A call for beta testers will go out when we're close to ready for a beta... we aren't yet.

Yesterday, I completely removed xajax from the CMSMS 1.7 core.  it was one of the big things (infact it was THE big thing) that caused problems with PHP 5.3 compatibility.

The xajax stuff (used for the funky hilighting and re-ordering stuff in listcontent, and for the preview stuff in editcontent/addcontent) has been replaced with some funky classes written by Ted that use jquery to do the same thing.

This means, that YES...  CMSMS will come with Jquery... maybe we'll change some of the default templates in 1.7 to show off the jquery support.

calguy1000 wrote: This means, that YES...  CMSMS will come with Jquery... maybe we'll change some of the default templates in 1.7 to show off the jquery support.

*does a happy dance*

Sure, I may not have a clue how to recreate the drag/drop reordering thing yet using jquery, but we'll think of something.  Hopefully without the 2nd screen.

Oh, and one more little thing.  The ORM is getting pulled in as well.  I'm not rewriting everything to use it, but it will get used for a few key things, most notably content/pages.

...talking about ajax and jquery...

Could this FRbe included in 1.7?

It's very useful for fast pages finding without using "CTRL-F" in browser.

But it's only a suggestion, assign priority to most important stuff. This is only an aesthetic FR.

regards
blast

Ted wrote: *does a happy dance*

We will see the video appear somewhere on the web..... 

Ronny

I really support the feature request of blast2007 (search field on the pages backend), in fact it is the first point of my customers wishing list.

calguy1000 wrote: The xajax stuff (used for the funky hilighting and re-ordering stuff in listcontent, and for the preview stuff in editcontent/addcontent) has been replaced with some funky classes written by Ted that use jquery to do the same thing.

Will these classes become available for moduledevelopers also?

far in the future it would be nice to load the tabs via ajax. that reduces load at the first tab since the whole page with all tabs is loaded atm in admin area.

if this is a common request, i'll make a feature request in the forge

@Jos:

Will these classes become available for moduledevelopers also?

Yes.... the files will just be in the lib directory... you'll be able to use them as much as you want.

@SimonSchaufi
This would be a complete rewrite of alot of code... so it's definitely 'out of scope' for 1.7....

calguy1000 wrote: @Jos:

Will these classes become available for moduledevelopers also?

Yes.... the files will just be in the lib directory... you'll be able to use them as much as you want.

i think he means if the javascript files will already be included in the header in the file moduleinterface.php so no need for self including the files.

calguy1000 wrote: @SimonSchaufi
This would be a complete rewrite of alot of code... so it's definitely 'out of scope' for 1.7....

of course

i think he means if the javascript files will already be included in the header in the file moduleinterface.php so no need for self including the files.

No, the javascript calls will not AUTOMATICALLY be included in every frontend page.  There'll be a fair bit of stuff in there, so most people wouldn't want ALL that javascript included automatically.  So you'll either have to include it manually with the appropriate tags, or we may provide some funky smarty tag method for including things... we haven't thought that far yet.