Create a page
site.ru/article
site.ru/blog/article
Add to the URL address of a non-existent
site.ru/article-123
site.ru/blog/article-123
site.ru/blog/article/123
site.ru/article-123 = 404 Error
site.ru/blog/article-123 404 Error
site.ru/blog/article/123 404 Error
site.ru/article-123 = 404 Error
site.ru/blog/article-123 The page reloads, open the same article, the wrong URL
site.ru/blog/article/123 404 Error
Tested in Joomla! 3.5.1, 3.6.5
SEF = on
Also,
Do you have articles or categories with the same id? If so they will always load since this is how the router is coded. Nothing they can do about it.
Many thanks
Tony
SEO Options http://prntscr.com/dmhl3x
Example:
http://arahort.pro/contacts/ -> http://arahort.pro/contacts-123/ = 404
http://arahort.pro/blog/53-samoskryvayushchiesya-yakorya-s-plavnoj-animatsiej-jquery/ -> http://arahort.pro/blog/53-samoskryvayushchiesya-yakorya-s-plavnoj-animatsiej-jquery-123/ = not 404
blog - blog category "Блог"
This is an old known issue, also present in staging.
Agreeded. The solution will be Joomla! 3.7 with the new SEF system which IMHO should be enabled by default for new Joomla! Installations, this would prevent the above type of issues occurring again.
Actually it should since the numbering won't be in the urls by default. I know it won't solve it for previous sites and it can't since the way the routers work.
But if there is no id in the URL in the first place i.e. the new routing system then the issue can't occur.
Bringing this backup, still a big issue here. New router doesn't seem to pickup 404's in the com_redirects component and always loads 404's to the homepage without showing any error.
Example. Enabled new router and remove ids from URLS. visit your new menu item which is linked to say a single article. remove 1 character from the url. Your site just loads the homepage. Fresh base Joomla! install. This is an issue.
shouldn't that be resolved before release?
Yes it should have, turns our the new router needs quite a bit of work :-(
yep @franz-wohlkoenig I've been chatting with George the last couple of days. It's a complex issue :-(.
You can not fix this issue by default for everyone without breaking backwards compatibility. It is fixed in 4.0-dev
Yup :)
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-03-04 10:38:08 |
Closed_By | ⇒ | wilsonge |
Can you confirm which sef options you have enabled?