There could be something we need to adjust to make it compatible with the variations plugin you’re using, or it also sounds like it could be a theme issue.
Can you try switching to one of the basic “Twenty” themes temporarily just to eliminate that possibility?
One question before I do so. If I switch themes won’t I lose all my plugin settings. I believe I switched before and it messed everything up. I have just got my site back to stable from I don’t know where. It was all messed up.
In most cases simply switching themes should not cause you to lose any settings. When you switch back everything should be exactly as it is.
Depending on exactly which theme and/or plugins you’re using, though, I cannot guarantee this 100%. That said, if doing so causes you to lose anything, I would recommend you ditch those themes/plugins. That shouldn’t happen, and if it does, they must not be very well built.
That said, if you were to switch your theme, and then adjust a bunch of post meta data or settings in that new theme, then when you switch back things could be screwy until you adjust it all back to fit that original theme.
In this case, though, I’m just asking you to switch the theme, don’t do anything with settings (other than re-enabling our payment gateway so you can try it). Then give it a quick test and switch it right back.
Of course, backing up your site files and database would always allow you to quickly restore the current state of the site if something were to go wrong, so that is always recommended.
I switched to 2015 theme and it still acts the exact same and I switched back and all was the same thank God. Here is a link to the test item I am using if you are able to see it. We are currently running out of memory on our server and have to upgrade so sometimes our database goes down. http://surpius.com/index.php/product/ussp-hoover-vacuum-uh30010-uh30010com-handle-assembly-replacement-part-002069001/
From what I’m seeing you’re getting the expected result.
Our plugin uses the woocommerce_after_add_to_cart_button hook to place the offer button after the add to cart button.
It looks like the plugin you’re using is outputting an add to cart button for each variation. As such, it’s outputting an offer button after each add to cart button, which again, would be expected.
What exactly is the Variations to Table plugin doing for you? If you disable that are you still getting multiple add to cart buttons? I don’t remember ever seeing multiple add to cart buttons with variable products in WooCommerce by default.
The plugin allows for there to be a add to cart button for each item condition (variation) instead of a drop down menu. Customers were confused with the drop down menu so we use the plugin to make a table for the multiple conditions. That part in your offer plugin is fine and looks great(or maybe just a single make offer button at the bottom would look better) but when you click the make offer button is when it gives the error to pick a variation first. I don’t know how to add a screen shot here or I would show you.
Ah, ok, I see what you’re saying now.
So you’re fine with the multiple offer buttons. It’s just that it’s still expecting a variation to be selected so it’s returning the validation error.
This would take some customization to work with that plugin. We can do this for you, but we’d have to treat it as a premium support case.
You’d probably be looking at a 5 hour project.
No thanks on the premium support. I can just use a make offer button on the page that connects back to our contact form page. I just wanted to let you guys know so you could maybe correct the issue or add it to future updates. Thanks.
Sure, we’ll add it to our GitHub repo to be fixed in a future version. Thanks for the feedback!
This issue has been resolved in our GitHub release branch and will be included in the 1.4.4 update coming soon!
I would like to make a suggestion. I use the pop up for the make offer. Could you please make it where they can choose the variation in the pop up after clicking the make offer button. Thanks
Okay, I’ve added this to our 1.4.5 list. 🙂
