Brian1
Forum Replies Created
-
So since the ownership/groups/permissions are all the same for these files the implication is that the WordPress installation changes its ID?
Please note the last column in the screen capture is the user and group.
So the user and group for all these files are the same.
I’m personally convinced that this is a server owner/permissions problem. Do you have access to the server’s error logs?
But the process is failing in the copying of files from the upgrade folder to the installation part way through. The files that it is copying over are all the same permissions and ownership.
Check out this screenshot;
http://www.burtsgh.com/dl/ScreenShot032.gifYou can see this is a section of the css folder where the installation fails and all permissions and ownerships are identical.
When trying to WordPress Autoupdate, make sure that you FIRST:
0. Delete the Upgrade folder completely from your server
1. Go into your Plugins page
2. Click the checkbox above all of them to select ALL plugins
3. From the pulldown, select DEACTIVATE, then OK it
4. Try the update again – that usually takes care of the errors for me.
5. Don’t forget to re-enable your plugins as in Steps 1-3Tried all this and the result was Could not copy file.: /wp-admin/css/theme-editor.dev.css Which has been documented many times in the forums by others.
Re: the pureftp to proftp issue I have read of people who this has not helped and my service provider claims that proftp is “Not seen this one before! If it is a bug with pure-ftpd then I’m afraid there is no recourse for action; Proftpd is slower, uses more memory and generally has a worse security record so we won’t be switching to it.”
So I am back to a wordpress bug.
For me I go to cPanel and look at the section “software services” and choose “php configuration”. Mine shows directive memory limit 64M.
Hello Folks,
I to am having this problem. I have had my PHP memory limit increased to 64M and I de-activated all my plug-ins.
Is this a know bug in WordPress?