0.11beta6 Released!

Ted · **Posted:** Wed Nov 30, 2005 2:11 am

From the front page:

Quote:

Yes, yes, we know! We REALLY didn't want to make another release, but it's REALLY necessary. In fact, we need this one tested, because of some major last minute changes that could break existing sites.

If you have a site that is in another language (and therefore, another encoding), we need the upgrade process tested ASAP. If you have a site written in German, French, Swedish, Norwegian, Italian or any other ISO-8859-X encoding, we need you to copy it to another location and upgrade. After the upgrade, make sure that when you edit, the content still shows correcty.

The plan is to release this Friday, so please test it as soon as you can and we can get this release out and as bug free as possible sometime this week!

Basically, the details go like this...

Before beta6, every language could specifiy their own encoding for their translation. Most of the European languages used ISO-8859-x encodings. English used UTF-8. However, this encoding change was a pain, because you either had to set the encoding of each template to match, or change default_encoding in config.php to match the admin language.

I've decided from here on out that all languages should be utf-8 instead. Yes, that might alienate some older browsers, but I think it's a risk worth taking.

So, now, no matter what the language in the admin, all of output will be the same encoding. This is a great thing as we move ahead, because it won't require noobies to change encodings just to get their language to work.

However, this creates a problem for existing sites. If the language encoding doesn't match the encoding in the existing content, it's not going to look right when you edit a page (or the template, or News, etc).

So, for certain situations, we're going to have to force the admin to display in the old encoding so that it matches. So, I've added an admin_encoding parameter to config.php and doing my best job to change it according to various existing settings. However, there could be a situation where it could need to be adjusted.

What does admin_encoding do? If the language translation is in utf-8 and the admin is displaying iso-8859-15, then the admin translation will look wrong. Good question. However, the beauty is this... I've found code to modify the encoding of languages on the fly. So, even though the strings are in utf-8, they're being converted to whatever is in admin_encoding automatically to match the content in the database.

It's a win-win situation. Existing stuff still works. New sites will be more language and noob friendly.

What would be the ultimate solution is to convert existing content to utf-8, but because of modules and other stuff, I didn't want to go there. That's an exercise left up to the reader.

cyberman · **Posted:** Wed Nov 30, 2005 1:27 pm

No real bugs, but

- the archive doesn't contain the uploads and uploads/images directory
- the URL output isn't xhtml-valid (IMHO & instead & - found for breadcrumbs)
- in adminlog.php I get this output for timestamp:

Code:

Wed Nov 30, 2005 11:07:39 Westeurop�ische Normalzeit

"Westeurop�ische" comes from server and can't be affected by user. Perhaps date format "T" in line 78

Code:

perhaps in admin echo "<td>".date("D M j, Y G:i:s T", $row["timestamp"])."</td>\n";

should be deleted :-?

...

cyberman · **Posted:** Wed Nov 30, 2005 1:50 pm

Admin section isn't fully localized - please make a look in group assignments (changegroupassign.php) and group permissions (changegroupperm.php). There I found in source code "Group Name" and "Select a Group" in english

...

Patricia · **Posted:** Wed Nov 30, 2005 1:55 pm

Cyberman and everyone else, please report bugs in the bug tracker of the cmsmadesimple project in the forge.
http://dev.cmsmadesimple.org/tracker/?group_id=6

I myself didn't do what I preach

and forgot to fill a bug report about what you mention for hardcoded language ...

Cheers

melix · **Posted:** Thu Dec 01, 2005 10:08 am

My site is in French and pages look ok. But I've submitted a rather annoying bug : my content list is definitely empty.

Piratos · **Posted:** Thu Dec 01, 2005 2:39 pm

PHP 5.05
Apache 2.055
Mysqli 5.0.15

Fresh installed 6.898.784 MB - this cms is more and more an memory eater.

You should spare memory or millions of domains with 8 mb scripbase cannot use this cms.

Piratos · **Posted:** Thu Dec 01, 2005 2:40 pm

Quote:

6.898.784 MB

Must be Bytes - cannot correct it here.

Server on Debian Sarge Linux.

roman · **Posted:** Thu Dec 01, 2005 3:54 pm

Piratos, for memory usage is http://sk.php.net/memory_get_usage function, how many bites you have on HDD is not important, also operating system have on HDD 400-2000 MB, and in memory 20-200 MB in ONE time

Ted · **Posted:** Thu Dec 01, 2005 4:14 pm

Quote:

Generated in 0.184069 seconds by CMS Made Simple 0.11 (not cached) using 13 SQL queries and 5620664 bytes of memory

Fresh install of svn on debian sarge linux.

I'm sorry, but I don't see that as unreasonable. The thing is actually doing something under there...

Either it's caching stuff because it's too slow and using memory, or it's using too much memory, so the caching comes out and it's too slow.

I'm trying my best to walk the delicate line between memory usage and speed here. *shurgs*

tamlyn · **Posted:** Thu Dec 01, 2005 6:52 pm

