Building a shop

Next topic

Author	Message
Bjørn Kaarstein	Friday 16 April 2004 6:33:01 am I've recently upgraded a site from 3.1 to 3.3, and am currently in the planning stage of adding webshop functionality. I could use some help to get started. Currently this site runs in element view. It's only a given part of the site which is supposed to be a part of a shop. I'll keep the design as is, and what I want to do is just to add a "buy" button to the full view of one specific product class. Is this possible to do with element view, or will I have to put this in a section of its own using {$module_result.content} to display? I'm a bit confused right now, so any clearifying answer will be greatly appreciated. Regards Bjørn
Silke Fox	Sunday 18 April 2004 11:50:24 pm The "add to basket" button should show up automatically in the full view of a product object (at least in the standard templates). You can test that with the default product content class or, if you want to set up your own product class, just add the "price" attribute to it. You don't need a new section for that. Products work like any other content object, so template overriding and so on is basically the same as with other content. Maybe this is a little hint to start with. Silke

Author

Message

Friday 16 April 2004 6:33:01 am

I've recently upgraded a site from 3.1 to 3.3, and am currently in the planning stage of adding webshop functionality. I could use some help to get started.

Currently this site runs in element view.

It's only a given part of the site which is supposed to be a part of a shop. I'll keep the design as is, and what I want to do is just to add a "buy" button to the full view of one specific product class. Is this possible to do with element view, or will I have to put this in a section of its own using {$module_result.content} to display?

I'm a bit confused right now, so any clearifying answer will be greatly appreciated.

Regards Bjørn

Silke Fox

Sunday 18 April 2004 11:50:24 pm

The "add to basket" button should show up automatically in the full view of a product object (at least in the standard templates).
You can test that with the default product content class or, if you want to set up your own product class, just add the "price" attribute to it.

You don't need a new section for that.
Products work like any other content object, so template overriding and so on
is basically the same as with other content.

Maybe this is a little hint to start with.

Silke

eZ debug

Timing:	Jan 19 2025 14:04:14
Script start
Timing:	Jan 19 2025 14:04:14
Module start 'layout'
Timing:	Jan 19 2025 14:04:14
Module start 'content'
Timing:	Jan 19 2025 14:04:14
Module end 'content'
Timing:	Jan 19 2025 14:04:14
Script end

Main resources:

Total runtime	0.0142 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.0049	589.0313	152.6094
Module start 'layout'	0.0049	0.0020	741.6406	39.4297
Module start 'content'	0.0069	0.0054	781.0703	89.1797
Module end 'content'	0.0123	0.0019	870.2500	30.3047
Script end	0.0141		900.5547

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0022	15.6507	14	0.0002
Check MTime	0.0010	6.9248	14	0.0001
Mysql Total
Database connection	0.0006	4.3722	1	0.0006
Mysqli_queries	0.0019	13.5571	3	0.0006
Looping result	0.0000	0.0555	1	0.0000
Template Total	0.0016	11.1	1	0.0016
Template load	0.0008	5.8823	1	0.0008
Template processing	0.0007	5.1423	1	0.0007
Override
Cache load	0.0005	3.5684	1	0.0005
General
dbfile	0.0010	7.3099	8	0.0001
String conversion	0.0000	0.0353	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