[wp-testers] Plugin update not working

[Stephen Rider]

On Jan 1, 2009, at 7:48 AM, DD32 wrote:

> Anyway, Heres an alpha release of a plugin i'm working on:
> http://dd32.id.au/files/core-control.zip
>
> * Activate that,
> * Then head over to the "Core Control" options page,
> * Activate the HTTP module  & Updates module
> * Head into the HTTP page (its up the top there)
> * Click "Test" on the Primary transports, If one fails to work, Click
> "Disable Transport" (most likely you'll do this to the cURL transport)

cURL:  An Error has occured: name lookup timed out

I Disabled cURL

PHP fopen(): Successfully retrieved & verified document from http://tools.dd32.id.au/wordpress/core-control.php

PHP fsockopen(): Successfully retrieved & verified document from http://tools.dd32.id.au/wordpress/core-control.php

> * See if the updates work properly:

With cURL disabled, I successfully auto-updated a plugin

> * Now, Head into the Updates tab now (up the top again)
> * Force an update check to occur for the plugins by clicking the  
> link (You
> can do Themes/Core too if you so wish)

Plugin update check worked -- no new updated found.
(Incidentally, Update *check* has been working, just no the actual  
auto-update on plugins

> Report back with any errors that it throws up, Hopefully it might  
> shed some
> light.
>
> Just to repeat, That plugin is alpha, and not release quality, Its  
> UI needs
> some work, and some of the modules code is horrible :) (Well..  
> actually its
> bloody beautiful compared to some WP plugins I've seen recently...)

The plugin looks as though it has good potential for troubleshooting  
and certain development tasks.  (Actually the ability to "check for  
update now" is going to help me with another thing I'm working on,  
so... Cool! :-)

Regards,
Stephen


> 2009/1/1 Stephen Rider <wp-hackers at striderweb.com>
>
>> The problematic test server is running MAMP on Mac OS 10.5.6.
>>
>> Plugin updates used to work fine.  I'm pretty sure I was updating  
>> even in
>> WP 2.7 (certainly in beta versions).  I can't say what change might  
>> have
>> triggered the error.
>>
>>
>> On Dec 30, 2008, at 4:47 PM, DD32 wrote:
>>
>>> "Couldn't resolve host" means that its having DNS issues.. Now why  
>>> PHP
>>> would have issues, yet browsers don't is odd.
>>>
>>> Sounds like it could be a HTTP API issue with one of the  
>>> transports on
>>> your computer..
>>>
>>> I'll get back to you later with some way of listing them.. dont  
>>> have the
>>> time to look it up right now, so unless someone else pops in and  
>>> tells you
>>> what transports you're running.. :)
>>>
>>> 2008/12/31 Stephen Rider <wp-hackers at striderweb.com>
>>>
>>> I get this error on my test setup in WP 2.7 any time I try to auto- 
>>> update
>>>> a
>>>> plugin:
>>>>
>>>> Downloading update from
>>>> http://downloads.wordpress.org/plugin/some-plugin.2.1.zip
>>>>
>>>> Download failed.: Couldn't resolve host 'downloads.wordpress.org'
>>>>
>>>> Plugin upgrade Failed