CB

Proposed fix is for J1.6+ only and it'll check your lang tag against the database row to ensure the database row is your lang tag or is for all languages before pulling the itemid, will prevent russian language for example pulling english language menu itemid (which would give a 404 error). The only possible problem is the lang tags are use defined in Extensions > Language Manager > Content.. so if the user doesn't supply as ru-RU for example it won't match, but not much we can do to avoid that except check the GET for the lang then check that against the database for its tag then check its tag against the menu link and that's a lot of overhead per page load for Itemid.

Implemented in r1736 with additional IN case '' (seen this for some menus in 2.5 installs)