[#22019] - The alias com-xxxx-name is already being used by COM_XXXX_NAME menu item ...
- Closed
- 4 Jan 2020
- Medium
- Build: 3.9.0-alpha
- # 22019
Steps to reproduce the issue
- Install an extension that still have this legacy tag in the configuration XML:
<!-- Administrator back-end section -->
<administration>
<menu view="cpanel" img="../media/com_xxxx/images/xxxx-icon.png">COM_XXXX_NAME</menu>Expected result
Installation success.
Actual result
Error: The alias com-xxxx-name is already being used by COM_XXXX_NAME menu item ...
System information (as much as possible)
Joomla_3.9.0-alpha-Alpha-Full_Package. PHP 7.1.21.
Additional comments
The menu tag was used for icon definition on Joomla 1.5/2.5, but it is currently useless. However, there are many extensions that still have it in the XML configuration and the error is shown in the extension installation on Joomla 3.9.
I'm testing on a clean J39 installation and the backend menu item is being created even without menu tag.
So, something has changed between J38 and J39, and an error is generated now.
Please, check this extension on J39 to better diagnose the case: https://www.extly.com/downloads/autotweetng-free/autotweetng-free-8-21-0.html
i just tried to install that extennsion but got the following error
@brianteeman Really weird, it seems that it is updating without creating the tables. That line is only present in a script for an old version upgrade 7.2.0.
UPDATE: I've confirmed that other extensions (Weblinks, K2, etc) are installing fine. So, I'm looking for the difference that is triggering the error in J39.
The problem is the view attribute definition.
Until J38, it has been ignored by the installer (menu item link index.php?option=com_autotweet).
I think that the attribute has been there since J25 and now it works again adding the view to the menu item link index.php?option=com_autotweet&view=cpanel. The change has been detected by a FOF validation.
I'm removing the view definition from the manifest to regain the previous behaviour and comply with the FOF validation. Since it hasn't been working in J3, the change doesn't affect the rest of the component.
The open question is if the view must be added or not and if it is added what the impact would be.
This is the FOF validation that expects a link without view: https://github.com/joomla/joomla-cms/blob/staging/libraries/fof/utils/installscript/installscript.php#L1776
franz-wohlkoenig
- | Status | New | ⇒ | Discussion |
| Labels |
Added:
J3 Issue
|
||
| Title |
|
||||||
Based in the comments above this should be closed
| Status | Discussion | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-01-04 06:34:04 |
| Closed_By | ⇒ | joomla-cms-bot |
| Closed_By | joomla-cms-bot | ⇒ | alikon |
Set to "closed" on behalf of @alikon by The JTracker Application at issues.joomla.org/joomla-cms/22019
closed
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/22019.
Afaik that menu tag creates the menu in the backend. It would be new to me that it is useless.
Only the "img" attribute is kind of useless since the Protostar menu doesn't show the image. It is shown in the Hathor menu however.
The error seems to come rather from a duplicate menuitem name. Eg COM_XXXX_NAME is also used in a different menu item already.