I love the new default template and content - it looks so much more professional straight 'out of the box' and we all know how much first impressions count. However, I already know how good cmsms is and I don't really like having to trawl through deleting all the content, templates and stylesheet associations and stylesheets. It took me almost 10 minutes! I propose a tick box in the install process for "install default content" which is ticked by default but can be unticked by experienced users to save time.

I don't have any non-english content so can't comment on that...

Piratos · **Posted:** Thu Dec 01, 2005 7:24 pm

Quote:

Generated in 1.379602 seconds by CMS Made Simple 0.11-beta6 (not cached) using 15 SQL queries and 6919616 bytes of memory

First call after starting Linux. Showing page home.

Standardmodules installed (first install) - cssmenu, ellnav,fckeditor x, news.

Piratos · **Posted:** Thu Dec 01, 2005 7:27 pm

Quote:

Piratos, for memory usage is http://sk.php.net/memory_get_usage function, how many bites you have on HDD is not important, also operating system have on HDD 400-2000 MB, and in memory 20-200 MB in ONE time

That is where the results comes from (memory_get_usage function).

Piratos · **Posted:** Thu Dec 01, 2005 7:29 pm

The second call with cache is:

Quote:

Generated in 0.236661 seconds by CMS Made Simple 0.11-beta6 (cached) using 15 SQL queries and 6898544 bytes of memory

Piratos · **Posted:** Fri Dec 02, 2005 10:59 am

$ADODB_COUNTRECS

If the database driver API does not support counting the number of records returned in a SELECT statement, the function RecordCount() is emulated when the global variable $ADODB_COUNTRECS is set to true, which is the default. We emulate this by buffering the records, which can take up large amounts of memory for big recordsets. Set this variable to false for the best performance. This variable is checked every time a query is executed, so you can selectively choose which recordsets to count.

$ADODB_COUNTRECS = false is one of the High Speed ADOdb - tuning tips !!

So let us test if this make this cms faster or spare memory and how big is the limit of the cms with the latest versions of apache, php and mysql - i'm using the mysqli - driver of adodb.

Cache was always deleted - ADODB_COUNTRECS always set to false in include.php before calling adodb.

Page Home
Generated in 0.315405 seconds by CMS Made Simple 0.11-beta6 (not cached) using 14 SQL queries and 6966584 bytes of memory

Page Content Types
Generated in 0.356179 seconds by CMS Made Simple 0.11-beta6 (not cached) using 14 SQL queries and 6965760 bytes of memory

Page Menus / Navigation Systems
Generated in 0.245252 seconds by CMS Made Simple 0.11-beta6 (not cached) using 14 SQL queries and 6966136 bytes of memory

Page Vertical - Bulletmenu
Generated in 0.282925 seconds by CMS Made Simple 0.11-beta6 (not cached) using 15 SQL queries and 6968216 bytes of memory

Cache was always deleted - ADODB_COUNTRECS always set to true (that is the adodb default) in config.php

Page Home
Generated in 0.294467 seconds by CMS Made Simple 0.11-beta6 (not cached) using 14 SQL queries and 6966584 bytes of memory

Page Content Types
Generated in 0.309264 seconds by CMS Made Simple 0.11-beta6 (not cached) using 14 SQL queries and 6965760 bytes of memory

Page Menus / Navigation Systems
Generated in 0.293889 seconds by CMS Made Simple 0.11-beta6 (not cached) using 14 SQL queries and 6966136 bytes of memory

Page Vertical - Bulletmenu
Generated in 0.312063 seconds by CMS Made Simple 0.11-beta6 (not cached) using 15 SQL queries and 6968216 bytes of memory

Result - in the most times with only some pages the performance with $ADODB_COUNTRECS set to false is not better it is slower !

Try a volume of 640 pages - showing default page $ADODB_COUNTRECS set to false or true

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 4864 bytes) in

Try a volume of 240 pages - showing default page $ADODB_COUNTREC set to false

Generated in 0.67406 seconds by CMS Made Simple 0.11-beta6 (not cached) using 15 SQL queries and 7708096 bytes of memory

Try a volume of 240 pages - showing default page $ADODB_COUNTREC set to true

Generated in 0.699239 seconds by CMS Made Simple 0.11-beta6 (not cached) using 15 SQL queries and 7708096 bytes of memory

With more pages $ADODB_COUNTRECS set to false is a little bit faster.

Try to list a volume of 240 pages with admin listcontent - same result with $ADODB_COUNTREC true or false

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 419840 bytes) in /opt/lampp/htdocs/ctest/admin/listcontent.php on line 387

Ted · **Posted:** Fri Dec 02, 2005 1:53 pm

Very intersting....

I think my next order of business after 0.11 goes out today is to tune the memory usage. I'm not quite sure where to start, to be honest.

Actually, since I'm not going to release until later on today/tonight, I'm going to take a stab at trying to find some of these issues now.

However, I have a feeling that they're ADODB related for the most part, which kind of scares me.

I am open to other options on an abstraction library that is like ADODB, though I would really miss the table creation functions and it would make installation (of the core and modules) much more difficult for different database platforms.

But if it would help performance, then I'm interested.

Let me see what I can do through the day and I'll report back.

0.11beta6 Released!

Who is online