trouble using ezhttp() to get post data when viewing a node

Previous topic

Developer

Next topic

Author	Message
Atle Pedersen	Friday 30 June 2006 9:10:32 am Hi everybody! I'm having trouble using froms to post data to a node view. For test purposes I'm tring the following temnplate when viewing a node: Testname value.:{ezhttp('testname')}:.<br /> <form name="something" method='post' action={$node.url_alias\|ezurl}> <input type="hidden" name="testname" value="testvalue" /> <input type="submit" name="submitbutton" value="submit" /> </form> Why isn't this working? When first loading the page, I get an error saying there's no postdata named testname. After pressing the submit button, there's no more error messages. But there still no data to be fetched by the ezhttp function. Also, if using the get method insted of post, the data is clearly present in the url. But still not accessible using ezhttp('testname','get')
Kristian Hole	Friday 30 June 2006 9:50:20 am This is because the node-view is cached. (ViewCaching=enabled). This is because is should not be needed to regenerate an article (for example) every time it loads. The caching system handles view parameters (on the format /myurl/(myparameter)/myvalue. Where it is available in the template as $view_parameters.myvalue. I know there are extensions for transforming get or post variables to view parameters. I could however not find it right now. Alternatively can you disable the view-cache for your specific template. This is done by adding the following to the template {set-block scope=root variable=cache_ttl}0{/set-block} By turning the viewcache off, the performance will offcourse be decrease. Have a nice weekend :-) Kristian http://ez.no/ez_publish/documenta...tricks/show_which_templates_are_used http://ez.no/doc/ez_publish/techn...te_operators/miscellaneous/attribute
Atle Pedersen	Friday 30 June 2006 10:19:43 am Thank you Kristian. The explanation makes sense, and that set-block hack seems to do the trick. I wish I understood more about the intricacies of the cache system, though.

Author

Message

Atle Pedersen

Friday 30 June 2006 9:10:32 am

Hi everybody!

I'm having trouble using froms to post data to a node view.

For test purposes I'm tring the following temnplate when viewing a node:

Testname value.:{ezhttp('testname')}:.<br />
<form name="something" method='post' action={$node.url_alias|ezurl}>
<input type="hidden" name="testname" value="testvalue" />
<input type="submit" name="submitbutton" value="submit" />
</form>

Why isn't this working?

When first loading the page, I get an error saying there's no postdata named testname. After pressing the submit button, there's no more error messages. But there still no data to be fetched by the ezhttp function.

Also, if using the get method insted of post, the data is clearly present in the url. But still not accessible using ezhttp('testname','get')

Kristian Hole

Friday 30 June 2006 9:50:20 am

This is because the node-view is cached. (ViewCaching=enabled). This is because is should not be needed to regenerate an article (for example) every time it loads.

The caching system handles view parameters (on the format /myurl/(myparameter)/myvalue. Where it is available in the template as $view_parameters.myvalue. I know there are extensions for transforming get or post variables to view parameters. I could however not find it right now.

Alternatively can you disable the view-cache for your specific template. This is done by adding the following to the template

{set-block scope=root variable=cache_ttl}0{/set-block}

By turning the viewcache off, the performance will offcourse be decrease.

Have a nice weekend :-)

Kristian

http://ez.no/ez_publish/documenta...tricks/show_which_templates_are_used
http://ez.no/doc/ez_publish/techn...te_operators/miscellaneous/attribute

Atle Pedersen

Friday 30 June 2006 10:19:43 am

Thank you Kristian. The explanation makes sense, and that set-block hack seems to do the trick.

I wish I understood more about the intricacies of the cache system, though.

eZ debug

Timing:	Jan 31 2025 01:35:36
Script start
Timing:	Jan 31 2025 01:35:36
Module start 'layout'
Timing:	Jan 31 2025 01:35:36
Module start 'content'
Timing:	Jan 31 2025 01:35:36
Module end 'content'
Timing:	Jan 31 2025 01:35:36
Script end

Main resources:

Total runtime	0.0256 sec
Peak memory usage	8,192.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0076	588.3906	151.2422
Module start 'layout'	0.0076	0.0041	739.6328	220.7500
Module start 'content'	0.0117	0.0123	960.3828	1,001.8984
Module end 'content'	0.0240	0.0016	1,962.2813	33.9922
Script end	0.0256		1,996.2734

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0028	10.7718	14	0.0002
Check MTime	0.0011	4.3147	14	0.0001
Mysql Total
Database connection	0.0015	5.6924	1	0.0015
Mysqli_queries	0.0032	12.4355	3	0.0011
Looping result	0.0000	0.0466	1	0.0000
Template Total	0.0011	4.4	1	0.0011
Template load	0.0009	3.4736	1	0.0009
Template processing	0.0002	0.9417	1	0.0002
Override
Cache load	0.0006	2.5318	1	0.0006
General
dbfile	0.0003	1.3115	8	0.0000
String conversion	0.0000	0.0354	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