User tests: Successful: Unsuccessful:
The Legacy router grabs the incorrect item ID if you've created a logout menu item before creating the login menu; that's because it doesn't verify the layout. This patch fixes that. No idea how to fix the Modern routing though.
URL Routing
set to Legacy
in Users > Manage > Options > Integration
Users > Logout
menu item and after that, create a new Users > Login
menu item.require_once JPATH_SITE.'/components/com_users/helpers/route.php';
var_dump(JRoute::_('index.php?option=com_users&view=login'));
var_dump(UsersHelperRoute::getLoginRoute());
die;
string(21) "/joomla/index.php/login" string(3) "110"
string(21) "/joomla/index.php/logout" string(3) "109"
Status | New | ⇒ | Pending |
Category | ⇒ | Front End com_users |
This was on 3.8.3 so no relation with that issue. This seems to have been added way back in #7703 - it added a new layout for the logout menu item, but the routing didn't take it into account (it assumed if it's view=login
then it's a login menu item and picks up the Itemid - however, we now have a view=login&layout=logout
which is a logout menu item - a little bit of discrepancy here, but everything should be fine after this is merged) :)
OK - thanks for clarifying that
I have tested this item
I have tested this item
Status | Pending | ⇒ | Ready to Commit |
RTC
RTC
@HLeithner please a final response
1 year old rtc pr
Labels |
Removed:
J3 Issue
|
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2019-05-10 12:51:49 |
Closed_By | ⇒ | HLeithner |
thx
IMO there is a little weird configuration after #7703.
Logout view should have own
view=logout
notindex.php?option=com_users&view=login&layout=logout&task=user.menulogout