Running WC 8.0.2 and v1.27 of this plugin, we seem unable to activate High-Performance Order Storage while this plugin is active because it hasn’t declared compatibility with HPOS.
Is there an ETA for HPOS support?
Starting with WC 8.2 which is due to be released around October 2023, HPOS will be the default experience for new stores. HPOS was originally planned for 8.0 which was released in August 23 and everyone was given ample of notice to prepare for it.
]]>Hi,
We really need to thank you for this great plugin of how its really useful and beneficial for people like us.
We have a single suggestion to modify in the core files of the plugin. we inspected it and found that this plugin its function work only if the user has cap (manage_woocommerce), which is in our opinion a general cap for the woocommerce because there are specific caps for coupons itself like (publish_shop_coupons).
So its better to make a this function to work with the users who has a specific funtion related to coupons which is (publish_shop_coupons) because if any user can publish coupons for sure will have an access to duplicate it.
This will result in what by changing the cap to (publish_shop_coupons) ?
This will result in making this plugin compatible to work with popular multi vendor plugins which will give the access to other roles like (vendors) with the cap of(publish_shop_coupons) to use the functionality of the plugin.
Will be compatible with ( Yith Multi Vendor, Product Vendor, etc.. )
What do you think of this suggestion ?
Stay Safe & Best Regards
]]>Hi,
thanks for the plugin!
Just one thing: It doesn’t make sense for us to copy the field “_used_by” to the new coupon. I have removed this behaviour by adding the following code in line 195:
// Don’t copy the “_used_by” field
if ( ‘_used_by’ === $meta_key ) {
continue;
}
Would be cool if you can change this in the official plugin to help others ??
Thanks!
]]>Hi,
Thanks for this useful plugin. It seems to work fine for our needs, however we noticed that the usage count is copied to the new coupon.
This shouldn’t be the case, as the new coupon hasn’t really been used and that could cause issues with the coupon usage restrictions.
I updated your plugin by changing line 179 to
if ($post_meta_row->meta_key == "usage_count") {
$sql_query_sel[] = $wpdb->prepare( "SELECT %d, %s, %s", $new_id, $post_meta_row->meta_key, 0 );
} else {
$sql_query_sel[] = $wpdb->prepare( "SELECT %d, %s, %s", $new_id, $post_meta_row->meta_key, $post_meta_row->meta_value );
}
But there might be a better solution to this.
]]>