What I’ve noticed looking at the database records and also at the html code: The slug sting is actually not encoded (e.g. whit rawurlencode() function) which cause the 404 error (it appears the default wordpress 404 page)
I’ve tried to find the place where is the MySQL query which updates the post to encode the slug sting but did not succeed.
Could someone help me with this because the Support team (inducing the head of the support) is incapable solve this problem more the 10days.
I’m using WPML 2.4.2
PS: This bug is because of the plugin because after desalinating wordpress works fine.
]]>I can set a DIFFERENT slug for the nav_menu_items, but not the same (it seems wp core is not ready to keep them apart from the actual post safely, yet)
I tried using menu_order, but it’s not safe.
Adding classes to the menues won’t export to the other blogs when exporting the pages (I’ll make a set of master pages in one site and then export them to the others)
Could you please, since using the same post_title or post_name is not an option, make a new function to add the post_name to the li class, somehow?
Thanks.
]]>https://www.coldclimate.co.uk/2002/01/01/Atlast—a-track-listing/ is a real post (see https://www.coldclimate.co.uk/2002/01/01/) but you can’t access it.
Looking in the db it would seem there is a column for these urls – wp_posts.page_name.
Is there a way to get WP to recalculate all these values. There seems to be a sanitization routine, but I don’t want to write a script to call it and UPDATE each row if possible.
]]>See: https://www.york-newyork.com/seo-plugin-wordpress-urls/
Includes an admin screen and is under GPL.
I was looking for a solution like this, and apparently not the only one: https://www.ads-software.com/support/topic/44342
Enjoy!