Ram Shengale

Hello,

We use the standard Woocommerce order status system for triggering notifications. So if the ShipRocket plugin uses the standard Woocommerce order status for updating shipping status, then our plugin will work perfectly with it without any issues. You can setup Trigger for shipping.

But if the plugin manages it’s own custom order status management, then you’ll not be able to use our plugin. For those cases, it’ll be better to use our Notification API to trigger notifications.

Regards,
Ram Shengale,
WANotifier Team

Hello,

Currently one line per item is not possible because variable in message templates do not support line breaks. Once WhatsApp API start supporting it, we’ll add the feature.

Regards,
Ram Shengale,
WANotifier Team

On digging deeper, I think the query in does_file_exist_local() can be run on this table instead: wp_as3cf_items. That’ll fix the slow query issue for uploads.

SELECT COUNT ( * ) FROM wp_as3cf_items WHERE path = ?

Also regarding offload_duplicate_items(), here the issue can be resolved by removing m.meta_value = %s part from the query and then checking the path in PHP from the query results.

Is it possible to incorporate these changes in the plugin?

Yeah, tthat’s fine. This was anyways a one-time thing.

Thanks for your help. We can close this ticket now.

I was able to achieve my goal by replacing your $args with this:

$args = array(
'return' => 'ids',
'type' => 'shop_order',
'limit' => -1,
'order' => 'ASC',
'orderby' => 'meta_value',
'meta_key' => '_wcpdf_invoice_date',
'paginate' => true,
'posts_per_page' => 250,
'page' => $page_count,
'date_paid' => $from_date . '…' . $to_date,
);

All good now.

It needs to use the _wcpdf_invoice_date or _wcpdf_invoice_date_formatted meta for sorting. That’s because the order can be created first but the payment may get processed after sometime (due to late payment or other reasons) and new orders can get created in-between.

_wcpdf_invoice_date or _wcpdf_invoice_date_formatted will give us true sequence of invoice numbers.

• This reply was modified 1 year, 1 month ago by Ram Shengale.
• This reply was modified 1 year, 1 month ago by Ram Shengale.

Thanks for this. I tested the plugin. The renumbering is happening but not as per invoice date. It’s following some other ordering.

When are you going to publish the update? I was not able to download earlier. Can you share the latest file again? Or it’ll be better if you directly push the new update.

Thanks

Hello Radhika,

Once you remove your number from WhatsApp Manager, your number gets free to use with the mobile app. Please make sure the number is actually removed from the WhatsApp Manager and then try adding it on your mobile app.

Regards,
Ram Shengale,
WANotifier Team

Hello Radhika,

I myself replied to your chat and have not received a reply from you so far. Regarding Transactional Notification, please read Step 6 in this article.

Thank you.

I do not see any transactional Notification in your screenshot. Also I checked your account backend from my end and see that you’ve not created it. Transactional notifications have status as On-going.

I would again request you to please go through the article I shared earlier to set that up. Or start a chat with us on our website if you’re not able to do the setup.

That is a Trigger. I asked for the Notification you setup of WANotifier. I think you’ve not done that step. I would highly recommend going through the article I shared earlier to set that up.

Can you share screenshot of the Notification you setup for WooCommerce integration?

Hello Radhika,

Sorry to know that you’re facing this issue. Can you confirm if you’ve setup a new Trigger on your website, create Message Template on our portal and then created a transactional Notification to do this integration?

I would suggest you checkout this article where we’ve covered step-by-step details on how to do the full setup.

Please check that out and let me know if you’re still facing issues.

Regards,
Ram Shengale,
WANotifier Team

There was some bug in our code which was causing this issue. We’ve fixed that now and everything seems to be working well.

Sorry for the trouble and thank you for your support.