Inline version numbering for WordPress

變更記錄

2.6.3

• Confirmation of compatibility with WordPress 4.7.
• No functional changes.

2.6.2

• Confirms compatibility with WordPress 4.6.
• Remove unused function which appeared outside the class structure.
• Corrects README and plugin comment.

2.6.1

• Confirm functionality in WordPress 4.5.

2.6.0

• Don’t change file paths if they already contain a version number.

2.5.1

• Confirm functionality in WordPress 4.4.2.

2.5

• Remove htaccess rule when deactivating plugin.
• Confirm functionality in WordPress 4.4.

2.4

• Ensure that .htaccess rules are maintained cleanly when accessing Permalink section in wp-admin.
• Thanks to http://wordpress.stackexchange.com/users/1685/thedeadmedic for the assistance.

2.3

• Extend regex pattern in .htaccess to recognize version numbers containing dots and dashes.

2.2

• Use the admin-init hook to update the .htaccess file whenever the version number changes. (e.g. when updating the plugin from the repository.) This is in addition to the modification which takes place when the plugin is activated.
• Minor corrections to README.

2.1.1

• Temporarily remove .htaccess update on plugin update, due to a bug.

2.1

• Update .htaccess when the plugin is updated from the plugin repository.
• Correct version number across all files in the plugin.

2.0

• Use better code solution by Dominik Schilling. (https://dominikschilling.de/880/) No copyright breach intended: just making this plugin code available through the WordPress Plugin Directory.

1.2

• Only modify resource src if it contains ?ver=
• Tweak PHP code spacing
• Modify plugin URI and key to reflect adoption in WordPress plugin repository.

1.1

• Update code to use add_rewrite_rule function.

1.0

• Initial version