=== WordPress Beta Tester  ===
Tags: beta, advanced, testing
Contributors: westi, mlteal, afragen
Tested up to: 4.9
Requires at least: 3.0.5
Stable Tag: 1.2.3
License: GPLv2
License URI: http://www.opensource.org/licenses/GPL-2.0
Requires PHP: 5.2.4

Allows you to easily upgrade to Beta releases.

== Description ==
This plugin provides an easy way to get involved with Beta testing WordPress.

Once installed it will enable you to upgrade your website to the latest Beta or Release candidate at the click of a button using the built in upgrader.

By default once enabled it switches your website onto the point release development track.

For the more adventurous there is the option to switch to the bleeding edge (trunk) of development.

Don't forget to backup before you start!

PRs are welcome on [GitHub](https://github.com/afragen/wordpress-beta-tester).

== Changelog ==

= 1.2.3 =
* updated a few strings and correct typos
* run through WPCS linter
* fixed translation strings to include HTML in context and properly escape with `wp_kses_post()`
* fixed link to settings page under Multisite

= 1.2.2 =
* change wording from blog to website

= 1.2.0 =
* Escape output
* Indicate that _Bleeding edge nightlies_ are _trunk_
* new screenshot
* code improvements from linter

= 1.1.2 =
* Remove anonymous function for PHP 5.2 compatibility.

= 1.1.1 =
* fixed PHP notice for PHP 7.1
* made URL scheme agnostic

= 1.1.0 =
* Fixed to work properly under Multisite.

= 1.0.2 =
* Update tested up to version to 4.7.
* Fix the location of the settings screen in Multisite (moved under Settings in Network Admin).
* Minor text fixes.

= 1.0.1 =
* Update tested up to version to 4.5.
* Fix PHP7 deprecated constructor notice.
* Change text domain to match the plugin slug.
* Update WordPress.org links to use HTTPS.
* Remove outdated bundled translations in favor of language packs.

= 1.0 =
* Update tested up to version to 4.2.
* Update screenshot.
* Fix a couple typos.

= 0.99 =
* Add support for HTTPS urls on WP.org as well as non-HTTPS ones.

= 0.98 =
* Unforce HTTPS for all api.wordpress.org requests.

= 0.97 =
* Force HTTPS for all api.wordpress.org requests.

= 0.96 =
* WordPress 3.4.x compatibility fixes

= 0.95 =
* Further WordPress 3.2 compatibility fixes from nacin
* Addition of activate and deactivate hooks to clear down the update core transient.

= 0.94 =
* WordPress 3.2 compatibility fixes from dd32

= 0.93 =
* Fixed a bug in the point release nightlies stream whereby we displayed the downgrade message erroneously

= 0.92 =
* Add support for converting WordPress mu installs over to WordPress 3.0 RC 1 dev track

= 0.91 =
* Fix bug which causes the message to always display

= 0.90 =
* Added a big error message to warn people that there configuration is going to downgrade the version of WordPress they have installed

= 0.81 =
* Fixed an issue in the version mangling for the bleeding edge develpment track which didn't handle the x.9 => y.0 transition
* Added translation files for Albanian and French.

= 0.8 =
* Fixed noticed on dashboard after upgrade and before the update api data was refreshed
* Added translation files for German, Bosnian, Italian, Polish and Romanian.

= 0.7 =
* Completed support for translations
* Added translation files for Japanese
* Fixed issue with calls to get_preferred_from_update_core() when running on a cron hook.

= 0.6 =
* Update the code to validate the returned upgrade url so as to ensure that we only offer to upgrade to builds that exist.

= 0.5 =
* Initial Release containing support for switching your blog to point release nightlies or bleeding edge nightlies

== Upgrade Notice ==

= 0.97 =
* This update forces https for all WordPress.org API requests please report issues here: http://core.trac.wordpress.org/ticket/18577

= 0.95 =
* Further WordPress 3.2 compatibility fixes from nacin

= 0.94 =
* WordPress 3.2 compatibility fixes from dd32

= 0.92 =
Added support for upgrading WordPress MU to WordPress 3.0 dev builds using built-in upgrader.
Updated Russian language pack.

== Installation ==

1. Upload to your plugins folder, usually `wp-content/plugins/`
2. Activate the plugin on the plugin screen.
3. Navigate to Tools ... Beta Testing to configure the plugin.
4. Under Mulitsite, navigate to Settings ... Beta Testing to configure the plugin.
5. Visit Dashboard ... Upgrade (Or Tools ... Upgrade in versions before 3.0) and update to the latest Beta Release.

== Screenshots ==

1. This shows the administration page for the plugin