Wrong entity module name

[michalcharvat]

I have fixed displaying modules in settings (6.5.x branch) where are two modules with the same name in different packages. However looks like there are other issues like

• how to defne module id - package-module -> it will define route #package-name so question is also how to define module route when there could be module with same id but different package.
• entity detail route
• load correctly detail by route + open correct module

@mschering any ideas? Do you have any plans to solve this issue? Currently it is unreal count with there will be always module with different name especially when there is Studio

[derjoachim]

especially when there is Studio

Studio has a safety built in for this kind of situation. See the screen shots below.

When trying to duplicate a module name:

When trying to duplicate an entitiy name:

[michalcharvat]

When trying to duplicate a module name:

I guess it is wrong when you display error message for module name which does not exists inside studio folder. Of course it is correct for now (when you simply cannot solve the problem with "namespaces") however from global scope it is wrong because the module with provided name does not exists in studio grid. It is misleading. Also it does not make sense to split modules to packages and then stricly say you cannot create new module because it already exists in package xyz :)

When trying to duplicate an entitiy name:

I would like to know how do you want duplicate entity across different packages - simply you shouldnt. Thats why there is a alias. Technically the entity alias could be generated automatically joining package and entity name but currently this problem is solvable by alias. Strange you dont use it in Studio when the alias is your idea :) Sure you have to check it entity does not exists in core_enttiy table but still you should be able generate unique entity name especially when you offer Studio module to brain free users :P

I already have modules with same name but different package. Strictly because people requested things with different functionality and you cannot call the module Dog when it is a Cat :D Of course you can also create huge module with different functionality hundreds of options and entities but it will bring unwanted compexity. Also call module with prefix company when it is already split by package is also strange - but yes it does solve the problem for now. From my point of view there is a bug in architecture.