WP-Seo by Yoast-update – PolyLang errors

I didn’t solve the problem, but at least, the warnings aren’t showing by doing this:

Add to functions.php:

ini_set( ‘display_errors’, false );
error_reporting( 0 );

at the beginning of the file.

Meanwhile, waiting for a better solution!

Which way is better for the functioning of the site?
Disabling WP-SEO or error reporting?

In my opinion, the best way is to revert to WPSEO 1.7.1

I confirm. Reverting to WPSEO 1.7.1 solved the error for me. However now I have the WPSEO on the plugin update list, so I hope the problem will be fixed eventually.

Okay, reverting helps except with WordFence!

If there is a problem between WordFence and WPSEO, I can’t help.

For the WPSEO regression impacting Polylang, the WPSEO team is working on it. I can’t do anything before knowing what will be their direction.

Polylang 1.6.5 should fix the issue with WPSEO 1.7.3

Thank you Chouby, once more, for the excellent support!

I reverted back this morning to WPSEO 1.7.1 based on your recommendation on that worked. Now I see that you have already released a new version. I’ll wait a few days to install it. Thanks!

Newbie here calling ??

I deactivated WPSEO because… I don’t know how to get back to a previous version.

Anyone could tell me briefly how I could do that please ? ??
Thanks in advance.

@happysun

You don’t need to use the previous version of WPSEO. You can re-activate it and use it together with the latest Polylang 1.6.5.

I already updated to 1.7.3.1, but still have the same problem.

Warning: array_merge(): Argument #1 is not an array in /home/passiona/public_html/wp-content/plugins/polylang/include/plugins-compat.php on line 89

Warning: Creating default object from empty value in /home/passiona/public_html/wp-content/plugins/polylang/include/plugins-compat.php on line 89

Warning: array_merge(): Argument #1 is not an array in /home/passiona/public_html/wp-content/plugins/polylang/include/plugins-compat.php on line 89

Warning: array_merge(): Argument #1 is not an array in /home/passiona/public_html/wp-content/plugins/polylang/include/plugins-compat.php on line 89

Warning: array_merge(): Argument #1 is not an array in /home/passiona/public_html/wp-content/plugins/polylang/include/plugins-compat.php on line 89

Warning: array_merge(): Argument #1 is not an array in /home/passiona/public_html/wp-content/plugins/polylang/include/plugins-compat.php on line 89

Warning: array_merge(): Argument #1 is not an array in /home/passiona/public_html/wp-content/plugins/polylang/include/plugins-compat.php on line 89

Warning: array_merge(): Argument #1 is not an array in /home/passiona/public_html/wp-content/plugins/polylang/include/plugins-compat.php on line 89

WordPress SEO will *never* revert the change made. Please use Polylang 1.6.5

Hi, I’ve just installed Polylang 1.6.5. and I’m suffering this error:

Fatal error: Call to private method WPSEO_OpenGraph::og_tag() from context ‘PLL_Plugins_Compat’ in /home/content/48/6600648/html/versogramas/wp-content/plugins/polylang/include/plugins-compat.php on line 197.

I can’t see my website, I had to deactivate the plugin to get it back to normal.
My version of WPSEO is 1.4.24.
I’m using WordPress 3.9.3. running Twenty Twelve theme

What is this happening? How could I solve it?
Thanks for your help

@celiap

What is this happening?

Obviously Polylang 1.6.5 is not compatible with WPSEO 1.4.24 ??
But this topic is about the compatibility with WPSEO 1.7.2 ??
As a side note, obviously you missed about 34 updates of WPSEO… Do you believe that I tested all these versions with Polylang 1.6.5 ? ??

Hi,

WordPress SEO 1.7.4 and Polylang 1.6.5 is getting me a 404 error on all the pages associated with Cherry Plugin 1.2.6.

An example is on my homepage, if you click in any of the customers links at the bottom it gives 404.

Also if you go here https://fontaneriaborja.com/en/work/

All of them give a 404 error.

I think Polylang is awesome but I also want to keep WordPress SEO. What can I do?

Thank you in advance for your help.

UPDATE: I have deactivated and activated the WordPress SEO plugin and now it seems to work. Weird.