For what it's worth, I have my resource limits in my "php.ini" file(s)
set as follows and I haven't had a problem with the auto-upgrade:
max_execution_time = 120 ; Maximum execution time of each script, in
seconds
max_input_time = 120 ; Maximum amount of time each script may spend
parsing request data
memory_limit = 32M ; Maximum amount of memory a script may consume
(10MB)
Anything less than 32 MB (and possibly having a max execution time of
less than 30 secs) may cause the problem you're seeing. The auto upgrade
for me takes no more than 10 to 12 secs max so I would think memory
limits are set too low.
On 10/24/2008 5:32 PM, Ryan Boren wrote:
On Fri, Oct 24, 2008 at 6:49 AM, Xavier Borderie<[EMAIL PROTECTED]> wrote:
Just to confirm issue is still there for revision 9247.
Yep, Havnt gotten around to submitting another patch for the notice fixes
yet :)
Not wanting to sound pushy or anything :)
I still can't seem to properly ugrade with 2.7-almost-beta-9300
(un-l10n install, trunk-r9324.zip from Trac).
wordpress-latest.zip is sitting in /wp-content, but still no no
/wp-content/upgrade/ to be found.
Clicking the Upgrade button displays two lines ("Downloading update
from http://wordpress.org/nightly-builds/wordpress-latest.zip"; and
"Unpacking the core update"), then nothing - and no footer. No more
notices, though ;)
That sounds like PHP is dying on the spot. Are there any errors in
the server log? We have to unzip in memory, so maybe we're hitting
the memory limit.
Ryan
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
