WordPress Bêta Tester

Description

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

Une fois installé, elle vous permettra de mettre à jour votre site à la dernière version bêta ou « Release Candidate » en cliquant sur le bouton « Mettre à jour ».

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

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

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.

FAQ

Installation Instructions
  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

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!

Must-have for any theme or plugin developer

This plugin works great, as advertised.

A lot of people complain that you can’t revert the DB changes. I bet (hope) that they are not plugin developers. The plugin warns you about this. You are meant to keep a backup of your site first. If you are testing in a container such as docker or a VM, then it’s even easier.

This highlights the issue that user reviews are not always reliable. A lot of users click on plugins and run arbitrary code on their sites without even reading the readme, then they come here and complain. Makes you wonder if there should be a feature on this site for users to rate the usefulness of reviews. Oh well, I’m getting side-tracked!

Anyway, thanks for a great plugin.

Good. But Please note:

Good. But Please note: (This is the bleeding edge development code which may be unstable at times. Only use this if you really know what you are doing.)

A Must have Developer Plugin

Very useful to test plugins against latest beta/rc versions.

But keep in mind, that this plugin is designed for developers only to use it on their development sites – never try to use it on a production site! you may not to be able to go back to stable releaes!

Excellent – Usage: For Development testing ONLY

I see a lot of 1 star reviews from people who obviously do not understand what this plugin is for. It is ONLY for Development testing and should ONLY be installed on a Development site/server. This plugin should ONLY be used by Coders and Developers (plugin authors, theme authors, custom coders) to test their code against the latest non-Publicly released WordPress versions. If you install this plugin on a Development site then there would be no reason to change to a publicly released Production version of WordPress since this plugin is ONLY for Development sites/servers and NOTHING else.

If you want to install and use this plugin then create a Development WordPress website (a copy of your Live Production website). If you accidentally installed this plugin on a Live Production website then restore your website from a backup.

Lire les 33 avis

Contributeurs & développeurs

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

Contributeurs

“WordPress Bêta Tester” a été traduit dans 9 locales. Remerciez l’équipe de traduction pour ses contributions.

Traduisez « WordPress Bêta 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.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