[wp-trac] Re: [WordPress Trac] #9275: Automatic Core Update feature not working if PHP is not CGI

WordPress Trac wp-trac at lists.automattic.com
Fri Mar 6 23:08:52 GMT 2009


#9275: Automatic Core Update feature not working if PHP is not CGI
--------------------------+-------------------------------------------------
 Reporter:  bloggersavvy  |       Owner:     
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  2.8
Component:  Upgrade       |     Version:  2.7
 Severity:  normal        |    Keywords:     
--------------------------+-------------------------------------------------

Comment(by DD32):

 > Needless to say, these are outrageous numbers, so if the issue was time
 or memory requirements, I think they are ruled out.

 Yep, That pretty much rules out timeouts and memory problems.

 > The plugin Upgrade/Install, only works if I first manually upload the
 new plugin files.
 In other words, You're not using automatic upgrade at all.

 >Oh!... and if I leave PHP as CGI, here's an example error (in the front
 end: .... session_start() [function.session-start]: ... Permission denied

 That points out what the problem is, When you're running php under apache,
 Its running as the Apache username, Now that you've moved to apache + cgi,
 Its running under a different username, and as such That plugin can no
 longer open the files it created as the other user

 The problem seems to be here that either you dont have *any* transports
 available to you, Or, Whichever one you do have is having an issue with
 your server.

  * Install this plugin: http://wordpress.org/extend/plugins/core-control/
  * Activate it
  * Load its Settings page
  * Check "Filesystem Module" & Save Module Choices
  * Open the Filesystem tab along the top of the screen now

 Can you tell me which transports are available, & Which is the current
 one?

 You can try disabling the current one, and seeing if the upgrade will work
 via the next one it flicks onto.



 > I'm on Apache 1.3.39 and PHP 5.2.5 I cannot upgrade yet as it would
 trash the video server (another PHP based site)
 Thats interesting, So.. WordPress is trying to upgrade the video site
 instead of itself?

 I guess that means you're using FTP, When you connect via FTP, what path
 do you see? ie. /public_html/wordpress.site/ and /public_html/video.site/
 or something different? Whats your ABSPATH (You can find that on the
 filesystem module page too)

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/9275#comment:6>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list