[florianwalter]

Hi all,

in our application we want addon-modules to carry their backend inside of a nested-module.
So every addon-module with a backend would have a module called 'backend'.

addonModule1
	controllers
	modules
		backend
			controllers
			views
	views
addonModule2
	controllers
	modules
		backend
			controllers
			views
	views

In the documentation is written: "A module is organized as a directory whose name serves as its unique ID."
We tried it anyhow and it seems to work, even though there are multiple modules called 'backend'.

Does anybody know about any side-effects, when having multiple modules with the same name?
Or isn't the unique ID mandatory for nested modules?

Thanks, Florian.

[Mike]

One side effect you should be aware of:

Quote

Additionally, if the application uses modules, a root alias is also predefined for each module ID and refers to the base path of the corresponding module. This feature has been available since version 1.0.3.

So you will probably not be able to use any root alias defined for your modules.

[Junior - df9]

florianwalter, on 16 June 2010 - 12:43 PM, said:

Hi all,

in our application we want addon-modules to carry their backend inside of a nested-module.
So every addon-module with a backend would have a module called 'backend'.

addonModule1
	controllers
	modules
		backend
			controllers
			views
	views
addonModule2
	controllers
	modules
		backend
			controllers
			views
	views

In the documentation is written: "A module is organized as a directory whose name serves as its unique ID."
We tried it anyhow and it seems to work, even though there are multiple modules called 'backend'.

Does anybody know about any side-effects, when having multiple modules with the same name?
Or isn't the unique ID mandatory for nested modules?

Thanks, Florian.

I've been using exactly the same structure you mentioned in a little cms and have no issues till now.

I think this is a good and flexible structure because you can easily include and exclude modules for your clients' projects depending on their needs. Also, I've created a theme called "Backend", which is shared by backend submodules and created widgets in modules for flexibiliby in the frontend

It's not finished yet, but it has been working fine

regards!