joy0114

Hi @reynierc ,

Thanks a lot for all your advices !

Unfortunately, I have already done these verifications, and it does not work..

I started use polylang to fix subject and header translations of emails. It works with the help of Polylang.

But, for email’s content, I have to modify templates, in order to call pll__(xxxx) instead of printf( esc_html__( ‘Hi %s,’, ‘woocommerce’ ), ….

Well, I switched this topic in “solved”, but I really think there is something strange which is suddenly arrived (probably with WP 6.7 …)

Anyway, thanks for your help and advices.

Best regards

Hi Qtwrk,

I have absolutely no idea …
Just that this is a part of this bad request, and that leads to a page 404:

Line 80: 12/17/24 12:05:40.519 [malicious_ip:26751 1 oVz] [Data] load url file: 404

Sometimes strange things happen on requests leading to a 404 response.
Anyway, thanks for your attention to my concern.

Best regards

Hi Gaurav,

Strange … I’m using 3.7.3 and wordpress debug tells me the “well known” warning about textdomain, is always present.
All server caches had been purged (files, opcache, object cache, js).

Do you think it could be relative to Loco Translate which deals with all my plugin’s translations ?

In Loco, I’ve got your translation, in plugins/woo-advanced-shipment-tracking/lang/woo-advanced-shipment-tracking-fr_FR.po
And mine (not updated with your plugin), in languages/loco/plugins/woo-advanced-shipment-tracking-fr_FR.po

I precise that Loco Translate is loaded before AST.

Thanks if you have any idea …
Best regards

Hi MrClayton,

Ok, thanks for your answer.
We’ll see next year, I’m in no hurry now.
Have a nice holiday season.

Best regards

Okay, thanks, I’ll try that.
Anyway, as soon as I figure out why I’m not allowed to save the configuration … Strange …

Best regards

Hi,

I putted it on:
https://pastebin.ubuntu.com/p/QhCnGV7Jq5/

If you have a few minutes to look at it, that would be great!

Thanks a lot.
Best regards

Hi Qtwrk,

In debug.log, the section about this visit (and only this one) is about 32Ko.
Do you think I can post it here ?

By the way, I precise my plugin configuration does not contain any automatic purge rule.

Report : YSDMHGLM
Date: 12/17/2024 22:23:55

Thanks !
Best regards

Hi Qtwrk,

Thanks a lot for your feedback.
Ok, so it seems “useable” !
On my side, some tests with a staging site don’t give me errors.
Well, I think I’m going to switch towards 8.3.

Best regards

Hi @bsfaradhy,

I took your advice to switch to the new header…
What a pain !
And of course, there’s no way of going back…
And frankly, not everyone needs to manage their header and footer in a beautiful GUI, with modules to move around to build .
Some people have simple, unchanging, or almost unchanging, headers and footers, so there’s no need for many people to burden the DOM and review all the css rules for these areas.

But, well, it seems that complexity is a sign of progress. Personally, I like the “keep it simple and stupid” type of computing.

In short, we’ll say it’s solved, because the cause of the problem has been found (Astra opted for complexity over simplicity and efficiency, but wouldn’t we do for the UX God ?)

That said, see you soon in another post, because of course, the “new header/footer” also impacts the rest of the page …

Best regards

Thanks for your confirmation.

As to me, I never update the site in production… always on a staging site.

Ok, Thank you for your quick answer !
And congratulations for your very good plugin.

Best regards

Hi Xootix,

Ok, thank you for your answer !
Best regards

Hi Jami23,

You’re right: probably another issue with nonces …
By the way, that’s nonce’s issues that make this plugin NOT compatible with ESI of Litespeed. And that’s too bad !
The wishlist plugin of YITH had solved this kind of problems and is compatible with LS (and ESI feature), that’s why I don’t understand why WPC who made a good and friendly plugin, does not work with LS developers for also making their plugin compatible with Litespeed …
WPC has been aware of this for months !

I hope they’ll take this issue seriously: litespeed is still widely used !

Hi,

Perhaps I’m wrong, but I think there are several fragments, so with a “s” at the end of “fragments”.

You can try “wc-cart-fragments”, but it should also work with “cart-fragments” since LS searches for strings.

I can’t guarantee anything: I haven’t tried it but let us know if it works…

Best regards

Ok, I understand now …
I haven’t seen version 9.1.2 at all.

You’re right, test phases are not enough, and indeed this has been going on for some time now.
Personally, I let one or two releases pass before updating.

Thanks for your answer, because several posts were talking about this version, and I had no idea where it was coming from …