[solved]can't upgrade wordpress after site moved

7 posts / 0 new
Last post
#1 Wed, 12/17/2008 - 08:24

[solved]can't upgrade wordpress after site moved

Hi there!

I have a site that was moved to a new directory some time ago, and now I can't upgrade wordpress. [code:1] Downloading http://wordpress.org/latest.zip .. Received 103424 bytes ... more of these ... Received 1758208 bytes .. download complete.

Configuring Apache PHP settings .. .. already done. Now installing WordPress version 2.7 .. Failed to extract source : Failed to create target directory : mkdir: cannot create directory `/home/username': Permission denied .. failed! See the error message above for the reason why. [/code:1]

The directory shown (/home/username) is the old directory where it was installed before, so I'm sure it's related to the move. It should be /home/users/username (the new folder).

I grepped /usr/libexec/usermin and /var/webmin for "/home/username" and found no references.

Any idea on where I should be searching for this outdated reference?<br><br>Post edited by: kato, at: 2008/12/17 20:32

Wed, 12/17/2008 - 08:28

Yeah, I imagine WordPress is setup for a given directory at install time.

I'm not sure whether or not that's a problem that can be solved in some automated way by Virtualmin -- but if it is, Jamie would be your man. I'd recommend filing a bug so that he can take a look, using the Bugs and Issues tracker below.


Wed, 12/17/2008 - 08:42 (Reply to #2)
Wed, 12/17/2008 - 10:25 (Reply to #3)
ronald's picture

for that domain find the correct folder in &quot;/etc/webmin/virtual-server/scriptlog&quot;
open up the file and change the &quot;opts_dir=/correct path goes here&quot;

its a little hard as the folders and files are numbered..
Im sure the script will update correctly after that.

Wed, 12/17/2008 - 10:27 (Reply to #4)

In the bug, Jamie recommended this command to find the id of the domain:
virtualmin list-domains --id-only --domain whatever.com

Wed, 12/17/2008 - 13:29 (Reply to #5)
ronald's picture

thx for posting, it will come in handy as I had to change those files for like 8 domains or so and had to go the path of trial and error :)

Wed, 12/17/2008 - 20:31 (Reply to #6)

This was solved in the bug report linked above and a very easy fix, for anyone hunting answers.

Topic locked