User tests: Successful: Unsuccessful:
Pull Request resolves #19652
Changed the method populateState() in itemModel.php to setUserState ( menu type, client id) only when a new menu item is being created.
What this does is that when we edit a menu item and click on 'save and close' we will be redirected to the list view of menu items with the original menu type filter instead of it being set to the menu type of the article that was edited.
But when we create a new menu item the previous functionality is preserved.
[ DO NOT test just yet as ideal behavior when the menu type of a previously existing item is changed while editing is ambiguous ( need help of maintainer) ]
Case 1: Editing
Case 2: Creating
Case 3: Editing ( change menu type )
get redirected to list view of menu items with the menu type filter set to the menu type of the article edited / created.
Case 1:
get redirected to list view of menu items with the original filter ( ie no filter ).
Case 2:
same as before
Case 3:
same as before
Please select:
Documentation link for guide.joomla.org:
No documentation changes for guide.joomla.org needed
Pull Request link for manual.joomla.org:
No documentation changes for manual.joomla.org needed
| Status | New | ⇒ | Pending |
| Category | ⇒ | Administration com_menus |
| Labels |
Added:
PR-5.4-dev
|
||
as getUserStateFromRequest() updates the session state, explicitly updating it later might be redundant
can a maintainer let me know what the ideal behavior for case 3 is ? ( i went through the conversation of the issue and could only find the desired behavior for case 1 and case 2 )
Currently, even if you change the menutype from 'X' to 'Y' and then immediately back to 'X' it still redirects back to list view with menu type filter set to 'X' and im not quite sure where the session state is getting updated for that to happen.