WordPress Beta Tester

Description

Cette extension permet de participer aux tests bêta de WordPress.

Une fois installé, elle vous permettra de mettre à niveau votre site vers la dernière version bêta ou « Release Candidate » d’un simple clic depuis l’outil de mise à jour.

Par défaut, une fois activé, elle passe votre site sur les mises à jour de type : « Version nocturne (point release nightly) ».

Pour les plus aventureux, il y a la possibilité de basculer votre site sur les mises à jour de type : « Version en cours de développement (Bleeding edge nightlies) ».

N’oubliez pas de faire une sauvegarde avant de commencer !

PRs are welcome on GitHub.

Captures d’écran

  • Cela affiche la page d’administration de l’extension.

Installation

  1. Ajoutez-la à votre dossier d’extensions, généralement wp-content/plugins/.
  2. Activez l’extension.
  3. Accédez au menu « Outils » puis « Test Bêta » pour configurer l’extension.
  4. Under Mulitsite, navigate to Settings … Beta Testing to configure the plugin.
  5. Accédez au « Tableau de bord » puis « Mise à jour » (ou « Outils de mise à niveau » dans les versions antérieures à 3.0) et mettez à jour avec la dernière version bêta.

Avis

WordPress Beta Using performance

I am a very new user of WordPress Beta Tester but I never show as a supporter as WordPress Beta Tester there has all item available and plugins also amazing. The installation system is very easy as a new member/user I am feeling exiting any hesitation wasn't working in my mind. I was thinking for a short time I am playing an interesting game.

So far looks good, but if…

So far looks good. Thank you for all your continuous effort to make WP better. It but would have been even nicer, to have a full set a built-in cookie disclaimer for GDPR compliance. Can you please add a cookie (may be filtered by cookies name) preference filter disclaimer with different level for visitors to choose from. Which disables all cookies deploy until the visitor accept one of the cookie level option. There could be a section where the WP developer/designer can have fields to add all the required cookie info and a option to categorise their importance for the filtering for the front end. Thanks. Kindest Regards Jay Vijay

Not recommended for 4.8.3

When I activated my plugins page returns 503: Server runs out of time. Deactivated this plugin and all back to normal. Not recommended for 4.8.3!
Lire les 37 avis

Contributeurs & développeurs

« WordPress Beta Tester » est un logiciel libre. Les personnes suivantes ont contribué à cette extension.

Contributeurs

“WordPress Beta Tester” a été traduit dans 19 locales. Remerciez l’équipe de traduction pour ses contributions.

Traduisez « WordPress Beta Tester » dans votre langue.

Le développement vous intéresse ?

Parcourir le code, consulter le SVN dépôt, ou s’inscrire au journal de développement par RSS.

Journal

1.2.6

  • remove extraneous code
  • add GitHub Plugin URI header

1.2.5

  • fixed error message for downgrading version, thanks @andreas-andersson

1.2.4

  • don’t use $GLOBALS

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