Re: [wp-testers] Plugin update not working

2009-01-02 Thread Stephen Rider


On Jan 1, 2009, at 9:27 PM, DD32 wrote:


2009/1/2 Stephen Rider wp-hack...@striderweb.com:

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


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


I somewhat thought that would happen, I dont know why, But i suspect
cURL bundled with PHP with MAMP is crippled.. or maybe the timeout for
curl's lookup is just too short.. no idea why


I'm quite sure something changed with WP 2.7.  This all worked before  
-- I didn't change MAMP, but I did upgrade WP.  Though again, it *was*  
working with WP 2.7 betas, so maybe something else on my computer is  
screwy



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

Which is odd.. Given that if one fails, they should both fail.. It
could just be that cURL works 50% of the time..


It's a pretty precise 50%.  Update checking worked (seemingly)  
normally, but actual updates failed every time.


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! :-)


Thats the main purpose of it :) But i'm planning on basing a few small
modules off it, I'm sick of building a dozen tiny plugins for random
uses which might only be used once, I wanted something i could just
add it as a seperate module which would hopefully be of use to someone
else in some form :) -


BTW, I updated your core plugin this morning, and now the front page  
is blank.  (The one that lets me turn modules on/off.)



That.. And some way I could update the plugin
without having to submit the 1-liner to wordpress.org..
Got any thoughts on other modules which would be helpful to plugin  
developers?


You might put in a module that shows everything in the wp-cron and  
allows the user to run them with a button.  A sort of stripped-down  
crontrol.


You could also put in something that shows the wp-rewrite info and/or  
the mod_rewrite stuff that WP writes to .htaccess


As for existing one-liner plugins, how about...

Toggle post revisions and autosave:
http://exper.3drecursions.com/2008/07/25/disable-revisions-and-autosave-plugin/

At any rate, you might set your plugin up so that third-party devs can  
make modules.  That probably includes making a module folder  
*outside* of your plugin's folder, so the third-party modules are not  
overwritten on auto-update.  (I really wish WordPress would figure out  
a standard for such things -- there are a lot of plugins that allows  
third-party add-on files.)


Stephen
___
wp-testers mailing list
wp-testers@lists.automattic.com
http://lists.automattic.com/mailman/listinfo/wp-testers


[wp-testers] Theme see details link is wrong

2009-01-02 Thread Stephen Rider

Hi --

In WP 2.7 -- one of my themes has an update available, but the link to  
go to the page is wrong.  Under the theme Barthelme I have this  
message:


There is a new version of available. _View version Details_ automatic  
upgrade unavailable for this theme.


So... two things --

1. The grammar of the message needs a fix (or at least one more  
period), and


2. The details link is actually the theme preview link

Stephen
___
wp-testers mailing list
wp-testers@lists.automattic.com
http://lists.automattic.com/mailman/listinfo/wp-testers


[wp-testers] Spamming comment from email very slow (2.7)

2009-01-02 Thread Kirk M
Hey folks,

I've come across a rather consistent problem with the 2.7 Admin when marking a 
comment as spam (or approving or deleting it) from the Spam it link in a 
notification email. It takes upwards of 45-50 seconds to accomplish once the 
comment is marked as spam from the resulting admin page to where the comment 
ends up in the spam queue.

However, if I spam a comment from the admin's comment page rather than the 
admin page launched by the Spam it link in the email, it only takes a few 
seconds to accomplish the same task. Any ideas why this may be occuring? The 
rest of the 2.7 admin runs nice and quick even without Gears enabled (I'm using 
Firefox 3.1 builds--not compatible with Google Gears yet). I've tested this 
with other browsers set as default and it's the same thing.
___
wp-testers mailing list
wp-testers@lists.automattic.com
http://lists.automattic.com/mailman/listinfo/wp-testers


[wp-testers] wp_schedule_single_event() acting funny

2009-01-02 Thread scribu
Hello, new to this list.

I was working on a plugin using wp_cron and I noticed some strange
behaviour when using wp_schedule_single_event().

