WordPress 3.0 Upgrade Error Nightmare Finally Solved/Fixed

Can you confirm that your hosting uses cPanel with WHM?

It does, why do you ask?

Because the original theory was that this was linked to cPanel + Pure-fptd specifically. But I (and many others) are running WP on cPanel + Pure-fptd hosting without any problems. Then I began to spot references to WHM + Pure-fptd – which suggest that this might be only be an issue with reseller type accounts where WHM is being actively used.

If we can gather enough anecdotal evidence for a cause and effect, we can:

– add the fix as a sticky post to the forums
– alert forum regulars to they know what to advise
– raise it as an issue with the core devs.

Otherwise, we’re still left with a generic “it’s a server specific permissions thing” – which isn’t exactly helpful to anyone. Right now, I’m just trying to gather evidence.

I see what you mean. I tried literally every thing, timeouts in php files , chmod upgrade folder, deleting different files/folders, this method worked.

Waiting to see if this helps others.

I just posted on the other thread and have just now seen this.

I am a re-seller, and I have this WHM and cPanel problem consistently with all of my, and my re-sold, accounts when trying to do the automatic update.

What info do you need from me to add to your stack of evidence?

-Sherry

Did this method work?

Did this method work?

So far, it’s been the only solution that has been reported as successful. I just think we need to define exactly what server environment is causing the problem.

@sherrynes: Can you try switching from Pure-fptd to Proftp in WHM?

Let us know!