[pLog-svn] r2067 - plog/branches/plog-1.0.1

Oscar Renalias phunkphorce at gmail.com
Tue May 24 12:35:24 GMT 2005


I also agree that it's not a really good fix. First of all because we
should fix this in our code ourselves and because as Jon said, people
with no access to ini_set() will also get errors.

There is no way to check whether ini_set has been restricted by the
admin, because function_exists() will return true even if ini_set is
forbidden. Also, 24M is waaay too much, people have been sucessful
with 10-12mb.

I say we reduce the amout to 16M (to be on the safe side) but leave
the lines commented out. Opinions?

Hopefully this situation will be improved in the future. Reto
suggested using more passing by reference instead of by value, which
should help specially when moving lots and lots of data to the
templates and which is something we could try in 1.0.2, and Ben's
changes in 1.1 will hopefully help too.

Oscar

On 5/24/05, Benjamin Krause <ork at orkland.de> wrote:
> Jon Daley wrote:
> >     This isn't a good fix is it?  Then the users who aren't allowed to
> > call this function, due to safe_mode, etc. will get errors, no?  Maybe
> > if it was called as @ini_set instead?  I can't test it, but I think
> > there have been users on the forums who have gotten error messages when
> > they have tried to do this.
> 
> yeah you're right. we should definitely address those memory issues.
> just setting the memory limit up and up isn't really a fix :)
> i would suggest leaving it the way it is and concentrate on the memory
> usage as part of the 1.1 development. with the new cached DAO objects, a
> lot of memory will be saved already, and we should be able to reduce the
> amount even more.
> 
> Ben
> _______________________________________________
> pLog-svn mailing list
> pLog-svn at devel.plogworld.net
> http://devel.plogworld.net/mailman/listinfo/plog-svn
>



More information about the pLog-svn mailing list