Relating order with collected info

Previous topic

Setup & design

Next topic

Author	Message
Felix Laate	Tuesday 13 September 2005 5:40:42 am Hi all! I have a product where I need to let the user set an arbitrary text which is used in the production of the product. As there is noe "textline'ish" datatype which can be plugged into the webshop, I made an text_line sttribute which is information collecting. This works allright. The text is uploaded. But I need to relate the two (the bought product and the uploaded text). Any ideas would make a difference ! Felix Publlic Relations Manager Greater Stavanger www.greaterstavanger.com
Felix Laate	Monday 19 September 2005 2:40:14 am Hi again! I couldn't figure this one (either) out, so I use the comment field in the registration for gathering this kind of info. This is not at all a good solution.. but it works. All in all my first experience with the ez-webshop has been exciting but time-consuming. In my head I have a wish-list that I might post to the developer-section of the forum. Felix Publlic Relations Manager Greater Stavanger www.greaterstavanger.com

Author

Message

Felix Laate

Tuesday 13 September 2005 5:40:42 am

Hi all!

I have a product where I need to let the user set an arbitrary text which is used in the production of the product.

As there is noe "textline'ish" datatype which can be plugged into the webshop, I made an text_line sttribute which is information collecting.

This works allright. The text is uploaded.

But I need to relate the two (the bought product and the uploaded text).

Any ideas would make a difference !

Felix

Publlic Relations Manager
Greater Stavanger
www.greaterstavanger.com

Felix Laate

Monday 19 September 2005 2:40:14 am

Hi again!

I couldn't figure this one (either) out, so I use the comment field in the registration for gathering this kind of info.

This is not at all a good solution.. but it works.

All in all my first experience with the ez-webshop has been exciting but time-consuming. In my head I have a wish-list that I might post to the developer-section of the forum.

Felix

Publlic Relations Manager
Greater Stavanger
www.greaterstavanger.com

eZ debug

Timing:	Jan 19 2025 09:54:16
Script start
Timing:	Jan 19 2025 09:54:16
Module start 'layout'
Timing:	Jan 19 2025 09:54:16
Module start 'content'
Timing:	Jan 19 2025 09:54:16
Module end 'content'
Timing:	Jan 19 2025 09:54:16
Script end

Main resources:

Total runtime	0.0215 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.0047	590.5313	152.6250
Module start 'layout'	0.0047	0.0033	743.1563	39.4453
Module start 'content'	0.0080	0.0112	782.6016	89.2422
Module end 'content'	0.0192	0.0023	871.8438	30.3047
Script end	0.0215		902.1484

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0023	10.9320	14	0.0002
Check MTime	0.0011	5.1133	14	0.0001
Mysql Total
Database connection	0.0006	2.8328	1	0.0006
Mysqli_queries	0.0027	12.6812	3	0.0009
Looping result	0.0000	0.1120	1	0.0000
Template Total	0.0017	7.9	1	0.0017
Template load	0.0009	4.3025	1	0.0009
Template processing	0.0008	3.5305	1	0.0008
Override
Cache load	0.0007	3.0425	1	0.0007
General
dbfile	0.0026	12.2597	8	0.0003
String conversion	0.0000	0.0355	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