Core Rollback

描述

Seamless rollback of WordPress Core to latest release or any outdated, secure release using the Core Update API and core update methods. Only latest release and outdated, secure releases are offered.

Refer to https://api.wordpress.org/core/stable-check/1.0/

Usage

From the Tools menu select Rollback Core, select the version you wish to rollback to from the dropdown and click Rollback. You will be directed to the update-core.php page where you should see a button to Re-install your specified version. If you move away from the update-core.php page before clicking the Re-install button you will have 15 seconds to return and complete the process or you will need to start over.

In multisite use the Settings menu.

WARNING: Downgrading WordPress Core may leave your site in an unusable state requiring a complete reinstall or a forced reinstall using WP-CLI, wp core update --force --version=5.5.3. It may also leave your site broken due to a plugin or theme incompatibility. Use at your own risk.

Rollbacks use your current locale.

PRs are welcome.

螢幕截圖

  • Tools menu item
  • Rollback Core action dropdown
  • Re-install Now button for rollback

評價

閱讀全部1個評價

貢獻者及開發者

“Core Rollback” 是一個開源的軟體。以下的人對這個外掛作出了貢獻。

貢獻者

Core Rollback 外掛目前已有 2 個本地化語言版本。 感謝所有譯者為這個外掛做出的貢獻。

將 Core Rollback 外掛本地化為台灣繁體中文版。

對開發相關資訊感興趣?

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

修改日誌

1.1.1 / 2021-10-14

  • use sanitize_title_with_dashes() as sanitize_file_name() maybe have attached filter that changes output

1.1.0 / 2021-07-07

  • add @10up GitHub Actions for WordPress SVN

1.0.1 / 2020-12-4

  • fix text-domain in string, thanks Alex

1.0.0 / 2020-11-17

  • initial release to dot org repository
  • add Class Bootstrap to intiate process
  • updated instructions, etc
  • add assets, screenshots, banners, icon
  • add readme.txt and clean up create_admin_page()
  • add warning notice to settings
  • add force-check query arg to redirect to more consistently display the Re-install Now button.
  • limit rollbacks to WP > 4.0, I found some non-recoverable issue in my local testing
  • initial release