Salva Machi
Forum Replies Created
-
Hi @jacque86
Please update to latest ATUM version. It should work there.
ok, if you receive it again, let us know.
But those files the error mentions are deprecated and were removed from latest version. So it shouldn’t happenHi @gerske
Your issue is the same as this one:
https://forum.stockmanagementlabs.com/d/5405-wordpress-caught-an-error-atum-inventory-management
Can you please try what I suggested there?Best Regads,
Salva.You can read the changelogs here:
https://stockmanagementlabs.com/the-changelog/But, specifically to your issue: compatibility with the WooCommerce’s product object cache was added and I guess it is what was causing those errors you mentioned.
Hi @ankitgoyal130
We have just released ATUM v2.0.2 that should fix that issue.
Please try to update and let us know.Best Regards,
Salva.@michaelkuen Make sure you have the WooCommece’s “Cache Product Objects” option disabled from WooCommerce >> Settings >> Advanced >> Features
That is still experimental and it is causing this kind of issuesBut how are you going to create that subscription box?
Are you going to use additional extensions as described in their docs?https://woocommerce.com/document/all-products-for-woocommerce-subscriptions/use-case-offering-subscription-boxes/
Or what you want is to have a unique product (the box) and adjust the stock of all the included vegetables when the subscription is sold?Hi @davidwjw
I don’t understand what you meant with “We need another plug-in that will break down the stock we need each week”. Can you elaborate on that, please?
And, FYI, ATUM is compatible with WooCommerce Subscriptions and WooCommerce Bundles but not with the Yith versions at this time.
Best Regards,
Salva.Hi @gentlemako
Have you enabled all the capabilities that start by the “atum” prefix for the shop manager role?
Hi @gentlemako
If you are using object caching, that could be causing this issue.
Try to go to ATUM Settings >> Advanced, enable the option “Disable ATUM orders’ object caching”, save the settings and check if everything works as expected that way.
I hope this helpsBest Regards,
Salva.All the features within that section are “experimental”. So they can change before they are moved to “stable” or it can be discarded completely (I’ve seen this happening in the past).
So adding compatibility to ATUM at this stage can be a waste of time. I hope you understand this.If this feature is finally marked as stable, we will look in to it, for sure.
Best Regards,
Salva.Hi @atombomb
We are not aware of any conflict with the Stripe plugin. And I’m sure many of our users are using it…
But, what you describe seems related to an issue with some sites using object caching (mainly WP Engine hosted sites).
If that is your case, try to go to ATUM Settings >> Advanced, enable the “Disable ATUM orders’ object caching” option and save.And let us know if that worked.
Best Regards,
Salva.A caching bug or some kind of specific configuration on the caching system. I don’t know what could be the cause…
Thanks for checking this 😉
Until now, we only had these kinds of issues on WP Engine’s object cache.
I am not aware of any other user having this issue. And many of our users use object caching on their sites, for sure.So, we don’t know why some object cache systems are causing issues here because this is external to PHP code.
FYI, we are using official functions to set the cache:
https://developer.wordpress.org/reference/functions/wp_cache_set/
And
https://developer.wordpress.org/reference/functions/set_transient/
If you know what could cause this issue or if it is possible to fix it from our side somehow, we are open to hear your proposal.
We have scoped it to this method: \Atum\Inc\Helpers::get_atum_order_model()Hi @ecommpower
There is no need to publish the same here and on our official forums.
We have already read your post on our forums, and we will give you an answer there soon.Best Regards,
Salva.