Hello there,
Good Day!!!
We would like you to troubleshoot the following things in your side.
1. Please check in your side cron job is active? It can be check under Admin Dashboard -> Instock Notifier -> Status which has all the information (please post that as screenshot here). That status page also has Test Email see if you receive any email(admin email) when you trigger that button.
2. Please try deactivate our plugin and activate again(sometimes background process not register properly)
Let us know.
Thanks.
Hi there, thanks for a swift response!
Status all looks fine, Cron is Active and Test email arrives. Also have reactivated plugin as you suggested. Will wait to see it that has sorted the process.
See screenshot here: http://prnt.sc/1w3n8q5
Thanks
Hi,
Today we had couple products returning in stock via a 3rd party plugin. Your plugin sent out messages for one of the products – presumably automatically, as we have more people working in the admin, we don’t know 100%. But not for the other product.
Is it possible to check if these messages that were sent out used automatic or manual sending method?
Thanks
Hello there,
Good Day !!
Yes we do record the log of both automatic and manual in our side. You can check it out by visiting the following page
Go to Admin Dashboard -> WooCommerce -> Status -> Logs -> Top right Dropdown(check for the prefix “back-in-stock-notifier” with latest date) If the latest log contain
Product id #{id} Instock Background Process started – Total: {total} something like this will be treat as automatic, if other than automatic we will record the log with key term “Manually Sent”
Please make sure this background process event registered properly in your side
Go to Admin Dashboard -> WooCommerce -> Status -> Scheduled Actions -> Pending -> Seach for hook -> cwg_schedule_third_party_support (screenshot attached)
If it is present this event will take care of stock status check automatically(every 5 minutes)
https://drive.google.com/file/d/1sfNnCZhAcklsTPYmUOkjJBFJF9_IGh14/view?usp=sharing
Let us know
Thanks.
Thanks for directions.
I found that latest emails were triggered by background process – so automatically. But only for one of the products that returned in stock, and not for the other one.
Other one had email sent out today manually by admin- which I see in logs as per your description.
In pending scheduled actions I see 2 of the cwg_schedule_third_party_support hooks registered.
Any ideas where is the inconsistency coming form?
Thanks.
Hello there,
Please remove duplicate of scheduled actions cwg_schedule_third_party_support
Previously we asked you to reactivate our plugin right? Due to this that duplicate entry arise(it will not create any issues with plugin functionality).
From next version we will validate the code to avoid duplication.
Let us know.
Thanks.
Hi there.
Unfortunately on top of the issue of plugin having inconsistency with back in stock message sending, last week we had a occasion when a many messages were sent out to subscribers even though products did not return in stock. Also logs do not contain any messages sent about back in stock products. Only couple new subscribers.
Do you have a list of incompatible plugins that we could check if we use any of them? Would be great to solve this issue once and for all.
Thanks.
I had the same and debugged until I found it:
In the method retrive_product_ids() the query has a bug ->
$select_Query = $wpdb->get_col($wpdb->prepare(“SELECT meta_value from $wpdb->postmeta where post_id IN(%s) and meta_key =’cwginstock_pid'”, $post_ids));
Change it to:
$select_Query = $wpdb->get_col($wpdb->prepare(“SELECT meta_value from $wpdb->postmeta where post_id IN(1%s) and meta_key =’cwginstock_pid'”, $post_ids));
So %s to 1%s. Because the current query will read post_id IN(‘123,145’) and thus will only look at 123 in the meta table, so only 1 product will be tracked. If you change to 1%s, it will be post_id IN(123,145), so without the quotes and will then result in all needed meta values.
Hi @omnisite
We checked your query in our side and unfortunately we couldn’t reproduce any issue in our side, it works normal in our side. Also we couldn’t find any documentation relevant to your suggested code 1%s
Further checked we found something like %1$s in wordpress documentation but from WordPress 4.8.2 specifically restricts the convenient usage of numbered placeholders like %1$s, %1$d, %1%f in WPDB::prepare
https://core.trac.wordpress.org/ticket/41925
Let us know.
Thanks.
Hi @kasparsmime ,
Good Day !!
We don’t have any list of incompatible plugins on our side. We strongly suggest you to check our plugin in your staging/testing site by deactivate all other plugins except WooCommerce and our Back In Stock Notifier Plugin, if it works properly then check the conflict plugin(s) by reactivate other plugins one by one and let us know.
Thanks.
Sorry, typo: %1s is what I meant. You can just try the query in mysql itself. If you do post_id IN(‘123,145’) it will give you 1 result. Without the quotes like post_id IN(123,145) will give you multiple results.
Also, if I read correctly on your WP link, the numbered placeholders were re-introduced: https://core.trac.wordpress.org/changeset/42068
Hi
@omnisite thanks for your involvement and advice.
@codewoogeeksupport I did tests on staging environment without uninstalling plugins first. My finding are that all messages were sent when receiving stocks via the third party plugin. But only one product ID is processed at a time, meaning, if there are more than one product returning in stock, the second one is processed in the consecutive cron job running (after 5min).
Issues I had on the production environment I still need to observe as and when stocks come in.
@codewoogeeksupport
I have a concern though about the fact that system sent out messages to subscribers without stock change and registering the sending actions in log files. Any idea how this could happen? We want to avoid that in the future as it confuses the end user and we get questions asked from them.
Thanks
Hello @omnisite @kasparsmime ,
Thanks for the detailed information regarding your reported issue and we able to reproduce that problem. We’ve fixed your reported problem in our side and it will be available in next update (v2.4.2).
For your information we planned to update our plugin in WordPress tomorrow(10th November 2021). We will let you know once we updated our plugin in WordPress.
Once again appreciated your detailed information regarding this issue.
Thanks.
