Forums / Developer / Extension's module/view path vs. node's virtual URLs
Piotrek Karaś
Wednesday 20 February 2008 1:06:44 am
Is there any mechanism in eZ Publish that would prevent from creation of virtual URL that exactly matches existing module/view's URL? It seems to do so for built-in modules, but failed in case of custom extension's module. Let's say I have a ezmyext extension with run view. If I create a node below root node, that is called eZMyEXT, and below that another node called Run, than the extension's module will not be accessible, and node will be displayed instead.
Before I report this as a bug, I would like to ask you guys, maybe there's a setting or detail I'm not aware of.
Thanks
-- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu
André R.
Wednesday 20 February 2008 1:32:44 am
Take a look in settings/module.ini there are some settings for this kind of stuff, esp 'ModuleList[]'
eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription @: http://twitter.com/andrerom
Wednesday 20 February 2008 3:26:57 am
Yup, not a bug, just my ignorance ;)
<i># An array of known modules in the system, extensions should # append to this array. # This is currently used to avoid URL aliases overriding# existing module names</i>
Thanks a lot!