Orders not deleted

Next topic

Author	Message
Oliver Frommel	Thursday 26 November 2009 5:33:41 am Hi there, I am trying to process some orders in the shop, for instance make use of the data_text_2 field and using custom status values. Everything works fine so far, but in the processs I discovered that orders don't really get deleted. That means they don't show up in the admin view of the shop, neither as active nor archived, but they do in order list of the logged-in user and when I list them in a template. How can I get rid of them? Best Oliver
Benjamin Selmer	Wednesday 02 December 2009 4:24:49 am Pressing the delete button in /shop/orderview/xx actually deletes the entry from the ezorder table in the database. If the order still shows up in the customer order view it is probably a caching problem. In a business and accounting sense it is not a good thing to delete orders. I would make a custom status called cancelled for the orders that aren't going to be delivered for some reason.

Author

Message

Thursday 26 November 2009 5:33:41 am

Hi there,

I am trying to process some orders in the shop, for instance make use of the data_text_2 field and using custom status values. Everything works fine so far, but in the processs I discovered that orders don't really get deleted. That means they don't show up in the admin view of the shop, neither as active nor archived, but they do in order list of the logged-in user and when I list them in a template. How can I get rid of them?

Best

Oliver

Benjamin Selmer

Wednesday 02 December 2009 4:24:49 am

Pressing the delete button in /shop/orderview/xx actually deletes the entry from the ezorder table in the database.

If the order still shows up in the customer order view it is probably a caching problem.

In a business and accounting sense it is not a good thing to delete orders. I would make a custom status called cancelled for the orders that aren't going to be delivered for some reason.

eZ debug

Timing:	Jan 30 2025 00:13:18
Script start
Timing:	Jan 30 2025 00:13:18
Module start 'layout'
Timing:	Jan 30 2025 00:13:18
Module start 'content'
Timing:	Jan 30 2025 00:13:18
Module end 'content'
Timing:	Jan 30 2025 00:13:18
Script end

Main resources:

Total runtime	0.0120 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	588.0156	151.1953
Module start 'layout'	0.0047	0.0027	739.2109	36.6328
Module start 'content'	0.0074	0.0034	775.8438	90.0313
Module end 'content'	0.0108	0.0012	865.8750	29.9922
Script end	0.0120		895.8672

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0022	18.0892	14	0.0002
Check MTime	0.0010	8.6090	14	0.0001
Mysql Total
Database connection	0.0007	6.0490	1	0.0007
Mysqli_queries	0.0024	19.8337	3	0.0008
Looping result	0.0000	0.1253	1	0.0000
Template Total	0.0009	7.6	1	0.0009
Template load	0.0007	5.7486	1	0.0007
Template processing	0.0002	1.8280	1	0.0002
Override
Cache load	0.0005	3.8808	1	0.0005
General
dbfile	0.0002	1.9116	8	0.0000
String conversion	0.0000	0.0418	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