WordPress Beta Tester

外掛說明

這個外掛提供了參與 WordPress Beta 版測試的簡單方式。

安裝並啟用這個外掛後,點擊按鈕便能透過內建的升級程式將網站升級至 Beta 版本或發行候選版本。

依照預設,外掛啟用後便會將網站切換至小數點版本頻道。

對於勇於嘗鮮的使用者來說,可以選擇切換到最新的開發版本 (Trunk)。

網站升級前,請不要忘記進行全站備份。

歡迎在 GitHub 上提出提取要求。

螢幕擷圖

  • 外掛管理頁面

安裝方式

  1. 將壓縮檔解壓縮所得的外掛資料夾上傳至 /wp-content/plugins/ 目錄中
  2. 請於 [外掛] 頁面啟用這個外掛。
  3. 前往管理後台的 [設定] -> [Beta 版測試] 設定外掛。
  4. 前往多站網路管理後台的 [設定] -> [Beta 版測試] 設定外掛。
  5. 前往 [控制台] -> [更新] (3.0 之前版本為 [工具] -> [升級]),然後更新至最新的 Beta 版本。

使用者評論

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!
閱讀全部 37 則使用者評論

參與者及開發者

WordPress Beta Tester 外掛為開源軟體。以下人員為這個外掛做出了重大貢獻。

參與者

WordPress Beta Tester 外掛目前已有 20 個本地化語言版本。 感謝所有譯者為這個外掛做出的貢獻。

將 WordPress Beta Tester 外掛本地化為台灣繁體中文版

對開發相關資訊感興趣?

任何人均可瀏覽程式碼、查看 SVN 存放庫,或透過 RSS 訂閱開發記錄

變更記錄

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