You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Log in to Joomla backend,
go to All menu items, select menu item(s), click 'Batch' you will see
"To use batch processing, please first select a Menu in the manager." message in modal window.
Now add new menu item, select some items click batch - modal window will open with batch options.
Logout -> login and again select some items and open batch window, "To use batch processing, please first select a Menu in the manager." will show up.
Expected result
Batch process modal window with batch options even if single menu item is selected.
Actual result
Batch process modal window with batch options showing up only after adding new menu item.
System information (as much as possible)
Joomla 3.6.2
Additional comments
The text was updated successfully, but these errors were encountered:
Either I am doing something wrong or I cannot replicate your issue
It is expected behaviour that if you are on ALL MENU ITEMS ie you have not selected a menu then the batch functionality is disabled but if you have selected a MENU (not an item) then it is enabled
Steps to reproduce the issue
Log in to Joomla backend,
go to All menu items, select menu item(s), click 'Batch' you will see
"To use batch processing, please first select a Menu in the manager." message in modal window.
Now add new menu item, select some items click batch - modal window will open with batch options.
Logout -> login and again select some items and open batch window, "To use batch processing, please first select a Menu in the manager." will show up.
Expected result
Batch process modal window with batch options even if single menu item is selected.
Actual result
Batch process modal window with batch options showing up only after adding new menu item.
System information (as much as possible)
Joomla 3.6.2
Additional comments
The text was updated successfully, but these errors were encountered: