dirkd

Yep, fixed here too. Thanks.

@marcanor, thank you to report the issue. Glad to see this is being handled.

Can you confirm it is only in posts where you use these symbols : < and > ?

I tried to type the ASCII character code, but it’s always converted to the symbols. So, in HTML it would show :

& l t ; or & g t ;

(remove the spaces)

@m22687
No, I did not roll back because it seems only the symbols are the problem.
However, I do get some errors in some posts.

An error occurred in the ‘fleschReadingEase’ assessment
An error occurred in the ‘textSentenceLength’ assessment
An error occurred in the ‘textTransitionWords’ assessment
An error occurred in the ‘passiveVoice’ assessment
An error occurred in the ‘sentenceBeginnings’ assessment

It seems to show up when using > or < in the post.

See topic here (May 2017) : https://github.com/Yoast/wordpress-seo/issues/7082
So, this is also not solved yet.
I tried to clear the caches but no results ??

• This reply was modified 6 years, 4 months ago by dirkd.
• This reply was modified 6 years, 4 months ago by dirkd.
• This reply was modified 6 years, 4 months ago by dirkd.
• This reply was modified 6 years, 4 months ago by dirkd.
• This reply was modified 6 years, 4 months ago by dirkd.

@marcanor

What an easy reply. So, we are all using wrong plugins ?

There is no conflict with other plugins or themes !
I am running different sites with various themes, various plugins, on various servers.

Tested with Yoast 9.0.1 => NO problem !
Updated to 9.0.2 => problem (no symbols) !
Changed to Twenty Seventeen => problem still there

The problems shows in ALL my sites after updating to Yoast 9.0.2 !

See screenshot here

@shahahmadyusof No, there are no errors in the console.

Yep, symbols disappeared after recent update! Just as Shah showed in the screenshot above.

Any update on this ?

Same problem here. Support ?

• This reply was modified 6 years, 6 months ago by dirkd.

Yep, same problem here. Upgrading to 10.0.1 does not fix the issues.
Empty widgets and running wheels.

Same problems here ! Even after upgrading to 10.0.1 the situation stays the same.
Cleaned cache, logged out/in and restarted browser but no solution.
Empty widgets and running wheels.

OK, so tonight both WPML and NextGEN were updated. It did NOT solve my redirecting issues.
The problem is definitely connected to these WP bugs :

https://core.trac.www.ads-software.com/ticket/35012
https://core.trac.www.ads-software.com/ticket/35031

It seems it has something to do with slugs being renamed and new pages generated with the old slug. I remember I changed some slugs a long time ago, so this does actually make sense. It is weird however, that the problems suddenly came up with 4.4.
The proposed code fixes still do not work for me, with NextGEN active.

Now, I solved my problem myself by renaming the slugs of the original affected posts. I left the slugs of the translations intact. Of course, this way I would generate 404 errors in Google searches, so I also created 301 redirects to catch them.
It was a huge job and I still don’t feel good with this ‘solution’ but at least my posts work normally again, with new slugs for the original language (not the translations).

I do hope WP will come up with a working solution fast because now it seems we need to be very careful with handling our slugs.

Hi iamfablaz,
Good to hear that the code fix worked for you. Well, I had some very long discussions already with WPML support and now here too ??
But concerning WPML we already found out that even with the WPML plugins deactivated the problem still comes up with NextGEN active, and disappears when NextGEN is deactivated.
That’s the stage where I am in now. The WP code fix seems to work but – in my case – not when NextGEN is active.
Hope to hear back from support soon.

As far as I know it is necessary to put the code fix inside the theme’s functions.php.
I mean the code fix mentioned here :

https://wpml.org/forums/topic/after-updating-wpmlwp-some-posts-automatically-redirect-to-english-version/page/2/#post-771536

It’s a fix for a bug in WP 4.4.

Did you use that fix too ? This solves the issue for me with NextGEN deactivated.

Hi Cais, thanks for the quick reply.
I reopened my ticket with WPML. They tested further and send me this reply :

Hello Dirk,

I did the following tests:

A1. Added my snippet in functions.php (see previous ticket)
A2. Deactivated WPML and activated NextGEN
A3. => https://outandabout.dev/baanbrekende-osprey-atmos-rugzak/ is redirected to https://outandabout.dev/groundbreaking-osprey-atmos-ag65-backpack/ (NOT expexted result).

B1. Added my snippet in functions.php (see previous ticket)
B2. Deactivated both WPML and NextGEN
B3. => https://outandabout.dev/baanbrekende-osprey-atmos-rugzak/ is not redirected. (expected result).

So my conclusion is that the issue is somehow related to NextGEN gallery (because it happens when WPML is deactivated).

Note that the fix I have provided is related to an issue with WordPress core. So at this point I’m not sure I can help.

Regards,
Pierre

So, I am out of options now. I am going to wait for your next release and also the upcoming WordPress update. If this does not lead to a solution I will have to find an alternative for my galleries, because all the rest simply works fine.