Rasti Tkac

Hi @sarathkumarrajendran

Thank you for your feedback.
I was able to make it work.
However, I had to substitute a few more $.ajax() and $.each() statements to jQuery.ajax() respectively jQuery.each().
One by one until there were no more errors in the console.
Not sure how my installation is different from those where your plugin works.

I am on:
PHP 7.4.27
WP 5.8.3
WooCommerce 6.0.0
Conversios.io 4.6.6

Best regards,
Rasti

Hi @tatvic,

The issue is not yet resolved.
On the same page, in the second step (Connect Google Analytics Account), when selecting the radio buttons “How do you plan to tag your website?”:

• an error appears in the console https://cln.sh/Kbxvk2
• and the loading animation spins endlessly again https://cln.sh/oVvgY6

We updated to the latest version of your plugin 4.6.5.
And we tested it on Chrome as well as Firefox and Safari.
Thank you for looking into this.

• This reply was modified 2 years, 9 months ago by Rasti Tkac.
• This reply was modified 2 years, 9 months ago by Rasti Tkac.

It appears that jQuery is not loaded on that page.
Funny thing is, that this happens only on the settings page (dashboard) of your plugin and not on other settings pages that use jQuery.
Do you have an idea, why this could be?

Hi @tatvic

Thank you for your feedback.
The JS errors seems to come from your plugin as you can see in this screenshot: https://cln.sh/pW28oD

Best Regards
Rasti

I created an issue on official repo: https://github.com/Yoast/wordpress-seo/issues/17681

I can confirm that this issue was introduced in Yoast SEO 17.6.
Version 17.5 doesn’t have this issue.

@duongcuong96 I tried the fix you recommended, but it doesn’t seem to solve the problem. The tokens are still expiring every 20 to 30 seconds.
What else can be done here?

[11-Oct-2021 10:01:08] Archivgr??e ist 834,94 MB.
[11-Oct-2021 10:01:08] 20273 Dateien mit 1,03 GB im Archiv.
[11-Oct-2021 10:01:08] 1. Versuche, das Backup zur Dropbox zu senden …
[11-Oct-2021 10:01:08] Token has expired; new token has been obtained
[11-Oct-2021 10:01:09] Authentifiziert mit der Dropbox von: Support Webkinder
[11-Oct-2021 10:01:09] Hochladen zur Dropbox hat begonnen …
[11-Oct-2021 10:01:09] Beginne neue Datei-Upload Session
[11-Oct-2021 10:01:39] Token has expired; new token has been obtained
[11-Oct-2021 10:02:06] Token has expired; new token has been obtained
[11-Oct-2021 10:02:36] Token has expired; new token has been obtained
[11-Oct-2021 10:03:06] Token has expired; new token has been obtained
[11-Oct-2021 10:03:36] Token has expired; new token has been obtained
[11-Oct-2021 10:04:05] Token has expired; new token has been obtained
[11-Oct-2021 10:04:34] Token has expired; new token has been obtained
[11-Oct-2021 10:05:04] Token has expired; new token has been obtained
[11-Oct-2021 10:05:33] Token has expired; new token has been obtained
[11-Oct-2021 10:06:02] Token has expired; new token has been obtained
[11-Oct-2021 10:06:31] Token has expired; new token has been obtained
[11-Oct-2021 10:06:58] Token has expired; new token has been obtained
[11-Oct-2021 10:07:28] Token has expired; new token has been obtained
[11-Oct-2021 10:07:57] Token has expired; new token has been obtained
[11-Oct-2021 10:08:27] Token has expired; new token has been obtained
[11-Oct-2021 10:08:57] Token has expired; new token has been obtained
[11-Oct-2021 10:09:27] Token has expired; new token has been obtained
[11-Oct-2021 10:09:56] Token has expired; new token has been obtained
[11-Oct-2021 10:10:02] Upload beendet: Es wurden 835 MB hochgeladen
[11-Oct-2021 10:10:04] Backup übertragen zu /Backups/fructus/fructus-weekly_2021-10-11_09-56-05_HHCC3VSY01.tar.gz

Hi @mikes41720

Our concern is that we cannot translate that string correctly into german, because taxonomy name is forced to be lower case.

This is problem in german, because nouns in german are to be written with capital letter. So the translated string would be “W?hlen sie prim?re Kategorie”.

In the code linked above the .toLowerCase() must be omitted to allow for correct translation. I don’t see any reason, why that string should be forced to be lower case in any other cases anyway.

Best regards,
Rasti

• This reply was modified 3 years, 2 months ago by Rasti Tkac. Reason: Better formulation

@ryanhungate
1. This was a clean installation. So there were no records in queue table. (For reference: we just found out on another installation that previous versions worked.)

2. We have other installations on the same server which are working with POST requests and handling them without problem.

3. This particular installation is on a “angency server” which has a dedicated IP, but I am cross-checking that with the hoster — just to be sure.

4. AKAMAI block was the first thing I checked (https://kb.mc4wp.com/solving-connectivity-issues/)

Maybe it helps to mention that I checked if it was:
– memory_limit related (no)
– curl version related (no)
– DNS related (no)
– mod_security related (no)

Hi @ryanhungate

Thank you for your feedback.
To answer your questions:

• Our hoster is https://www.cyon.ch
• The file is reachable from outside, when called directly https://somesite.ch//wp-admin/admin-ajax.php (returns 0). Permissions on the file makes it also readable to everybody.

No we don’t have any plugins that would disable the file.

Kind regards
Rasti

You’re right, i see it now.
Thank you for pointing it out.
Yes it makes sense to me. I will try to find out what conflicts with it.

Yes, the version of your plugin is 1.1.3.
It’s weird, I can’t make it do what it should even on Polylang.
1. I’ve translated processing order and on hold order strings https://jmp.sh/veoYLio
2. Only on hold order mail arrives translated. Processing order ignores the translation: https://jmp.sh/QduJyKo

I first thought that it might be a problem that the strings are the same (which would be unfortunate), but even after changing the strings and their translation (and deleting the old strings from database via Polylang String translation) the emails would arrive in same manner (on hold correct, processing not correct).

Hey,

My versions are pretty same:
WooCommerce: 3.5.3
WPML Multilingual CMS: 4.1.3
WPML String Translation: 2.9.1
WooCommerce Multilingual: 4.3.7

The domain admin_texts_kt_woomail is unfortunately not in the dropdown (after saving new texts in the customizer AND after rescanning the plugin): https://jmp.sh/N2VxOO0

Hey!
Thanks for a lightning fast answer.
Yes, I am aware of subject and header strings in both WPML and Polylang.

I’ve got problem with the strings that are visible only in custommizer.
Please, review my workflow in following steps (screenshots):
1. Set a custom subtitle and body texts in customizer (https://jmp.sh/GJBezIa)
2. Search for previously set strings in WPML String Translation; I’m able to find subject and heading but not subtitle or body strings ( https://jmp.sh/lMi456T )

Extra info: Yay! I’ve been able to make it work in Polylang but not in WPML String Translation. In WPML I even rescaned the plugin (both woocommerce and your plugin) as they recommend in their documentation but still no luck finding those strings.

Best regards,
Rasti

Thanks for your notification Moumita,

I can confirm, that update 1.4.2 will resolve problems on woocommerce 3.0.4 but the plugin remains broken for woocommerce 2.6.14

Kind regards, Rasti