Emmanuel Hesry

Hi!
Thank you to report that to us.
There is obviously an issue and we will fix it in a future release.

@leemon
Thanks.
It seems this issue has already been reported and fixed in our side.
https://github.com/polylang/polylang/pull/1154

@patmasayuki
As Polylang changelog says
https://www.ads-software.com/plugins/polylang/#developers

3.3.1 version mainly fixes Polylang Pro issues and some conflicts with other plugins (Sendinblue for WooCommerce and WooCommerce Product Add-Ons Ultimate).

It has no effects on translations.
So you can permanently delete your “polylang.old” folder.

Regards

• This reply was modified 2 years, 2 months ago by Emmanuel Hesry.

@paaljoachim happy to see you found your answer without us ??

Hi!

I’m a developer of Polylang team and I investigated the last week about this issue.
I then propose a fix in the Yoast SEO code because the issue appears since its 15.8 release.

See https://github.com/Yoast/wordpress-seo/pull/16689

Regards

Hello,

You don’t have to update to 2.6.6 if you are not concerned by the fixes
See https://github.com/polylang/polylang/blob/master/readme.txt#L86-L92

The warning is due of the update of WordPress 5.3 and our 2.6.6 version was not ready for this version of WordPress.
See https://polylang.pro/polylang-requires-php-5-6/

So 2.6.7 version correct this warning but you need to be sure you are using PHP 5.6 too.

Regards?

• This reply was modified 5 years, 4 months ago by Emmanuel Hesry.
• This reply was modified 5 years, 4 months ago by Emmanuel Hesry.

Thanks Takayuki for your reply

I already found it. Security plugin disabled REST API and I refreshed permalinks too and all it’s ok.

But there is a little bug here in script.js

var $e = $( '<div class="ajax-error"></div>' ).text( error.message );

because when a http 404 error is coming, error.message is undefined and so the div is empty.

I know, I have to use browser’s dev tools to see this error in the network tab

Best regards
Emmanuel

Hi,

It seems to be a problem with WP Super Cache as lolobu said.
You can see my answer here =>
https://www.ads-software.com/support/topic/regression-in-1-4-9-for-yoast-sitemap_index-xml/#post-8938122

Hope this help

Best regards
Emmanuel

Hi,

I had the same issue between Yoast SEO and WP Super Cache.
When I searched in network flow, I saw sitemap_index.xml was sent with the content type text/html instead of text/xml.
So the browser misunderstood the xml file, did not load main-sitemap.xsl and displayed xml files as a text file.

I don’t know why wp super cache put this wrong content type.

So I decided to exclude all sitemap xml files from wp super cache settings – in the exclude file field in advanced tab.

I added this line => .*sitemap.*\.xml

Hope this helps.

Best Regards
Emmanuel

• This reply was modified 8 years ago by Emmanuel Hesry.

Ok.
The trick is necessary because I can’t modify PHPMailer SMTP Options with MailPoet to resolve PHPMailer troubleshooting with PHP 5.6 and SMTP server self certicated.

See this link I already posted above
https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting#php-56-certificate-verification-failure

To work fine, MailPoet and wp_mail() together, I patched your MailPoet Plugin

I sent to you another message by your form here
https://www.mailpoet.com/support/wordpress-forums/

Thanks
Best regards
Emmanuel

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

yeah : good news see you soon next week ??

Hello,

I have this issue when I activate your Really Simple CAPTCHA plugin.
With all other plugins, it works fine.
It’s a multisite network wich I migrated to WP 4.1

Any idea ?

Hi Zack,

Plugin version 2.0.10

I applied what you said 2 weeks ago and I obtain an URL like this
https://www.wunderground.com/q/locid:FRXX2328

When I put locid:FRXX2328 in shortcode call, it display only a search form with “The Location could not be found”

Thanks for your help
Emmanuel

Hi,

It works fine for me with WP 3.9.1
I only installed the plugin and activated it.

Thanks Lorenzo

Yes, I tried with firefox or chrome with clearing cache too

Me, I develop on localhost and I am used to proceeding by FTP.
In this case, it’s what I also advised.

I’m surprised that only on this website, it didn’t work and I can’t test on hosting for debugging and understanding why.