e-commerce site (tasks to do after buying)

Previous topic

Developer

Next topic

Author	Message
Jorge estévez	Saturday 30 April 2005 2:10:22 pm I am developing an e-commerce site with ver: 3.5.2 When a user buys a product I would like to do the following: 1. Change the user from group XXX (with roles) to group YYY (other rules) 2. Create a structure within folder CLIENTS with the following in it: CLIENTS --New Client Folder (create) ----Forum for technical support (create) ----Folder for articles (create) 3. Create a group (whith roles to access his new structure) 4. Asign to the new client the group above I dont now if I make myself clear, once a client buys a product he will be member of group "CLIENT" so I will have to move him from a simple subscribed person to the CLIENT's group, he will also have support for the product he bought that's why I need to create the structure to be used only by that client and add roles to access that part of the site. To be able to buy at the site he has already been at the subscription form, so with his login/pass he must also be able to access the newly created structure. Please if someone will explain "How To" try to explain in details. I asume workflow will be the way to go... Thanks Diseño Web Cuba Web Design Cuba www.elfosdesign.com

Author

Message

Jorge estévez

Saturday 30 April 2005 2:10:22 pm

I am developing an e-commerce site with ver: 3.5.2

When a user buys a product I would like to do the following:

1. Change the user from group XXX (with roles) to group YYY (other rules)
2. Create a structure within folder CLIENTS with the following in it:

CLIENTS
--New Client Folder (create)
----Forum for technical support (create)
----Folder for articles (create)

3. Create a group (whith roles to access his new structure)
4. Asign to the new client the group above

I dont now if I make myself clear, once a client buys a product he will be member of group "CLIENT" so I will have to move him from a simple subscribed person to the CLIENT's group, he will also have support for the product he bought that's why I need to create the structure to be used only by that client and add roles to access that part of the site.

To be able to buy at the site he has already been at the subscription form, so with his login/pass he must also be able to access the newly created structure.

Please if someone will explain "How To" try to explain in details. I asume workflow will be the way to go...

Thanks

Diseño Web Cuba
Web Design Cuba
www.elfosdesign.com

eZ debug

Timing:	Jan 31 2025 05:59:47
Script start
Timing:	Jan 31 2025 05:59:47
Module start 'layout'
Timing:	Jan 31 2025 05:59:47
Module start 'content'
Timing:	Jan 31 2025 05:59:47
Module end 'content'
Timing:	Jan 31 2025 05:59:47
Script end

Main resources:

Total runtime	0.0161 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.0055	588.2656	151.2266
Module start 'layout'	0.0055	0.0024	739.4922	36.6797
Module start 'content'	0.0079	0.0067	776.1719	90.0781
Module end 'content'	0.0147	0.0014	866.2500	29.9922
Script end	0.0161		896.2422

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0024	14.6427	14	0.0002
Check MTime	0.0010	6.4792	14	0.0001
Mysql Total
Database connection	0.0010	6.1326	1	0.0010
Mysqli_queries	0.0022	13.3643	3	0.0007
Looping result	0.0000	0.0681	1	0.0000
Template Total	0.0011	6.7	1	0.0011
Template load	0.0008	4.8157	1	0.0008
Template processing	0.0003	1.8457	1	0.0003
Override
Cache load	0.0005	3.1567	1	0.0005
General
dbfile	0.0025	15.7433	8	0.0003
String conversion	0.0000	0.0489	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