Thread Starter
mrppp
(@mrppp)
Can someone clarify this before ui update other sites please
should the remove stop words from slug only apply to NEW pages/posts/events etc rather than alter existing?
Do any of these issues ever get read by support? not many rectified
Thread Starter
mrppp
(@mrppp)
Even with it unticked it still rewrites titles to remove stop words
And if you put the old version back it does the same.
Actually it is rewriting urls on sites i have not even updated!
Thread Starter
mrppp
(@mrppp)
This is a nightmare, even sites i have not updated with latest update rewrite slugs when updating pages causing the old slug to 404, how can this be good seo?
You’re right – it really should only apply to NEW posts/pages.
You can turn off the function completely in the plugin Permalinks settings – 3rd item
Thread Starter
mrppp
(@mrppp)
I can’t it still rewrites with it turned off
Think i will leave latest update on other sites, i would end up with hundreds of pages giving a 404
Strange though that sites without the update are re writing new pages i create?
Thread Starter
mrppp
(@mrppp)
I think the rewrite must have been in last update too. As prior to that it allowed stop words, but testing on last version it does re write
But trying a local copy updating an existing page with a stop word in slug does not get re written
EDIT oh maybe because i just updated todays two other revisions on local copy
1.4.18
Unhooking ‘shutdown’ (part of the NGG fix in 1.4.16) caused caching plugins to break, fixed while preserving NGG fix.
1.4.17
Missed a line in the commit of the option to stop stop words cleaning.
Many Thanks @mrppp and @mikeotgaar for your posts.
My permalink structure is /%category%/%postname% and after the update to WordPress SEO 1.4.18, access attempts to ALL my posts resulted in 404 errors. I disabled WordPress SEO and all my posts reappeared so I knew the plugin was blame.
After switching off the “remove stop words” option, normal service was resumed.
There were no stop words in the slugs anyway so there is clearly some bug in the stop word processing.
