Plugin / Revisionize
Jamie ChongChangelog
Changelog
2.3.2
- Fix. Work toward being translatable.
2.3.1
- Fix. Add missing i18n domain.
- Improvement. Add Known Issues to readme.
2.3.0
- New. Setting to preserve original author or overwrite it with author who is revisionizing.
2.2.8
- Fix. Show settings on default multisite page.
- Fix. Prevent non super admins from uploading addons on multisite.
2.2.7
- Fix. Undefined index errors.
2.2.6
- Fix. Handle edge case where malformed addon data comes back from revisionize.pro
2.2.5
- Fix. Use correct path to addons directory for Multisite.
2.2.4
- New. Action for developers. revisionize_after_copy_post
- Fix. Ensure author ID is set when a backup revision is created during cron.
2.2.3
- Fix. Move addons directory to a location safe from overwrites.
2.2.2
- New. Action for developers to add hook after a revision is created.
- Fix. Fatal error when checking is_wp_revision_different.
2.2.1
- Fix. Notices when admin bar shown on non-edit pages. Thanks @kshaner.
2.2.0
- Fix. Use settings when cron publishes a scheduled post.
- Feature. Revisionize link added to admin bar.
2.1.4
- Fix. Properly fetch addons list.
2.1.3
- Fix issue where addons list is empty causing Warnings to be displayed.
2.1.2
- Fix issue where addons weren’t loaded if the revisionize_addons_root was used. Thanks @piscis
2.1.1
- Make revisionize and its addon framework work better with WordPress Network/Multisite installations.
- Add filter to change the addon install directory.
- Check for addon updates.
2.0.2
- Generalize user_can_revisionize so that it’s true if a user can edit pages.
2.0.1
- Fix Fatal error on 2.0.0 – had forgot to commit settings.php and addon.php. Please update and activate again.
2.0.0
- Add a basic settings panel.
- Add ability to install addons
1.3.6
- Fix critical bug for non ACF users.
1.3.5
- Add filter to give developers control over updating post dates. See here. Thanks @piscis
- Fix bug with gmt date.
1.3.4
- Fix edge case bug where ACF change was not tracked in WP Revision Tracker.
1.3.3
- Track ACF changes in the built-in WP Revision Tracker when a Revisionized post is published.
- Add filter (
revisionize_exclude_post_types) to exclude Revisionize functionality for specific post types. By default ACF custom field types are disabled.
1.3.2
- Maintain original post dates when a revision is published
- Add filter (
revisionize_keep_original_on_publish) to override behaviour of keeping the original as a revision when publishing. - Hide experimental dashboard widget that was added in 1.3.0. See here if you want to show this widget again.
1.3.1
- Fix issue where publishing a revision did not overwrite the original post when ACF 5 was installed but no fields were assigned to the post type.
1.3.0
- Add filters to let developers control which users can revisionize or access revisionized posts. See here for more details on how to use. Thanks @ryanshoover.
- Add a dashboard widget showing pending revisions. See here for more details. Thanks again @ryanshoover.
1.2.2
- New add filter to allow developers to customize button text. Thanks @robbiepaul.
1.2.1
- Fix issue where post titles containing ampersands are escaped when a revision is scheduled with cron. Thanks @piscis.
1.2.0
- Fix known issue where direct publishing of a Revision that has ACF would not actually update the fields. Thanks for the help @thegaffney
1.1.0
- Only allow users to Revisionize posts that they can also edit. Related discussion
- The author of the original post is maintained when a Revision is published – it doesn’t get set to the author of the user who created the Revision.
Ratings
Rating breakdown
Details Information
DIRECTORY DISCLAIMER
The information provided in this THEME/PLUGIN DIRECTORY is made available for information purposes only, and intended to serve as a resource to enable visitors to select a relevant theme or plugin. wpSocket gives no warranty of any kind, express or implied with regard to the information, including without limitation any warranty that the particular theme or plugin that you select is qualified on your situation.
The information in the individual theme or plugin displayed in the Directory is provided by the owners and contributors themselves. wpSocket gives no warranty as to the accuracy of the information and will not be liable to you for any loss or damage suffered by you as a consequence of your reliance on the information.
Links to respective sites are offered to assist in accessing additional information. The links may be outdated or broken. Connect to outside sites at your own risk. The Theme/Plugin Directory does not endorse the content or accuracy of any listing or external website.
While information is made available, no guarantee is given that the details provided are correct, complete or up-to-date.
wpSocket is not related to the theme or plugin, and also not responsible and expressly disclaims all liability for, damages of any kind, arising out of the use, reference to, or reliance on, any information or business listed throughout our site.