miahz

I was confused was like almarma. I was on 3.1 and wanted to try 3.2 beta via automatic updating with the Beta Tester plugin. With Point release nightlies selected it linked to “3.1-latest.zip”. Which didn’t seem to be what i wanted. With Bleeding edge nightlies selected it linked to “nightly-builds/wordpress-latest.zip”. But that didn’t seem right either. I didn’t want nightlies — i wanted the beta “point release” aka 3.2 beta 2.

Eventually i just tried them both. First the Point release nightlies, which put me on 3.1.2 something — which is older than the current stable 3.1.3 (latest.zip). Odd.

Then i tried the Bleeding edge nightlies option. It installed ok, but at the bottom is said i was on 3.1.2-alpha.

It wasn’t until i clicked to the main dashboard page that it said i was on 3.2-beta2-18145. And the “3.1.3 update available” notification was still displayed on a couple pages.

It all seems far too confusing. I get that the plugin name probably implies “beta testers” in the generic sense, not necessarily a specific “beta release”. And perhaps the nightlies aren’t any more scary than the labeled beta downloads. But it can be misleading. I don’t always want to run nightlies, but i am more comfortable installing official betas and release candidates. Perhaps a new update channel could be added to the plugin for pre-release point releases like betas and RCs.

I just started using this plugin and i’ve already had a few odd results. A the same time i changed WordPress’s discussion options to allow comments by default instead of moderating, because i figured this plugin should take care of that.

But i’ve had a few comments tagged as Blocked by CFC land as approved comments on posts. What’s more, at least two of them have been link dump comments that should have been blocked by WP’s built-in More than X links rule. I’m not sure who’s to blame there.

#7745: Private posts cannot have unpublished or pending review status
http://trac.wordpress.org/ticket/7745

Just happened to me. This is not cool. It’s at least a bug or serious UI problem, and maybe even a small security issue.

I was working on a draft, and checked ‘Keep this post private’ then clicked the save button. That oddly made the post Private, and removed it from Draft status (it no longer was in the Drafts list)—in my mind those are two exclusive concepts—one post could be both private and a draft (a private post, but not finished being written).

Then, i unchecked ‘Private’ on that post and clicked save. I left it like that for a day, not thinking much of it.

When i returned to write more, the post was neither in Private nor Drafts. It was Published! What was basically my rough notes for a post i was working on had been published, and i had never clicked the Publish button!

That cannot be right.

So my rough notes were sitting out in the wild for a day before i realized what happened.

Thanks, Kafkaesqui. That plugin should do the trick on my own site. I wonder if there will be any way around it on wordpress.com blogs.

edit:
Just found wpc/forums and posted there:
http://wordpress.com/forums/topic.php?id=98&replies=1

I upgraded to 1.5, and pings to “real” sites in the wild haven’t worked, but i was able to ping podz’ test blog. Not sure what the difference is. I guess i just need to test it more.

Actually, you delete the old files first, then upload the new ones, because sometimes all the files aren’t overwritten. Just a precaution.

I used the upgrade instructions from Codex to upgrade from a 1.3 nightly to a 1.5 nightly and it worked fine.
As macmanx said: “backup first.” I saved my database with phpMyAdmin and the actual files via FTP.

I personally went with the delete everything then upload the new nightly files method. Since i just backed up everything, i could just copy back anything i still needed. Then run upgrade.php. No problems. That was with the 2005-01-22 nightly, and i’m about to do it all again with a more recent one.