Partial delivery in the shop

Next topic

Author	Message
Piotr Switkowski	Sunday 26 November 2006 10:23:27 am I am just working of the e-shop for bookstore. I realized that some orders cannot be fully delivered: eq. one of ordered books is not in store. As clients might order books that are announced but not yet published, this situation is quite common. In such situation there should be mechanism to allow admin to edit the order, eq. and split it to 2 orders or move some items to wishlist. However, in ezPublish orders could hardly be edited. Do you have any suggestions how to handle such situation. Or what is the best way to customise ezPublish?
Pascal Specht	Thursday 05 July 2007 3:29:07 am Hi Piotr, unfortunately, I've no answer to your request, but was wondering if by the time you did solve your problem, and how? I'm typically searching for a similar solution: customers may want to "pre-buy" (reserve) some products that are announced but not yet available: The shop owner should see these orders in the back-office and keep the orders on hold until they are possible. Have you used the existing shopping mechanisms and some overrides, or did you have to modify the source code to get to your objective? Thanks for any suggestions, Pascal

Author

Message

Sunday 26 November 2006 10:23:27 am

I am just working of the e-shop for bookstore. I realized that some orders cannot be fully delivered: eq. one of ordered books is not in store. As clients might order books that are announced but not yet published, this situation is quite common. In such situation there should be mechanism to allow admin to edit the order, eq. and split it to 2 orders or move some items to wishlist. However, in ezPublish orders could hardly be edited.

Do you have any suggestions how to handle such situation. Or what is the best way to customise ezPublish?

Pascal Specht

Thursday 05 July 2007 3:29:07 am

Hi Piotr,

unfortunately, I've no answer to your request, but was wondering if by the time you did solve your problem, and how?

I'm typically searching for a similar solution: customers may want to "pre-buy" (reserve) some products that are announced but not yet available: The shop owner should see these orders in the back-office and keep the orders on hold until they are possible.

Have you used the existing shopping mechanisms and some overrides, or did you have to modify the source code to get to your objective?

Thanks for any suggestions,
Pascal

eZ debug

Timing:	Jan 31 2025 00:30:34
Script start
Timing:	Jan 31 2025 00:30:34
Module start 'layout'
Timing:	Jan 31 2025 00:30:34
Module start 'content'
Timing:	Jan 31 2025 00:30:34
Module end 'content'
Timing:	Jan 31 2025 00:30:34
Script end

Main resources:

Total runtime	0.0216 sec
Peak memory usage	6,144.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0045	588.1328	151.2109
Module start 'layout'	0.0045	0.0033	739.3438	220.6875
Module start 'content'	0.0079	0.0125	960.0313	997.7891
Module end 'content'	0.0203	0.0013	1,957.8203	29.9922
Script end	0.0216		1,987.8125

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0024	11.1291	14	0.0002
Check MTime	0.0010	4.5182	14	0.0001
Mysql Total
Database connection	0.0007	3.1297	1	0.0007
Mysqli_queries	0.0020	9.2733	3	0.0007
Looping result	0.0000	0.0463	1	0.0000
Template Total	0.0009	4.3	1	0.0009
Template load	0.0008	3.4768	1	0.0008
Template processing	0.0002	0.8320	1	0.0002
Override
Cache load	0.0005	2.4586	1	0.0005
General
dbfile	0.0014	6.6274	8	0.0002
String conversion	0.0000	0.0242	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