sotosx

Hello again,

We have found today 2 new eshops with Woocommerce that have a huge issue after the upgrade to WP 6.3.1. Both use Longer Permanlinks because of the greek slugs that we use.

To the issue: A large number of products stopped working and all of them where redirected strangely to the same product. Everything worked fine until WordPress got updated to 6.3.1.

What happened after the upgrade is that all these products’ slugs where reverted to their initial value stored in the _postmeta > longer-permalinks-post-name-longer that was the same for all products. The reason they where reverted to the same slug is that we found that the shop owner used to duplicate an existing product and then edit the title/slug/description etc. So when the product was duplicated the longer permalink plugin stored the same slug value as the inital product, in the _postmeta > longer-permalinks-post-name-longer.

Even now when we create again manually all the product slugs, the field _postmeta > longer-permalinks-post-name-longer does not change and still has the slug of the product that was initally duplicated from.

This issue had a huge impact on our clients eshop and their seo/rankings.

As for my previous post above with the empty slugs issue, it is based on the same malfunction. The owner of this specific blog usually creates most posts as draft (that don’t have slug yet) and schedule the post to be published at a selected date. So at the time the author creates a draft post the _postmeta > longer-permalinks-post-name-longer is empty, and stays empty forever. So when WordPress was updated the posts’ slugs where reverted to the value of the stored _postmeta > longer-permalinks-post-name-longer that was empty.

Please give us a feedback as soon as possible.

Thanks

• This reply was modified 1 year, 2 months ago by sotosx.
• This reply was modified 1 year, 2 months ago by sotosx.
• This reply was modified 1 year, 2 months ago by sotosx.

Hello,

We confirmed today another completely destroyed staging wordpress installation with over 2k posts that lost their slug, of a website we are working on.

The WordPress was updated to 6.3.1 from 6.2.2 and already had longer permalinks 1.28. We had to restore from a backup before the wordpress update and everything is working as expected and all slugs are there.

There is definitely something wrong during the update process of wordpress core. We don’t have any other installed plugins that affects slugs & permalinks in this installation, so this is really weird to let it go and not find out what happened.

Thanks again,

• This reply was modified 1 year, 2 months ago by sotosx.

Hello and thank you for your work on this usefull plugin!

We have also noticed a very strange behaviour in some WordPress Installations after they where upgraded to 6.3.

Many posts completely lost their slug, returning a 404 error. The slug field is completely empty when trying to quick edit the post and after a new save, the slug is generated again.

We noticed this behaviour in many websites whith the biggest one loosing almost 2000 slugs. All these posts do not have the longer-permalinks-post-name-longer postmeta anymore.

Do you believe there was a malfunction of the plugin because of the WordPress Core Update?

We need to address this issue as soon as possible. We have generated again the slugs in small websites, but 2000 posts is a very large number to do it manually in the large one.

Thank you in advance,

S.

• This reply was modified 1 year, 2 months ago by sotosx.