CMS Made Simple Forums

Thanks wishy and westis...problem solved. The new version is awesome - I love the expanding/collapsing content list. CMS Made Simple is always my first choice for content management - I've used it on a number of sites. It just keeps getting better with each new version.

Keep up the good work!

Here some results of testing cms 0.11

PHP 5.05  Mysql 5.015  Linux

Without eaccelerator

Page Home
Generated in 0.22653 seconds by CMS Made Simple 0.11 (not cached) using 15 SQL queries and 7188832 bytes of memory
Page Content_Types
Generated in 0.226169 seconds by CMS Made Simple 0.11 (not cached) using 15 SQL queries and 7187976 bytes of memory
Page Navigation_Menus
Generated in 0.235193 seconds by CMS Made Simple 0.11 (not cached) using 15 SQL queries and 7188440 bytes of memory
Page Navigation_Menus
Generated in 0.256229 seconds by CMS Made Simple 0.11 (not cached) using 15 SQL queries and 7188440 bytes of memory
Page Navleft
Generated in 0.23844 seconds by CMS Made Simple 0.11 (not cached) using 16 SQL queries and 7190376 bytes of memory
Page navleft_1col
Generated in 0.223762 seconds by CMS Made Simple 0.11 (not cached) using 17 SQL queries and 7197744 bytes of memory
Page navleft_2_col
Generated in 0.21544 seconds by CMS Made Simple 0.11 (not cached) using 14 SQL queries and 7197184 bytes of memory
Page Navtop
Page CSS_Menu
Generated in 0.186309 seconds by CMS Made Simple 0.11 (not cached) using 11 SQL queries and 7178664 bytes of memory

Here the results of my CSSMENU - SPEED-VERSION
Page CSS_Menu
Generated in 0.18343 seconds by CMS Made Simple 0.11 (not cached) using 11 SQL queries and 7054008 bytes of memory

You must see, that the executiontime of 390 pages is nearly the same, the original has there a time of 1,2 seconds.
But you can see, that we  have by the  memory an advantage of 124 KB


Now here the results WITH eaccelerator

Page Home
Generated in 0.054895 seconds by CMS Made Simple 0.11 (not cached) using 13 SQL queries and 1154848 bytes of memory
Page Content_Types
Generated in 0.06091 seconds by CMS Made Simple 0.11 (not cached) using 13 SQL queries and 1153248 bytes of memory
Page Navigation_Menus
Generated in 0.068394 seconds by CMS Made Simple 0.11 (not cached) using 13 SQL queries and 1154448 bytes of memory
Page Navleft
Generated in 0.056008 seconds by CMS Made Simple 0.11 (not cached) using 14 SQL queries and 1154424 bytes of memory
Page navleft_1col
Generated in 0.056843 seconds by CMS Made Simple 0.11 (not cached) using 15 SQL queries and 1161232 bytes of memory
Page navleft_2_col
Generated in 0.079149 seconds by CMS Made Simple 0.11 (not cached) using 14 SQL queries and 1176688 bytes of memory
Page Navtop
Generated in 0.075121 seconds by CMS Made Simple 0.11 (not cached) using 17 SQL queries and 1165800 bytes of memory
Page CSS_Menu
Generated in 0.055962 seconds by CMS Made Simple 0.11 (not cached) using 11 SQL queries and 1158040 bytes of memory

My comment

The Speed of the cms is in progress but the need of memory is too high.

The concept of the cms must changed - scriptparts for the visitors use and for the admin use must be separated

Cannot edit anything with Firefox 1.0.7  and Linux and FCKEditor if there are no default settings of text-align.

If i set a default it works.

If i set a default it works.

But it works only the first time after making the setting.

if i will edit a page with Linux and Konqueror it works without FCKEditor.

If i change something and will save it  i get the error  Wert Inhalt nicht gegeben!

in english  " There is no content"

Oh man that is a big bug.

Most WYSIWYGs don't work in Konqueror or Safari (which is based off of Konq).  However, there should probably be a browser check in FCKeditorX that checks for that and degrades more nicely.

I'll have to get Megabob to look at that.

f i will edit a page with Linux and Konqueror it works without FCKEditor.

If i change something and will save it  i get the error  Wert Inhalt nicht gegeben!

in english  " There is no content"

Yeah but this is in a normal textarea and i can nothing save.

Piratos wrote: Cannot edit anything with Firefox 1.0.7  and Linux and FCKEditor if there are no default settings of text-align.

If i set a default it works.

FCK isn't updated on it.

I am working on it, right now.

Controlling all source and something else.

See You.

Wow is the CSS ever easy to modify for CSSMenu now! Great job guys.
Conversion from .10.3 to .11 only required 4 changes to the CSS Vertical file.

hi,

i updated Version 0.10.4 to 0.11

i dont know, but looks like a bug,

all my Section Headers are know linked to News-Modul-URL,

is there a workaround to fix possible ?

if i add new pages as Section Headers there also linked to this News-Modul-URL in the Menu..

best regards
thom

megabob3 wrote: EllNav seem don't go

Page with only link to other page don't mach good.

There are any news from EllNav?

A member told me, EllNav makes problems with a fresh installation - on a click on the Ellnav entry comes this error:

{nocache:1e48ab6d6529c3031ad1e38279e47f90#1}
Fatal error: Call to a member function on a non-object in /usr/www/htdocs/pczgz/cms/modules/EllNav/EllNav.module.php on line 218

See it at http://www.pczgz.ch/cms/index.php?page=Navigation_Menus

With Tobago no changes  ...

Looks ok to me...

Please click the links "Horizontal (EllNav)" and "Split Menu (EllNav)" then I get also this error ...

Any news on cssmenu and upgrading from .10x to .11?

Previous posts suggest a change in ID's break the upgrade, anyone care to elaborate or detail this? Any ideas on how to fix this without a new install?

Any assistance appreciated.

Cheers,

Shane.

Shane wrote: Any news on cssmenu and upgrading from .10x to .11?

Previous posts suggest a change in ID's break the upgrade, anyone care to elaborate or detail this? Any ideas on how to fix this without a new install?

Any assistance appreciated.

Cheers,

Shane.

Shane, sorry for this. Basicaully ul.cssmenu-vertical (for the vertical CSSMenu) and ul.cssmenu-horizontal (yes, that's right, for the horizontal version ) are no longer output in the CSSMenu html. Replace all instances of these two elements with #primary-nav and you're a big step closer.

However, the CSS has also been simplified/improved, so there are other changes to be made too, for the menu to look proper. I'll elaborate on this later, am already late to work now...

Meanwhile, try the above and report what problems that remain and I can address those specifically.