Forums / Suggestions / Reconstructing eZOption datatype

"Please Note:

At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

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