1 vote Vote There is a conflict between the WooCommerce Dynamic Pricing plugin and the Attribute Swatches plugin. Support said it was related to the Fees portion of the Attributes Swatches plugin and suggested this feature request. Declined Category: Attribute Swatches scmsteve shared this idea This should hopefully be completed by the end of April 🙂 Reply There was an issue we encountered last year that put a blocker on this, and the issue has of course been overlooked by other projects we’ve had ongoing. I’ll be revisiting this in the coming months, but rather than treating this as a feature request, this is classed as a bug internally moving forward. Reply ← All Requests Don't have an account? Register Already have an account? Login Username Email / Username Password Repeat Password Login Register Top Requests Dokan multivendor support for pickup and delivery slots 25 Votes Select delivery date and time slot visibility by product category 20 Votes Different angles 17 Votes Integration with WooCommerce Subscriptions 16 Votes Let the customer input their own text 13 Votes Categories Account Pages Attribute Swatches Bundled Products Custom Fields for Variations Delivery Slots Flux Checkout General Image Swap Linked Variations Product Configurator QuickTray Quickview Sales Booster Show Single Variations Wishlists WooThumbs
1 vote Vote There is a conflict between the WooCommerce Dynamic Pricing plugin and the Attribute Swatches plugin. Support said it was related to the Fees portion of the Attributes Swatches plugin and suggested this feature request. Declined Category: Attribute Swatches scmsteve shared this idea This should hopefully be completed by the end of April 🙂 Reply There was an issue we encountered last year that put a blocker on this, and the issue has of course been overlooked by other projects we’ve had ongoing. I’ll be revisiting this in the coming months, but rather than treating this as a feature request, this is classed as a bug internally moving forward. Reply
There was an issue we encountered last year that put a blocker on this, and the issue has of course been overlooked by other projects we’ve had ongoing. I’ll be revisiting this in the coming months, but rather than treating this as a feature request, this is classed as a bug internally moving forward. Reply