corinnarake

Thank you for posting the solution @haywyre! I had the exact same issue with this plugin.

NOTE to the developer – please consider adding a simple checkbox/option to ADD or REPLACE the stock with the number entered.

I have made the above suggested change and it works perfectly, so it would only be a matter of adding a check for the option setting and either use $final_stock=$main_stock+$wssmgk_stock;
OR
$final_stock=$wssmgk_stock;

Nothing else needs to change. But now I’m worried that a future update will erase this change and I won’t remember to go back and fix it. So it would be great if this IS the future update. ??

Thanks for a great plugin otherwise – it does exactly what my client needs.

Thank you for your quick response, Alex!

For anyone else having this issue, I was using the incorrect fields. Instead of using the ‘attribute-key’ field under “Products”, I needed to use the attribute name key under “Product Order Items”.
Works exactly as expected now.

Thank you for your quick reply Alex. I have submitted a ticket as requested with screen shots and export file.

I am having this exact same issue. This thread doesn’t provide a resolution. Can someone help please?

Only thing I would add to the original post would be that I manually processed the refund in the WP dashboard before logging into PayPal to refund the customer. Could the order of this cause problems/be the reason for the duplicate email notifications?

I’m having this exact same issue with two of my client sites. Have rolled back the site to 3.3.5 woocommerce and it works. As soon as I update to 3.4.5 (or 3.4.4) the checkout process breaks.

I’ve disabled all plugins and switched the theme to twenty seventeen, still doesn’t work.

In the above scenario (no plugins & 2017 theme), it *sometimes* loads before the 1.5min timeout, and when it does, it appears to have been hung up on this: /?wc-ajax=update_order_review (although in most recent test, this page used only 15s of the 1.2min total time it took to load the page. The css files were all cached and therefore took 0s to load. The rest of the resources each took under 25ms to load).

Were there any changes to wc-ajax in the 3.4.? updates?