[wp-forums] Sticky might be needed re: Earthlink 3.0 upgrade fails
macmanx at gmail.com
Wed Jun 30 23:42:17 UTC 2010
Thank you! I can't even put to words how surprised and grateful I am for the extend that you went to investigate and solve the issue. This level of support and dedication by developers is just something that I don't hear about much in the open source world.
Thank you again!
On Jun 30, 2010, at 3:53 PM, Andrew Nacin wrote:
> I will be posting the following into the threads below, once the nightly
> builds refresh in 6 minutes.
> I have been in touch with Earthlink and have identified the following:
> Earthlink runs PHP 5.0.5, at least for the affected sites and for the
> testbed they provided me. We have identified a single line of code in
> WordPress 3.0 that causes a fatal error in PHP 5.0.5 due to a bug that the
> PHP team fixed in 5.1. It appears this bug also affects PHP 4.4.
> I have committed a change for WordPress 3.0.1, to be released in July, to
> ensure compatibility.
> In the meantime, you may do any ONE of the following:
> Option 1. Download the WordPress Beta Tester plugin, use the "Point release
> nightlies" update stream, and upgrade WordPress. This will upgrade you to
> WordPress 3.0.1-alpha. You can disable the plugin after you are done.
> Option 2. Download the latest build for WordPress 3.0.1:
> http://wordpress.org/nightly-builds/wordpress-3.0-latest.zip. You may
> replace all core files (wp-includes and wp-admin) to get all changes made
> for 3.0.1 so far. Or, to fix this one issue, you may also simply upload
> wp-admin/includes/post.php from the downloaded package to your server.
> Option 3. If you know how to apply a patch, see the "Unified Diff" link at
> the bottom of http://core.trac.wordpress.org/changeset/15359. You could also
> make this change directly to wp-admin/includes/post.php.
> If you are so inclined, I would also contact Earthlink support and suggest
> you wish to run PHP 5.2 or greater. Hosts generally have a greater vested
> interest in upgrading their servers when users voice concern.
> I would also strongly encourage upgrading to WordPress 3.0.1 when it is
> released, and always ensure you are using the latest and greatest version of
> For reference, this is the Trac ticket I handled this issue in:
> On Tue, Jun 29, 2010 at 7:47 PM, Andrew Nacin <wp at andrewnacin.com> wrote:
>> One of those threads is five months old, so I'm not sure it's just 3.0?
>> Symptoms seem to be all over the map.
>> I may contact Earthlink and see if they can shed any light on the issue. In
>> the past some of us have signed up for accounts or asked for sandboxes on
>> hosts so we can test and see what's going on.
>> If you can shed any light on it, let us know.
>> On Tue, Jun 29, 2010 at 4:32 PM, Chris Olbekson <chris at c3mdigital.com>wrote:
>>> I have been providing support for a user in this thread
>>> http://wordpress.org/support/topic/416873?replies=10 regarding not being
>>> able to use quickpress or the post editor. Upon further investigation it
>>> seems that this is a major issue regarding Earthlinks server settings.
>>> following threads all describe pretty much the same problem when upgrading
>>> to 3.0
>>> I am doing a transfer to a new host for one of the effected sites and the
>>> user has given me ftp and wp permissions so I will be investigating to see
>>> if root of the problem can be found. Earthlink is running php 5 and
>>> everyone is able to set memory limit to 64MB.
>>> [image: Chris Olbekson]
>>> (713) 581-4107
>>> [image: C3MDigital.com] <http://c3mdigital.com>
>>> [image: Facebook] <http://facebook.com/c3mdigital>[image:
>>> Google] <http://www.google.com/profiles/c3mdigital>[image:
>>> Flickr] <http://flickr.com/photos/chris_olbekson>[image:
>>> wp-forums mailing list
>>> wp-forums at lists.automattic.com
> wp-forums mailing list
> wp-forums at lists.automattic.com
More information about the wp-forums