gaspar

Marked it as “unresolved” – this problem still exists, also in the latest version of CF7.

Any news about how to resolve this problem, Takayuki Miyoshi?

Tried to contact you in Slack..

Well. I made some progress with debugging the issue.
Installed Flamingo for that. And it reports:
“Spam log: reCAPTCHA response is empty.”

We are using Google Captcha v3.

It worked well until latest update. Has something changed in the latest version(s) of CF7?

How can i contact you and send this information?

So i figured it out finally.

The correct syntax is wp yoast index --reindex --skip-plugins=$PLUGIN_LIST

$PLUGIN_LIST – substitute this with your plugin list, separated by comma, excluded wordpress-seo (Yoast plugin).

This allows reindex all YOAST SEO data.

Extra tip. You can also add --skip-themes to avoid problems with theme(s) code.

• This reply was modified 2 years, 3 months ago by gaspar.
• This reply was modified 2 years, 3 months ago by gaspar.
• This reply was modified 2 years, 3 months ago by gaspar.
• This reply was modified 2 years, 3 months ago by gaspar.

This command doesn’t work:

wp yoast index –reindex –skip-plugins=wordpress-importer
Error: Too many positional arguments: –reindex –skip-plugins=wordpress-importer

PHP 7.4.32 (memory_limit 1024M)
MYSQL 10.4.26-MariaDB
WP-CLI 2.6.0
Wordpress 6.1.1
wordpress-seo 19.10

It was not your plugin..
Another shortcode function decided to mess it up.
Thanks for the input.

Well.. The problem is your plugin can not change theme template because it is not compatible with woocommerce – that was my point. I just wanted to let you know. And maybe to get some advice or future update.
At least add this to your plugin description so everyone else knows it and do not spend time to figure it out why it is not working.

Have a nice day.

Well, the main problem is it caches the result.
It creates hash based on template name.
The hash is same for original and switched theme.
Same thing with wc_get_template_part().

Yes, it is related to float values.

The problem resolved automatically – it takes some 24hrs for GA to catch up.

Thank you for your support.

You can use jQuery selector. And it works

Let’s contact privately.

Thanks!
I sorted everything out.
1) The problem was Qtranslate-X Slug. It made several problems beside that. I switched it off. Your plugin is getting the right locale now!
2) I assumed (as other plugins do) the translation files should be under plugins folder. I changed the location and it get’s right language files now.

Regards!

• This reply was modified 8 years, 1 month ago by gaspar.

hello, pcarvalho ??

Any news?

I tested it, it always gets the default language (not chosen one by Qtranslate-X).

Second question, i would like to make special translation.
Usually the extra plugin translations are in /wp-content/languages/plugins folder (it does not have system russian translation for example – so it can reside this folder without overwritten by an update). Your plugin doesn’t support it?!