So I ran the latest version of this plugin for the 4.2 beta. After release, as I did in previous beta cycles, I deactivated it and attempted to upgrade to the release version. No dice. Even manually installing the 4.2.x files leaves me in 4.3 alpha mode.
Any solutions? Anyone?
Gene Steinberg
]]>WHAT it does it does wel, that is, install versions other than the latest stable, but the usefulness for checking my plugins under the latest RC is lacking..
]]>https://www.ads-software.com/plugins/wordpress-beta-tester/
]]>According to the plugin settings: “By default, your WordPress install uses the stable update stream. To return to this, please deactivate this plugin.” So I deactivated it, but still I keep receiving many emails like: “SUCCESS: WordPress was successfully updated to WordPress 4.2-beta4-32051” Anything else I need to do?
PS: In a future release I would appreciate an additional option where you can turn off the email notifications. I use the plugin only on a blog that serves no other purpose than testing, where this information is not actually needed and it would be great not to have to dig into the code to make manual changes. Thanks!
https://www.ads-software.com/plugins/wordpress-beta-tester/
]]>1. IF I disable the plugin (but leave it installed), what happens to my installation when WordPress reaches the actual 4.2 public release?
2, IF I disable the plugin (and uninstall it), what happens to my installation when WordPress reaches the actual 4.2 public release?
The reason that I ask these questions is that up-until-now, anytime I did one of the above two actions: my installation would inadvertently continue on the next alpha release path (even though I didn’t want it to). Has this plugin’s update to version 1.0 changed that scenario?
I guess what I’m looking for is a usable “In or Out” or “Stop or Go” option for this plugin.
https://www.ads-software.com/plugins/wordpress-beta-tester/
]]>