I've written this test plugin: http://wordpress.pastebin.ca/1298571

If I set it to a time in the past, like

  wp_schedule_single_event(time(), CRON_HOOK);

it fires twice on every page load.

If I set it in the future, say

  wp_schedule_single_event(time()+15, CRON_HOOK);

it just fires once, even if I clear the hook first.

Any ideas?

I'm using WP 2.7.1-alpha-10188 on localhost (Ubuntu 8.10 + LAMP).

-- 
http://scribu.net
___
wp-testers mailing list
wp-testers@lists.automattic.com
http://lists.automattic.com/mailman/listinfo/wp-testers


Re: [wp-testers] Plugin update not working

2009-01-02 Thread DD32
2009/1/3 Stephen Rider wp-hack...@striderweb.com:
 I'm quite sure something changed with WP 2.7.  This all worked before -- I
 didn't change MAMP, but I did upgrade WP.  Though again, it *was* working
 with WP 2.7 betas, so maybe something else on my computer is screwy

The orders of the transports may've been changed, Theres 5 HTTP
transports as you can see, I think one of them was higher than cURL at
one point, so curl probably wasnt used.. It could also be that the
code that was working before hadnt been converted to the new HTTP API
when you were testing..

 It's a pretty precise 50%.  Update checking worked (seemingly) normally, but
 actual updates failed every time.

Since it works half the time, and only on specific requests, It sounds
like its having problem with the request being made, It might be that
it doesnt like binary data, or a hostname.. Whilst that may sound
stupid.. well.. it is stupid..

 BTW, I updated your core plugin this morning, and now the front page is
 blank.  (The one that lets me turn modules on/off.)

Grrr. I commited what i had to SVN last night, Turns out the
WordPress.org packer decided that it'd offer that update to everyone
(even though it has no readme.txt).. The actual problem is the 'inc'
folder got deleted, The WordPress.org plugin packer doesnt include
svn:externals, http://trac.wordpress.org/ticket/8611 which is a major
anoyance to me.. I like the idea of having a common svn:external i can
rely upon..
(Hmm..  Maybe it just doesnt like non-wordpress.org externals? Maybe i
should try that..)
You can create a folder 'inc' and add this file to it:
http://svn.dd32.id.au/wp-plugin-dd32-common-class/class.dd32.php to
get it working again if you wish :)

 You might put in a module that shows everything in the wp-cron and allows
 the user to run them with a button.  A sort of stripped-down crontrol.

Sounds good to me :) Never thought of cron

 You could also put in something that shows the wp-rewrite info and/or the
 mod_rewrite stuff that WP writes to .htaccess

Could be useful too, Thanks :)

 As for existing one-liner plugins, how about...

 Toggle post revisions and autosave:
 http://exper.3drecursions.com/2008/07/25/disable-revisions-and-autosave-plugin/

I was toying with the idea of if i should rewrite 'Revision Control':
http://wordpress.org/extend/plugins/revision-control/ to be a module
(I've got to rewrite it eitherway), but think i'll leave that as a
separate plugin, its not really aimed at developers.. I might include
a striped down version though.

 At any rate, you might set your plugin up so that third-party devs can make
 modules.  That probably includes making a module folder *outside* of your
 plugin's folder, so the third-party modules are not overwritten on
 auto-update.  (I really wish WordPress would figure out a standard for such
 things -- there are a lot of plugins that allows third-party add-on files.)

Yeah.. I'm supposed to be rewriting part of the plugin upgrader for
trunk right now.. i was going to work something like that in.. but..
its difficult for plugins which were not automatically
upgraded/installed, the upgrader changes the foldername to the
wordpress.org slug, ie. 'dd32-revision-control' now becomes
'revision-control', and it'd have to manually move the files it was
told not to delete into the new folder in the right place, etc..

Thanks for your feedback :)
___
wp-testers mailing list
wp-testers@lists.automattic.com
http://lists.automattic.com/mailman/listinfo/wp-testers