Changeset 1708032
- Timestamp:
- 08/03/2017 08:38:07 PM (9 years ago)
- Location:
- wp-safe-updates
- Files:
-
- 6 edited
- 1 copied
-
tags/1.2.2 (copied) (copied from wp-safe-updates/trunk)
-
tags/1.2.2/readme.md (modified) (1 diff)
-
tags/1.2.2/readme.txt (modified) (2 diffs)
-
tags/1.2.2/wp-safe-updates.php (modified) (2 diffs)
-
trunk/readme.md (modified) (1 diff)
-
trunk/readme.txt (modified) (2 diffs)
-
trunk/wp-safe-updates.php (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
wp-safe-updates/tags/1.2.2/readme.md
r1708022 r1708032 12 12 ## How does it work? 13 13 14 This plugin adds a "test update" button when plugin updates are available. Clicking it triggers the creation of a sandbox where the user can safely test updating plugins without affecting the live site. Once the user is finished testing the plugin, they can go back to the live site and do updates if they like.14 This plugin adds a "test update" button when plugin updates are available. Clicking it will trigger the creation of a sandbox where you can safely test updating plugins without affecting the live site. Once finished testing the plugin, you can go back to the live site and do the real updates if all is well. 15 15 16 The sandbox works similarly to how WordPress multisite works. We tell WordPress to temporarily use a different database prefix and a different plugins directory while in the alternative heap (sandbox). This is done by sending WordPress a special _alt_heap cookie.16 The sandbox works similarly to how WordPress multisite works. We basically tell WordPress to temporarily use a different database prefix and a different plugins directory while in the sandbox, which means while you test the update, no changes are made to the live site. 17 17 18 18 ## Screenshots -
wp-safe-updates/tags/1.2.2/readme.txt
r1708027 r1708032 5 5 Requires at least: 4.5 6 6 Tested up to: 4.6.1 7 Stable tag: 1.2. 17 Stable tag: 1.2.2 8 8 License: GPLv3 9 9 License URI: http://www.gnu.org/licenses/gpl-3.0.html … … 13 13 Test WordPress plugin updates safely before applying them on the live site. 14 14 15 This plugin adds a "test update" button when plugin updates are available. Clicking it triggers the creation of a sandbox where the user can safely test updating plugins without affecting the live site. Once the user is finished testing the plugin, they can go back to the live site and do updates if they like.15 This plugin adds a "test update" button when plugin updates are available. Clicking it will trigger the creation of a sandbox where you can safely test updating plugins without affecting the live site. Once finished testing the plugin, you can go back to the live site and do the real updates if all is well. 16 16 17 The sandbox works similarly to how WordPress multisite works. We tell WordPress to temporarily use a different database prefix and a different plugins directory while in the alternative heap (sandbox). This is done by sending WordPress a special _alt_heap cookie.17 The sandbox works similarly to how WordPress multisite works. We basically tell WordPress to temporarily use a different database prefix and a different plugins directory while in the sandbox, which means while you test the update, no changes are made to the live site. 18 18 19 19 **Disclaimer** -
wp-safe-updates/tags/1.2.2/wp-safe-updates.php
r1708027 r1708032 4 4 * Plugin URI: https://github.com/anttiviljami/wp-safe-updates 5 5 * Description: Test WordPress plugin updates safely before applying them on the live site. 6 * Version: 1.2. 16 * Version: 1.2.2 7 7 * Author: @anttiviljami 8 8 * Author URI: https://github.com/anttiviljami … … 11 11 */ 12 12 13 /** Copyright 201 6Antti Kuosmanen13 /** Copyright 2017 Antti Kuosmanen 14 14 15 15 This program is free software; you can redistribute it and/or modify -
wp-safe-updates/trunk/readme.md
r1708022 r1708032 12 12 ## How does it work? 13 13 14 This plugin adds a "test update" button when plugin updates are available. Clicking it triggers the creation of a sandbox where the user can safely test updating plugins without affecting the live site. Once the user is finished testing the plugin, they can go back to the live site and do updates if they like.14 This plugin adds a "test update" button when plugin updates are available. Clicking it will trigger the creation of a sandbox where you can safely test updating plugins without affecting the live site. Once finished testing the plugin, you can go back to the live site and do the real updates if all is well. 15 15 16 The sandbox works similarly to how WordPress multisite works. We tell WordPress to temporarily use a different database prefix and a different plugins directory while in the alternative heap (sandbox). This is done by sending WordPress a special _alt_heap cookie.16 The sandbox works similarly to how WordPress multisite works. We basically tell WordPress to temporarily use a different database prefix and a different plugins directory while in the sandbox, which means while you test the update, no changes are made to the live site. 17 17 18 18 ## Screenshots -
wp-safe-updates/trunk/readme.txt
r1708027 r1708032 5 5 Requires at least: 4.5 6 6 Tested up to: 4.6.1 7 Stable tag: 1.2. 17 Stable tag: 1.2.2 8 8 License: GPLv3 9 9 License URI: http://www.gnu.org/licenses/gpl-3.0.html … … 13 13 Test WordPress plugin updates safely before applying them on the live site. 14 14 15 This plugin adds a "test update" button when plugin updates are available. Clicking it triggers the creation of a sandbox where the user can safely test updating plugins without affecting the live site. Once the user is finished testing the plugin, they can go back to the live site and do updates if they like.15 This plugin adds a "test update" button when plugin updates are available. Clicking it will trigger the creation of a sandbox where you can safely test updating plugins without affecting the live site. Once finished testing the plugin, you can go back to the live site and do the real updates if all is well. 16 16 17 The sandbox works similarly to how WordPress multisite works. We tell WordPress to temporarily use a different database prefix and a different plugins directory while in the alternative heap (sandbox). This is done by sending WordPress a special _alt_heap cookie.17 The sandbox works similarly to how WordPress multisite works. We basically tell WordPress to temporarily use a different database prefix and a different plugins directory while in the sandbox, which means while you test the update, no changes are made to the live site. 18 18 19 19 **Disclaimer** -
wp-safe-updates/trunk/wp-safe-updates.php
r1708027 r1708032 4 4 * Plugin URI: https://github.com/anttiviljami/wp-safe-updates 5 5 * Description: Test WordPress plugin updates safely before applying them on the live site. 6 * Version: 1.2. 16 * Version: 1.2.2 7 7 * Author: @anttiviljami 8 8 * Author URI: https://github.com/anttiviljami … … 11 11 */ 12 12 13 /** Copyright 201 6Antti Kuosmanen13 /** Copyright 2017 Antti Kuosmanen 14 14 15 15 This program is free software; you can redistribute it and/or modify
Note: See TracChangeset
for help on using the changeset viewer.