When Joomla SEF is enabled, the url looks like this. For example, I'll use an article from K2.
getk2.org/blog/item/993-k2-v261-now-available
But the article alias doesn't seems to be checked properly, so it can be renamed to something else and the same article still display regardless.
Say the example url above, I rename them to:
getk2.org/blog/item/993-k2-v261
getk2.org/blog/item/993-something-offensive
getk2.org/blog/item/993
It seems that as long as the itemID is in the url, the article will still display regardless of the alias. This is quite a big issue because it leads to a very possible abuse by changing the alias to something offensive then sharing the link & getting index by Google.
The correct behavior should be a 404 error when the alias doesn't match. This problem can be found on every Joomla or Joomla+K2 site, whether it's 2.5.x or 3.0.x
I see that this problem was reported recently on Joomla where the fault was pointed to component\com_content\router.php
joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=29428
github.com/joomla/joomla-cms/pull/472
Now I see that in component\com_k2 there's a router.php. as well. Does the router.php in K2 require changes as well to fix the issue? Or is this problem strictly with Joomla only?
getk2.org/blog/item/993-k2-v261-now-available
But the article alias doesn't seems to be checked properly, so it can be renamed to something else and the same article still display regardless.
Say the example url above, I rename them to:
getk2.org/blog/item/993-k2-v261
getk2.org/blog/item/993-something-offensive
getk2.org/blog/item/993
It seems that as long as the itemID is in the url, the article will still display regardless of the alias. This is quite a big issue because it leads to a very possible abuse by changing the alias to something offensive then sharing the link & getting index by Google.
The correct behavior should be a 404 error when the alias doesn't match. This problem can be found on every Joomla or Joomla+K2 site, whether it's 2.5.x or 3.0.x
I see that this problem was reported recently on Joomla where the fault was pointed to component\com_content\router.php
joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=29428
github.com/joomla/joomla-cms/pull/472
Now I see that in component\com_k2 there's a router.php. as well. Does the router.php in K2 require changes as well to fix the issue? Or is this problem strictly with Joomla only?