jamiechong

Mark,

I haven’t done extensive testing with Woocommerce products. I don’t foresee any issues, but you should set up a few test products and try it out first for your own peace of mind. It’d be great for the community if you could report back with any issues you find, or confirm that all’s well.

Jamie.

Hey Dale,

Yep that’s it.

Click Revisionize
Make your changes
Set the date to the future.
Click “Schedule”

When the revisionized post publishes, it will know to update your original post.

@shyzer

This is working as intended. Although perhaps the setting and its description are a little misleading.

Without revisionize, if a user edits a post and updates it, the original publish date is left unchanged.

So the default revisionize behaviour is the same. Creating a revision produces a new post with the same publish date as its original. When you publish the Revision, the date stays the same.

*However – there are cases where users want to use the schedule functionality to publish their revision in the future. To do this, they must edit the post date to the future. When the date comes to pass, WP publishes the revision on top of the original post. If the setting your refer to is checked, then we keep the original date, otherwise we fallback to the date of the Revision/copy which is the present date.

So in short, this checkbox/setting is really only for the case of scheduled revisions and not for normal manual revisions. You or your contributors will have to manually change the date when you publish.

Hey @msudano – I’ve never used the Elementor plugin. There’s a good chance that Revisionize just won’t work with this as I imagine the way this plugin handles page building is substantially different from how WordPress manages content of its posts.

Do you have any more details on the 500 error? Check your error logs for specific error messages?

@clemorphy I haven’t looked into preparing it yet – there’s been no real demand until now, but I’ll take a look.

You can add a filter in your functions.php file. Something like this might work (untested)

add_filter('revisionize_user_can_revisionize', function($can) {
  return !current_user_can('update_core') && $can;
});

@aretzer

Check version 2.3.0 – I’ve added a new setting, which should help.

Using those 2 filters should work to solve your problem. But the way you’ve written them, _only_ users with edit_farms caps will be able to revisionize. You’re not including the default value. You may want to consider something like this, but of course every situation is different.

add_filter('revisionize_user_can_revisionize', function($userCan) {
	return $userCan || current_user_can('edit_farms');
});

add_filter('revisionize_user_can_publish_revision', function($userCan) {
	return $userCan || current_user_can('publish_farms');
});

You can always look at the source to see where these filters are being used:
https://github.com/jamiechong/revisionize/blob/master/revisionize.php#L423-L429

'capability_type' => 'post' is the default, so you don’t even need to explicitly define that.

I think you only need to add those filters if your user doesn’t have the *_post capabilities. Is that the case?

Does your custom post type definition have any settings for
capability_type or capabilities ?

What role is your non-admin user? Is it one of the stock WP roles or have you created a new one? If it’s a new one, which capabilities have you given it?

What other plugins do you have installed? It seems like somethings is interfering when the WordPress scheduler publishes your future post.

Can you try to disable other plugins that might be a problem and redo your test?

Yes, I agree that some documentation and improvements to the UI/X would benefit you guys. It’s on the list, but low priority right now!

I can’t reproduce.

Note that the Revision that you create will become your own, but when you publish it back, it will maintain the original author.

@adminseekout

Probably not because this sort of functionality doesn’t already exist in stock WordPress. WordPress already has the ability for contributors to submit New posts for review and there isn’t a way for an admin to decline/notify the contributor.

This revisionize plugin just adds the ability for contributors to submit changes to existing posts for review.

Hi @ceubri,

I just tested out the schedule a revision functionality and all seems well to me.

Can you give me more information? What version of WordPress are you using? Version of Revisionize? Can you give me step by step instructions on how to reproduce the problem? Be as detailed as possible.

For example, I’m able to schedule a page revision by doing the following:

1. Open the page I want to schedule.
2. Click the Revisionize button (on the right column)
3. Make changes to my page
4. Edit the “Publish On” date, which is in the right hand column. Set the date to some time in the future.
5. Make sure the blue “Publish” button now says “Schedule”
6. Click “Schedule”

Once the future date comes to pass, the scheduled page gets published.