How do I use the customObjectAttributeHTTPAction to run a custom action from a new datatype as an extension.

Previous topic

Developer

Next topic

Author	Message
Stuart Fenton	Friday 12 November 2004 2:46:28 am I have written some code to run under customObjectAttributeHTTPAction but I am unsure how to get it to run. The code will be used from the user side of the site not the admin side and it will get used to calculate the price of an item prior to it being added to the basket. It's a simple "Update Prices" button that calculates all the options added before adding it to the basket. Is there a setting I am suppose to add to the ini files? I know I can create a custom action using code stored in actions/content_actionhandler.php but I would rather it was self contained in the object itself. I know that I can add code to the "content.ini.append.php" stored in the exntention settings like: [ActionSettings] ExtensionDirectories[]=ezcalculateoption But that is outside of the object itself. How do I do this? Any ideas. Any help is greatly appreciated. -- Stuart stuart@grandmore.com http://www.grandmore.com

Author

Message

Stuart Fenton

Friday 12 November 2004 2:46:28 am

I have written some code to run under customObjectAttributeHTTPAction but I am unsure how to get it to run.

The code will be used from the user side of the site not the admin side and it will get used to calculate the price of an item prior to it being added to the basket. It's a simple "Update Prices" button that calculates all the options added before adding it to the basket.

Is there a setting I am suppose to add to the ini files?

I know I can create a custom action using code stored in actions/content_actionhandler.php but I would rather it was self contained in the object itself.

I know that I can add code to the "content.ini.append.php" stored in the exntention settings like:

[ActionSettings]
ExtensionDirectories[]=ezcalculateoption

But that is outside of the object itself.

How do I do this? Any ideas.

Any help is greatly appreciated.

-- Stuart

stuart@grandmore.com
http://www.grandmore.com

eZ debug

Timing:	Jan 31 2025 04:29:25
Script start
Timing:	Jan 31 2025 04:29:25
Module start 'layout'
Timing:	Jan 31 2025 04:29:25
Module start 'content'
Timing:	Jan 31 2025 04:29:25
Module end 'content'
Timing:	Jan 31 2025 04:29:25
Script end

Main resources:

Total runtime	0.0150 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.0051	588.8906	151.3047
Module start 'layout'	0.0051	0.0029	740.1953	36.7891
Module start 'content'	0.0080	0.0055	776.9844	90.3438
Module end 'content'	0.0135	0.0014	867.3281	29.9922
Script end	0.0149		897.3203

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0023	15.6466	14	0.0002
Check MTime	0.0011	7.0374	14	0.0001
Mysql Total
Database connection	0.0009	6.2523	1	0.0009
Mysqli_queries	0.0025	16.4859	3	0.0008
Looping result	0.0000	0.0876	1	0.0000
Template Total	0.0010	6.9	1	0.0010
Template load	0.0008	5.3637	1	0.0008
Template processing	0.0002	1.4970	1	0.0002
Override
Cache load	0.0006	3.7743	1	0.0006
General
dbfile	0.0014	9.0456	8	0.0002
String conversion	0.0000	0.1194	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