CMS Made Simple Forums

Though, I am impressed that it's working enough that a small bug like that is causing an issue. 

Quick note.  I posted an update on the blog about 2.0 development this morning.

http://blog.cmsmadesimple.org/2008/02/1 ... ong-again/

Just read it. Excitement builds. Keep it up.

I must confess that I really am curious what the new version will look like and how it will "feel". Sounds really good, Ted!

Well, I'm hoping the feel of it stays the same.  I like the admin with it's clearly defined parts that can be swallowed in bits and pieces.  Sometimes it means you have to click around a little more when you're a more advanced user...  but that's what the bookmarks are for.

It will, however, get an upgrade on look a little bit.  Mostly to clean up the html but also make it look a little more contemporary.

I don't know if someone is updating the standard theme of the admin panel...

I've made some changes on the admin theme  for myself (and always work with my own since then), so...

.... if anyone doing this needs help with CSS or design... contact me!

Ted,
Are you going to include the ability to increase the php memory allowed:

ini_set('memory_limit','32M');

The problem we who have no control over the ini file have to use the line in our config.php or the site can have no modules other than the basics.

I am pretty sure this can only be set by the server admin, a .htaccess file or .ini file. Not by any normal php script.

HuttonIT wrote: Ted,
Are you going to include the ability to increase the php memory allowed:

ini_set('memory_limit','32M');

The problem we who have no control over the ini file have to use the line in our config.php or the site can have no modules other than the basics.

This is a per-server issue.... not a cms issue.  some servers disable ini_set but allow stuff in .htaccess, some servers do the opposite, some servers do both.... there is no point in doing stuff like this and putting an option into a webpage someplace when only 'some' webhosts will listen to it.

This is a per-server issue.... not a cms issue.  some servers disable ini_set but allow stuff in .htaccess, some servers do the opposite, some servers do both.... there is no point in doing stuff like this and putting an option into a webpage someplace when only 'some' webhosts will listen to it.

Thanks calguy but if there is no way of raising the default PHP memory allowed there are lots of us who will be stuck on Ver 1.2.3 or go else where.  There needs to be serious thought to a work round as that was the work round for most.  It may not be CMSMS issue but it does become one when we have to abandon CMS in the search of a system which will work. 
Some server providers are not interested in listening as they claim it is a security risk or a drain on resources....  What they mean is that they either don't know or their servers are over loaded, flakey and old.

CMS 2.0 will require PHP 5 anyways.... which usually raises the memory limit significantly by default.

so, some people will have to migrate to new servers anyways.... not much we can do about that.

If your hosting company doesn't increase it for you, it's time to find a new host.

I find it hard to believe that they wouldn't, given current standards, as they stand to lose a lot of customers.

Nullig

PHP 5 as standard has a 128mb memory limit anyway on most hosts.

You have to move with the times I am afraid. PHP 4 is far too old.

I am not saying I don't have the facility to increase the memory but it is a work around again and not the server being set by the supplier to what would be considered reasonable by programmers. 
My host has both PHP4 and PHP5 and I can increase the memory by adding a file to root of my site php.ini and adding the one line memory_limit = 32M.
It works fine for me but as for 128MB I think they may bitch a bit at that as a modern server with only 1GB of memory and 1,000 websites on it with 20% using php they are asking for a crash.

Thanks anyway for the input it is just that I have encountered the problem and many developers do sometimes forget that must users don't have the same access levels to servers, the knowledge and know how they have, luckily for me they are good at what they do though.

Keep the good work up and I am look forward to a release version of 2.

Don't forget, this is a memory limit per request.  It's main purpose is to make sure that scripts don't run away, allocation a TON of resources and kill the server for the other requests.  It's meant to be a safety measure, not a measure of how well php can perform on a server.  This really shouldn't need to be tweaked, as the chances of a script that isn't flailing wildly out of control using 128 megs is pretty darn rare.  I hope that server administrators acknowledge this fact.

For those of you who care about these things, php 5.2.0 changed the default to a slightly more reasonable 16 megs.  PHP 5.2.1 upped it to 128 megs.  The 2.0 core will work within the confines of the 16 meg limit because 5.2.0 is the minimum requirement (right now a "regular" page render with menus, blog & comments uses about 6 megs -- that's 10 extra megs to play with for modules and stuff).

However, I see no reason to mess with the memory_limit.  If you're using enough modules to go over that limit, then chances are that you know what you're doing to fix it, or can at least google it.  It's one of those 80/20 issues that's best left to the "advanced" users and not causing potential support issues for us from the "newbies".