wpupgrade not working?
-
Anonymous
UnregisteredHey all
Just a quick question:
Has anyone had any issues going from 3 to 3.01 using the multisite version of WordPress even when using the wpupgrade ssh method?
Error I get is:
Warning: copy(/home/UserName/public_html/mySite.com/public/wp-includes/Text/Diff/Engine/xdiff.php) [function.copy]: failed to open stream: Permission denied in /home/UserName/public_html/mySite.com/public/wp-admin/includes/class-wp-filesystem-direct.php on line 200
Cheers in advance!
Posted 1 year ago # -
Gary Robar
MemberI think the http://vpsbible.com/content-management/wordpress3-lemp-guide/ has a wrong bit of code.
In the section where you add a chunk of stuff to bashrc to make the commands wpupgrade work, there are some inconsistencies with the variable names.
guv can you comment?
Posted 1 year ago # -
cdroo
MemberI haven't had a chance to play, myself, with the bashrc. I do like the fact that the defaults are pretty secure... However, for upgrades I set the ownership to Nginx via chown recursively (-R) for the whole directory containing the site. A reboot later on resets this anyway back to the default. I'd probably prefer the bashrc bit to be optional in the script. Next config I do I'll probably remove it. The command line isn't that scary. ;-)
Posted 1 year ago # -
hey y'all .. i think likely the export commands (export USER="vpsUserName" etc) could be lost somewhere.
log in as root and follow the tut, they're all changed now to ensure the export variables will be recognized.
mr roo .. i separated the bashrc commands a while back, they're all rightly optional, not set in as before which, apart from other things, had meant the same command was being replicated in the bashrc file for multi WP installs!
.. which reminds me.
folks, if you want to run the bashrc alias shortcut thing then before you do, check your bashrc file and clear out any old, possibly incorrect command:-
nano /home/USERNAME/.bashrc
scroll to the bottom and you'll recognize my spiel to delete.
Posted 1 year ago # -
Using Stack for 3.01
.. hopefully this will help Dan and others ..
the best thing is to install 3. then, after log into the Dashboard, upgrade the core to the WP latest version.
Posted 1 year ago # -
Andrew Bell
MemberHi
I am getting a similar message.
Warning: copy(/home/andrew/public_html/mysite.co.uk/public/wp-app.php) [function.copy]: failed to open stream: Permission denied in /home/andrew/public_html/mysite.co.uk/public/wp-admin/includes/class-wp-filesystem-direct.php on line 200message.Not sure how I can fix it to get the automatic update working.
Info: I have used the Ubuntu LEMP stackscript and the wordpress 3 for LEMP stackscript to install wordpress etc from scratch.
I then added the script for wpupgrade wpsafe commands.
Posted 1 year ago # -
Justin Sonter
MemberHi there,
I was getting the same errors on trying to upgrade to WP3.01. In order to get past this file permissions error I changed the commands given in the .bashrc file for wpupgrade and wpsafe to chown the /public directory instead of the /wp-admin.
ie: "sudo find /home/USERNAME/public_html/DOMAIN/public -exec chown -R www-data:webmasters " etc..
After doing this, WP went through the update ok and reported success but when I go back to the dashboard it says I'm still on ver 3.0 and that I should upgrade to 3.01!
Plugins install ok although WP Super-Cache tells me that "Mod Rewrite might not be installed".
Posted 1 year ago #
Reply
You must log in to post.
Want HTML?
a blockquote code em strong ul ol liPlace code between backticks `codeHere`
You've got it.