Extension's module/view path vs. node's virtual URLs

Author Message

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

Piotrek Karaś

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!

--
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

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 31 2025 05:58:23
Script start
Timing: Jan 31 2025 05:58:23
Module start 'layout'
Timing: Jan 31 2025 05:58:23
Module start 'content'
Timing: Jan 31 2025 05:58:23
Module end 'content'
Timing: Jan 31 2025 05:58:23
Script end

Main resources:

Total runtime0.0167 sec
Peak memory usage2,048.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0054 588.2813151.2266
Module start 'layout' 0.00540.0026 739.507836.6797
Module start 'content' 0.00810.0072 776.187594.1875
Module end 'content' 0.01530.0014 870.375033.9922
Script end 0.0167  904.3672 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002514.8234140.0002
Check MTime0.00116.6836140.0001
Mysql Total
Database connection0.00084.893610.0008
Mysqli_queries0.002515.158630.0008
Looping result0.00000.065610.0000
Template Total0.00116.810.0011
Template load0.00085.084710.0008
Template processing0.00031.638810.0003
Override
Cache load0.00063.427410.0006
General
dbfile0.002917.144080.0004
String conversion0.00000.041440.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs