Tom

Unfortunately today it happened again (first time using Zettle again after reporting the issue).

Looking through the log file, the issue starts appearing after the first variable product was sold via the Zettle app. Any simple product sold before that did not result in any issue.In the log-file under Woocommerce status, the following line appears:

“Stock management at variation level is not supported from PayPal Zettle. ID:6075”

After that, more and more syncing errors pop up for any product sold or even edited in the Products list in Woocommerce.

The test I did earlier (with a specially created variable product) did not result in this error, so I really do not understand what is going on.

Replied to the last email I got on the support ticket, but not sure if that is still active.

Updated it here so other users with potential similar issues might respond as well.

Hope you or anyone else can come with a solution for us and solve this permanantly.

Kind regards,

Tom Vos

Hi Joost,

Thanks for your reply and adding this thread to the feature request, hope it would be possible to get it added as it may solve quite some syncing problems quite easy.

As for the reason why it is happening, I am totally in the blind. It seems to have occurred to random products (but I did not pay close enough attention to spot similarities and simply started fixing). Have not installed any new plugins lately, and as far as I can deduce, for sure none should be tampering with tax settings of individual products (but you never know).

Also not sure when it happened, I do not check the sync issues that often. It also did not happen on products on the first page, and there is also not an option to filter or sort on sync status (would also be a valuable addition to the plugin, but if not possible maybe some example code would be helpful so I can add that myself :-)).

That is the reason why I don’t think I can share any valuable log files now. However I will check the status more often and when it happens again try to mach it to the corresponding log.

Hope this thread can be kept open for some time, will get back to you when I have new info (or you when you get confirmation the plugin is getting updated :-).

Regards,

Tom Vos

Hi Mostafa,

Just installed the v5.0.3 update, but unfortunately still get an error (see details – in Dutch – below). If I am not mistaken it is similar to what is reported by another user above.

Hope you can look into it, thanks in advance.

Regards,
Tom

WordPress versie 6.2, Slimstat Analytics (versie 5.0.3), PHP versie 8.1.2-1ubuntu2.11

Foutmelding: Uncaught TypeError: implode(): Argument #1 ($pieces) must be of type array, string given in /var/www/<site>/wp-content/plugins/wp-slimstat/admin/view/wp-slimstat-reports.php:1250

Stack trace:

#0 /var/www/<site>/wp-content/plugins/wp-slimstat/admin/view/wp-slimstat-reports.php(1250): implode()

#1 /var/www/<site>/wp-content/plugins/wp-slimstat/admin/view/wp-slimstat-reports.php(956): wp_slimstat_reports::show_chart()

#2 /var/www/<site>/wp-admin/includes/template.php(1445): wp_slimstat_reports::callback_wrapper()

#3 /var/www/<site>/wp-admin/includes/dashboard.php(271): do_meta_boxes()

#4 /var/www/<site>/wp-admin/index.php(203): wp_dashboard()

#5 {main}

  thrown

• This reply was modified 1 year, 11 months ago by Tom.

Hi Edward,

What I understand from the below, that should be supported now:
https://docs.microsoft.com/en-us/graph/users-you-can-reach

Hi Edward,

Thanks for your quick response!

Yes, it is for a free Outlook account so that most probably is the rootcause of this issue?

I am deperately seeking for a solution for a free outlook account and was very happy I made it through the authorization part. But seems that is as far as it goes for now so need to seek for yet another solution.

Again thanks and regards,
Tom Vos

Just to make sure I used the correct tenant ID I have just entered a wrong tenant ID in the Mail Integration setup.

When saving this immediately reports an invalid tenant ID.
After correcting it with the one I copied from Azure it reports the app is configured to send email via Office 365.

When sending email however, the reported tenant ID error pops up.

Regards,
Tom Vos