-
Notifications
You must be signed in to change notification settings - Fork 51
Support WC 3.0 #96
Comments
Switching milestone to 1.2. Reason: Scheme data will be obtained via the Product API in 1.2, which will abstract a lot of direct |
See https://github.com/Prospress/woocommerce-subscribe-all-the-things/tree/issue-96 Leaving this open until we can test with a final WC 2.7-compatible version of WCS. |
On with this :) |
Quick update: If you depend on SATT, it is recommended to stick with WC 2.6 until a final SATT 2.0 release is available. Feel free to take the See progress in master...2.0 |
Note: Integrations with PB, CP and MnM do not work in |
Hi, |
Hi, I know you guys are super busy with the 2.0 update (huge thanks!), and I don't want to waste your time. I've been trying 2.0 out. Forgive the vagueness, but pre2.0 if I was subscribed to a Product Bundle, and the items bundled within that changed between renewals, then the next renewal would give me the updated contents of the Bundle. I am seeing in 2.0 that if I change the items in the Bundle, each renewal just keeps giving me the same contents as when i first signed up, even if those products have since been removed from the Bundle. May be a unique user case, and I know that PB's are not quite supported in 2.0 yet, but I thought it worth asking, otherwise I am headed in the wrong direction bigly. |
@sambomcd Can you please open a new issue about this? Thanks! |
Of course! Apologies - I just wasn't sure if this was an actual issue or if I am confused about how it is supposed to work. Normally it is the latter...
… On Jul 8, 2017, at 4:44 PM, Manos Psychogyiopoulos ***@***.***> wrote:
@sambomcd Can you please open a new issue about this? Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Opening this to start working on WC 2.7 compatibility.
Since SATT does not extend any core CRUD classes, WC 2.7 compatibility is limited to the following tasks (more added as we investigate):
The text was updated successfully, but these errors were encountered: