sylvain68

Bonsoir @iscpcolissimo,

Super, merci pour votre retour.

S’agissant d’une amélioration, je ferme cette demande de support.

Bien cordialement,

Sylvain

Thank you for your quick feedback @izzih!

It’s perfect if your teams are already working on solving this issue.

I will check if the next update includes the fix.

Thanks again.

Hello @mtamy,

The only current workaround, without downgrading to a lower version of your Dymo software (which is the official recommendation of Dymo…), is to uninstall this update again.

With Windows CLI if needed: wusa /uninstall /kb:5000802

Although not recommended, you can also “pause updates for 7 more days”.

FYI Microsoft is working on a fix. Given the number of users affected, I don’t doubt their reactivity ??!

A lot of information about this problem can now be found on the web. Depending on the version of W10 installed, other KB updates may be concerned.

Good luck to all!

Thank you all for your feedback, glad it helped ??!

Sylvain

Just perfect, thanks again @zorem.

I confirm that it’s all good on my side.

Don’t take some of my words wrong @zorem. OK, it is possible that the verb I used is not the right one (English is not my mother tongue but I do my best).

Don’t worry (be happy??), I just tried to explain to you that you probably marked this subject as resolved too quickly, and that I could understand it as you certainly have a lot of work to do…

Of course, I’m totally aware that this is a free plugin with free support and I thank you again here. That’s why I try to help you when I see possible bugs or suggest improvements when it can be interesting for you and the other users. Know that I have nothing against pro plugins, not all features can always be free, it is sometimes the only way to ensure a good development and support for the plugin.

And finally, if you haven’t noticed it, I encourage as many WooCommerce users as possible to install your quality plugin ??!

Thank you in advance.

Hi @zorem,

Thank you very much for your answer but I think you read my message a bit quickly.

The problem is not solved and, to be honest, I don’t really like the way you sweep my request. Let’s say you have a lot of work to do… so I won’t hold it against you. I’ve always been very satisfied by your high quality plugin and support (which earned you a 5 star rating when your plugin was not yet very well known). But when a possible bug is reported to you, with detailed explanations, you could at least take the time to check.

the Partially shipped and Updated Tracking Custom Statuses exist – https://tinyurl.com/y4nfd9v5

Of course, your custom statuses “partial-shipped” and “updated-tracking” appear because you have forced them as ‘type’ = ‘default’. Try to change them to ‘type’ = ‘custom’ and you’ll see that they will no longer appear in the general settings.

As I told you, take a closer look at your get_html_ul() function, and you’ll realize by yourself that the code for custom order statuses is no longer there.

Thanks in advance.

Bonsoir @iscpcolissimo,

Avec plaisir, merci à vous pour la réactivité de vos réponses.

Je cl?ture cette demande puisqu’elle concerne des améliorations prévues.

Bien cordialement,
Sylvain

Hi @champsupertramp,

All the best for this new year!

If I am not mistaken, the filter hook ‘um_register_form_enabled_logged_in’ (includes/core/class-shortcodes.php) is not available in the latest version of the plugin (2.1.15).

Your change is however well committed on Github. Could you please check?

Thanks in advance and have a great week-end.

Sylvain

Merci pour l’ajout du filtre ‘lpc_payload_letter_parcel_instructions’ dans la version 1.5 du plugin.

Pour ceux qui souhaiteraient systématiquement mettre à blanc les instructions sur les étiquettes (plut?t que d’afficher la note de commande) :

add_filter( 'lpc_payload_letter_parcel_instructions', 'remove_instructions_from_colissimo_labels', 10, 3 );

function remove_instructions_from_colissimo_labels( $instructions, $order_id, $is_return_label ) {
	return '';
}

Parfait, merci pour votre réactivité !

Je cl?ture cette demande.

Bien cordialement,
Sylvain

Hi @maximumsoftware,

Thank you for your prompt feedback and sorry for the delay of mine.

FYI I opened a ticket through your website with the relevant plugin .zip attached.

Thanks in advance and have a nice day.

Sylvain

Bonjour,

Pour ce warning je vous confirme que c’est OK, merci encore. Je marque en résolu.

J’en ai d’autres sans gravité. J’ouvrirai un topic à part pour plus de clarté.

Très bonne journée.

Sylvain

Bonjour,

Merci beaucoup pour votre retour. Cette modification permettra effectivement d’éviter le warning.

Je vous tiens informé d’ici quelques jours.

Excellente après-midi.

Sylvain

Hi @maximumsoftware,

I hope you are doing well.

After upgrading to version 1.3.2, I saw that it was now possible to edit fields in the “Field Mapper” tool and I thank you for that ??!

This allows me to solve part my request concerning repeater fields, like “your-field__1”,your-field__2 etc…).

On the other hand, I have just noticed a change after filling in the PDF forms.
Even if some values of the CF7 repeated fields are empty (for example nothing in [your-field__2]), I now find in my PDF form field the name of the shortcode of the CF7 field, that is “[your-field__2]”, instead of it being empty.

Of course I have checked that no value was posted for [your-field__2] (nothing in CF7 e-mail where I use this shortcode with option to clear the empty line).

If the CF7 field is not empty, this works fine (value well filled in the PDF form field).

Could you please check this on your side?

Thanks in advance and have a great day,

Sylvain