Add revision support to product post type

[gw0]

Because product post types could be edited often and by different people it would be great to have revision support for them so that you can revert to a previous version, check differences... This functionality would also be useful in case someone mistakenly published something or has some kind of difficulties entering data.

(I am trying to debug some issues where the wp-admin page automatically reloads while someone is in the middle of the editing/inserting process for attributes and having previous versions available would make things simple.)

As I see some code for this is already present, but the product post type is not registered with support for this (woocommerce.php:993). Was it intentionally disabled, are there some issues?

[mikejolley]

It is intentionally disabled because revisions support post content only afaik. This is pointless for products because the import part is the writepanel + meta. Therefore we cannot add this feature at this point in time. Right @coenjacobs?

[coenjacobs]

I agree with @mikejolley here. We can add revisions, but it would only cover the main text (editor) of a product and that is not the most valuable data. WordPress 3.6 is currently scoping features and it is likely that they will cover the revisions saving for meta data. I'll be on top of that and once there is pretty support possible, we will support that.

[kirkearl]

Any updates on this topic? I'm interested in the same functionality.

[coenjacobs]

@kirkearl I've added this on our Roadmap for considering in future releases. WordPress core still hasn't improved much, which is what we're waiting for.

[gabiudrescu]

I'm trying to use WP with Woo Commerce and WP All Import, but I'm afraid sometimes, due to a broken import, stuff might go wrong and I can lose all my work. Therefor, 5 steps revisions going back would help me sleep better. I have activated revisions for products by editing the core of Woo Commerce, but I soon realized this saves the data only for some of the fields, not for all.

Googleing more about this, I found out about this topic: http://support.advancedcustomfields.com/forums/topic/wordpress-3-6-revisions-custom-fields-no-longer-tracked/

Maybe you could try to implement the same for Woo? I'm really sure that in multi user configuration, this would be very helpful in tracking down editor's activity. Also, by having this revision info saved into DB, you could easily pull a price evolution graph for certain products, a very nice to have feature for affiliate marketing websites powered by WP + Woo stack.

[bsgreenb]

Would really appreciate this feature, especially since you can completely lose original content if you mistakenly sync over it with Woozone or a mistaken editor

[bsgreenb]

@coenjacobs any chance to introduce this, if only just for product descriptions (short and long)?

[coenjacobs]

First of all, I'm no longer maintaining this plugin, so this needs to be considered by the current WooCommerce team. Here's my $.02 though:

If post meta ever made it into revisions (I honestly don't know, I lost track) in WordPress, there is a lot of added value for this to be added to WooCommerce. Not just for products, but also for orders and other post types that might be introduced at some point. It will add value because of the paper trail it creates, you can always review who created/changed what and when. This will be a bigger change though, so this needs to be implemented on a slightly larger scale than just adding revisions to the supports array.

[aibrean]

People use WooCommerce for more than just ecommerce. I think the people who need this are using it because they know how to build sites and aren't just pressing "install". I have used it for two site builds where in one case we only used Woo for the logic and the other as a way to show reviews (and they were all external products). In both cases, the Woo product box was not utilized outside of the external product link in the latter event. They were both heavily doped up on custom fields, to which revision control is a necessity.

[aibrean]

Since WooCommerce is now owned by the owners of WordPress...couldn't this be something to revisit?

[claudiosanches]

@aibrean WooCommerce is not owned by WordPress. WooCommerce is owned by WooThemes that is owned by Automattic.

[aibrean]

Tehnicality... @claudiosmweb ...my point is they have the capabilities to push for revisions since they are owned by the same group now. No reason for it not to be in core.

[claudiosanches]

@aibrean it's not the same group.

[douglaz]

This is really an important missing feature.

[douglaz]

Asked for a workaround here: http://wordpress.stackexchange.com/questions/238905/adding-revision-support-to-woocommerce-product-content

[claudiosanches]

@douglaz I don't see this happening, since WordPress don't covers revisions for custom fields and we have some plans to create new tables for this meta data for performance, so I don't see this happening too fast. Anyway feel free to submit a Pull Request if you are able do to it.