Reconstructing eZOption datatype

Previous topic

Suggestions

Next topic

Author	Message
H-Works Agency	Friday 18 May 2007 5:56:42 am Hi all, After working a lot with the ezoption datatype i think its too rigid to cover product options problematics. In fact its attributes (value, additional_price), hard coded in kernel functions, poses a lot of problem when real cases appears. I think that attributes should be manageable in a way or another, without having to code a new datatype. Maybe through ini settings (in datatype.ini) or directly inside ezOption edit view. Even if each attribute datatype is for now text fields only. This would solve a lot of issues by allowing administrators to set each option's attributes. For example : [quantity, reference, price] or [reference, quantity, size]...etc EZP is Great

Author

Message

H-Works Agency

Friday 18 May 2007 5:56:42 am

Hi all,

After working a lot with the ezoption datatype i think its too rigid to cover product options problematics.

In fact its attributes (value, additional_price), hard coded in kernel functions, poses a lot of problem when real cases appears.

I think that attributes should be manageable in a way or another, without having to code a new datatype. Maybe through ini settings (in datatype.ini) or directly inside ezOption edit view.

Even if each attribute datatype is for now text fields only.

This would solve a lot of issues by allowing administrators to set each option's attributes.

For example : [quantity, reference, price] or [reference, quantity, size]...etc

EZP is Great

eZ debug

Timing:	Jan 18 2025 11:14:28
Script start
Timing:	Jan 18 2025 11:14:28
Module start 'layout'
Timing:	Jan 18 2025 11:14:28
Module start 'content'
Timing:	Jan 18 2025 11:14:28
Module end 'content'
Timing:	Jan 18 2025 11:14:28
Script end

Main resources:

Total runtime	0.0132 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0057	587.9219	152.6250
Module start 'layout'	0.0058	0.0026	740.5469	39.4609
Module start 'content'	0.0083	0.0032	780.0078	85.2422
Module end 'content'	0.0115	0.0017	865.2500	30.3047
Script end	0.0132		895.5547

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0022	16.7782	14	0.0002
Check MTime	0.0010	7.3678	14	0.0001
Mysql Total
Database connection	0.0005	3.7451	1	0.0005
Mysqli_queries	0.0031	23.3164	3	0.0010
Looping result	0.0000	0.1278	1	0.0000
Template Total	0.0014	10.6	1	0.0014
Template load	0.0007	5.6077	1	0.0007
Template processing	0.0007	5.0031	1	0.0007
Override
Cache load	0.0005	4.0006	1	0.0005
General
dbfile	0.0002	1.7115	8	0.0000
String conversion	0.0000	0.0594	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	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs