Antidot developer

Released!

I will release the 2.3.9 nearly ?? .

I guess WordPress will suggest to update from 2.3.8.2 to 2.3.9.
If it doesn’t Monday, back to 2.3.8 and the 2.3.9 will come with WordPress updates

Hi,

I tried a new version: https://we.tl/t-WjejqoIGic

Thanks for your feedback about this archive.

Regards,

Hi,

You have the issue for all orders, or only some ones?

I continue to search and try to reproduce that on my webshop.

By waiting my fix, continue on the version 2.3.7 of the plugin.
I try to fix that as soon as possible.

Regards,

But i see MANY files of bpost generated inside our wordpress library whereas i’ve setup the “Labels stored as simple files: root folder path” here : /wp-content/uploads/bpost-labels

Yes, it’s normal. If unchecked, the label are stored as WP attachments.

Can you try the plugin version (v2.3.8.1) : https://we.tl/t-ntE0TEI0dn

If you need to send me non-public feedback, send me a mail to [email protected].

Thanks for your feedback!

Hi,

Oops, sorry for the issue :-/ .

We are testing a fix is working and let you know.

Just to know, in the bpost-shipping settings, the checkbox “Store bpost labels as simple files” is checked or not?

Regards,

Bonjour,

Merci pour votre retour.

Bien à vous,

Hello,

The new release 2.3.3 fixes the issue.
Can you update, check, and confirm me that’s solved?

Thanks all for your feedbacks

Hello,

The new release 2.3.3 fixes the issue.
Can you update, check, and confirm me that’s solved?

Thanks for your feedback

Hello,

The new release 2.3.3 fixes the issue.
Can you update, check, and confirm me that’s solved?

Thanks all for your feedbacks

Hi,

In the log, I don’t see exchanges between WordPress and bpost API about labels (only requests about bpost shipping manager settings).

Can you check the log file “fatal-errors-*.log”, and send lines about bpost ?

Thanks,

Bonjour,

Quelle est votre version de PHP ? Inférieure à 7.0 ?

Hi,

Can you send us the logs of exchange with API during the printing of a label?

You posted the log of the exchange with API during the opening of the setting (where WC asks to API the bpost settings of the user).

Try by disabling, then re-enabling, the debug option in bpost settings, and post the result. Be careful to remove authentication (Authorization: Basic ***) before posting logs ?? .

Regards

Hi,

I am just releasing the fix (v2.3.2).

Can you update the plugin in few minutes and tell me if that fixes the issue?

Can you get the error message by enabling the WP_DEBUG setting please?

Thanks,