Everybody Staze...

Nobody leavz...

  • Home
  • About Me
    • LinkedIn
    • Lab
  • Contact
  • Links
  • Reviews
  • Sitemap
  • Weather
You are here: Home / Archives for automatic update

WordPress auto-update

2010/02/15 By staze

Just a quick note. WordPress 2.9.2 came out today, and I found that since my server upgrade, the core auto-update/upgrade feature wasn’t working. It wanted me to have FTP access.

Turns out that the website folder itself (in my case, since I host on a Mac, a folder within /Library/WebServer/Documents) wasn’t owned by www. Once I chowned that to www, the auto-upgrade worked perfectly.

Everything else was already owned by www… so, just make sure, the folder wordpress resides in is also owned by the web user (the user httpd runs as).

Good luck! And remember, Happiness is only a chown away.

Filed Under: Sys Admin Tagged With: automatic update, update, upgrade, Wordpress

Automatic plugin updates

2009/06/07 By staze

Just thought I’d add to the world’s collective knowledge by posting this tidbit…

I’ve been wresting with trying to get wordpress’s automatic plugin update to work for the past hour or two, and just figured out what was going on.

First, I had to install the SSH2 plugin for php. Info on that can easily be found via google. Once you have that installed, and the php.ini changed to load the plugin, restart the webserver and make sure it’s loaded (phpinfo()).

Okay, so, once that was done, I saw the SSH option for the autoupdate. Looking around, people said to use “localhost” as the hostname, since the connection seems to be initiated from the webserver. I guess this field really only matters if you have a separate ftp/sftp server than the webserver.

So, next hurdle is to create a user that has it’s “home directory” or “root” set to the wordpress install directory. Since I’m hosting on a Mac, this is /Library/WebServer/Documents/staze.org/. So, now, things should work, right?

Nope. Kept getting “unable to locate wordpress plugin directory”. As it turns out, most inaccurate error message ever. I tested again and again with various settings, and all I kept getting was “unable to locate wordpress plugin directory”.

So, turns out, apache (or php maybe?) doesn’t like ACLs. I previously had the web directory owned by an admin user, with www as the group, then ACLs set for the www user. No good. Once I chowned everything over to the prevebial “www:www”, things immediately worked.

So really, the error message should have been saying “unable to write to plugins directory” or something like that.

*sigh*

Going to create another post for the other things going on…

Filed Under: Sys Admin Tagged With: automatic update, plugin, Wordpress

Weather

Categories / Archives

  • Apple
  • Coding
  • Electronics
  • Energy
  • Home Ownership
  • Miscellany
  • Politics
  • Prius
  • Sys Admin
  • Travel
  • Uncategorized
  • Work
  • June 2026
  • April 2026
  • August 2025
  • April 2025
  • January 2024
  • February 2021
  • July 2020
  • January 2020
  • April 2019
  • March 2018
  • February 2018
  • June 2017

Copyright © 2026 · Staze On Genesis Framework · WordPress · Log in