Siteaccess specific template overrides for extensions

Previous topic

Developer

Next topic

Author	Message
Eirik Alfstad Johansen	Tuesday 23 November 2004 3:14:51 am Hi, I'm creating an extension which, among other things, creates a couple of new classes. For these classes, I've created override templates in full and line view, and then created an override.ini.append.php in extension/extname/settings in order for them to be applied, which they are. The only problem is that the admin siteaccess templates are also overriden. I tried solving the problem by moving the override.ini file to extension/extname/settings/siteaccess/usersiteaccess but then the overrides were ignored alltogether. Is there any way around this problem? Thanks in advance ! Sincerely, Eirik Alfstad Johansen http://www.netmaking.no/
Lazaro Ferreira	Tuesday 23 November 2004 4:05:25 am Hi, We have had a similar problem, that is reported here : http://ez.no/community/bug_reports/extension_with_settings_override_ini_append_breaks_ezp_override_system Our workaround was to remove the override.ini.append.php for the extension, and override directly under settings/siteaccess Lazaro http://www.mzbusiness.com
Hans Melis	Tuesday 23 November 2004 5:48:26 am Just an idea here... It's quite logical that an override.ini.append in an extension is applied to <b>all</b> siteaccesses. The regular way of activating extensions (ActiveExtensions in the global site.ini.append) implies that behaviour. But what if such an extension is only activated for selected siteaccesses? There is a setting in site.ini: [ExtensionSettings] ActiveAccessExtensions[] If you put that in the site.ini.append of a siteaccess, then the extension is only loaded if that siteaccess is wanted/needed (at least that's how I think it works). If the extensions is siteaccess specific, all its settings could be siteaccess specific too (the extension's override.ini.append would be added to the siteaccess' override settings). I've never tried this though, so I'm not sure if this will work or if this is what you need... Hans http://blog.hansmelis.be

Author

Message

Eirik Alfstad Johansen

Tuesday 23 November 2004 3:14:51 am

Hi,

I'm creating an extension which, among other things, creates a couple of new classes. For these classes, I've created override templates in full and line view, and then created an override.ini.append.php in extension/extname/settings in order for them to be applied, which they are.

The only problem is that the admin siteaccess templates are also overriden. I tried solving the problem by moving the override.ini file to extension/extname/settings/siteaccess/usersiteaccess but then the overrides were ignored alltogether.

Is there any way around this problem? Thanks in advance !

Sincerely,

Eirik Alfstad Johansen
http://www.netmaking.no/

Lazaro Ferreira

Tuesday 23 November 2004 4:05:25 am

Hi,

We have had a similar problem, that is reported here :

http://ez.no/community/bug_reports/extension_with_settings_override_ini_append_breaks_ezp_override_system

Our workaround was to remove the override.ini.append.php for the extension, and override directly under settings/siteaccess

Lazaro
http://www.mzbusiness.com

Hans Melis

Tuesday 23 November 2004 5:48:26 am

Just an idea here...

It's quite logical that an override.ini.append in an extension is applied to <b>all</b> siteaccesses. The regular way of activating extensions (ActiveExtensions in the global site.ini.append) implies that behaviour.

But what if such an extension is only activated for selected siteaccesses? There is a setting in site.ini:

[ExtensionSettings]
ActiveAccessExtensions[]

If you put that in the site.ini.append of a siteaccess, then the extension is only loaded if that siteaccess is wanted/needed (at least that's how I think it works).

If the extensions is siteaccess specific, all its settings could be siteaccess specific too (the extension's override.ini.append would be added to the siteaccess' override settings).

I've never tried this though, so I'm not sure if this will work or if this is what you need...

Hans
http://blog.hansmelis.be

eZ debug

Timing:	Jan 19 2025 03:41:39
Script start
Timing:	Jan 19 2025 03:41:39
Module start 'layout'
Timing:	Jan 19 2025 03:41:39
Module start 'content'
Timing:	Jan 19 2025 03:41:41
Module end 'content'
Timing:	Jan 19 2025 03:41:41
Script end

Main resources:

Total runtime	1.8275 sec
Peak memory usage	4,096.0000 KB
Database Queries	59

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0111	589.3828	152.6406
Module start 'layout'	0.0111	0.0063	742.0234	39.4766
Module start 'content'	0.0174	1.8085	781.5000	572.1719
Module end 'content'	1.8259	0.0015	1,353.6719	12.1250
Script end	1.8274		1,365.7969

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0043	0.2332	16	0.0003
Check MTime	0.0015	0.0846	16	0.0001
Mysql Total
Database connection	0.0035	0.1916	1	0.0035
Mysqli_queries	1.7630	96.4733	59	0.0299
Looping result	0.0008	0.0441	57	0.0000
Template Total	1.7662	96.6	2	0.8831
Template load	0.0022	0.1180	2	0.0011
Template processing	1.7640	96.5286	2	0.8820
Template load and register function	0.0001	0.0071	1	0.0001
states
state_id_array	0.0012	0.0630	1	0.0012
state_identifier_array	0.0031	0.1689	2	0.0015
Override
Cache load	0.0018	0.0977	22	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0006	0.0335	3	0.0002
Fetch class attribute name	0.0014	0.0761	5	0.0003
XML
Image XML parsing	0.0014	0.0788	3	0.0005
class_abstraction
Instantiating content class attribute	0.0000	0.0005	5	0.0000
General
dbfile	0.0016	0.0888	21	0.0001
String conversion	0.0000	0.0008	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
2	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
4	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezxmltags/literal.tpl	<No override>	extension/community/design/standard/templates/content/datatype/view/ezxmltags/literal.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 12 Number of unique templates used: 6

Time used to render debug report: 0.0002 secs