[#19381] - Menu Item Batch Process Alias Check Bug
- New
- Medium
- Build: master
- # 19381
Steps to reproduce the issue
Create A Menu Type Menu A and a menu type Menu B
in Menu A create items:
A
B
C
D
In Menu B create:
E
- A
- B
-- A - C
Try to move the complete E-Tree to Menu A with batch process.
An error apears that Alias A is already existing in Menu A. (But not in that structure)
Try to bypass this error by creating a new submenu Item E in Menu a and give it an alias new-e
Move the submenu Items of Menu B into Menu A into the new created E item.
An error apears that Alias A ist already existing in Menu B ( but i am just about to move them to A)
Additionally the Menu items are shuffled after the error message.
Expected result
You should be able to move the whole tree
Actual result
It's not possible to move it...
System information (as much as possible)
Joomla 3.8.3
Screencast:
http://recordit.co/0wNxn5bqBU
| Labels |
Added:
?
|
||
ok... my issue is now to move a top item with 150 subitems to another menu without issues. If anyone has an idea how to comment the checks out properly to quickly fulfil this task, would be much apprechiated. I tried already to comment out severall lines in libraries/legacy/table/menu.php public function store but It still did not work...
franz-wohlkoenig
- | Status | New | ⇒ | Discussion |
| Category | ⇒ | com_menus |
do it manually in the database?
I will probably go crazy by editing the lft and rgt values for 150 Items, or do they stay the same?
if the structure is the same then iirc they will stay the same. it is just the parentid you will need to change
Unfortunately it does not work to just set menutype and parentid in the menutype
Maybe you should try to use the Rebuild button.
No it does not work. My Problem is that I have to move in total 600 menu items (5 languages) from one menu to another and because of that bug it does not work. changing values manually in database doesn't work.
unable to reproduce on staging no-multilingual
| Labels |
Added:
J3 Issue
|
||
| Status | Discussion | ⇒ | Closed - Unconfirmed Report |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-03-11 19:36:45 |
| Closed_By | ⇒ | jwaisner |
| Status | Closed - Unconfirmed Report | ⇒ | Closed |
| Closed_By | jwaisner | ⇒ | joomla-cms-bot |
Set to "closed" on behalf of @jwaisner by The JTracker Application at issues.joomla.org/joomla-cms/19381
Closing as this cannot be confirmed as an issue in the staging branch.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/19381.
I confirm that the issue still exists, I can demo it in a staging branch
| Status | Closed | ⇒ | New |
| Closed_Date | 2020-03-11 19:36:45 | ⇒ | |
| Closed_By | joomla-cms-bot | ⇒ |
sure it is on my corona list :D
Confirming the exact same issue is present in j4
Tested by @webnet-assmann and me and not reproduceable anymore, @brianteeman should I close or do you want to retest as well?
Still reproducable
Thank you for retesting ! @brianteeman
Could someone change the label to j4 issue please
| Labels |
Added:
No Code Attached Yet
J4 Issue
Removed: ? |
||
I said change the label not add a new one - please. And check the others you have updated
| Labels |
Removed:
J3 Issue
|
||
| Labels |
Added:
bug
|
||
You dont even have to move it from menu a to menu b. The same thing happens in a single menu.