How-to avoid double post into custom modules

Previous topic

Developer

Next topic

Author	Message
Sébastien Antoniotti	Monday 14 December 2009 2:02:10 am Hi, I have a custom module who creates eZ objects based on post data. After the publication made by the module, I would like to redirect the user to some view and disable the possibility to re-post the form (with F5 by example). The problem is that $module->redirect... does the redirection but post data are still here. I think a header redirection can do the job but I haven't found how to redirect properly to a custom module/view... any ideas ? eZ Publish Freelance web : http://www.webaxis.fr
Łukasz Serwatka	Monday 14 December 2009 2:19:01 am Hi, There are few possibilities. Easiest will be set session variable after object was created and check it before. Or set a remote_id for created object which will be a hash included in the POST array and check if object exists with such remote_id if so then you skip creation process. Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog
Sébastien Antoniotti	Monday 14 December 2009 2:47:23 am Thanks Lukasz for the advice ! Meanwhile I found the following solution which is to redirect in 301 on the confirmation page. In this way, post data no longer exist. // redirect eZHTTPTool::redirect( eZSys::indexDir().'/member/mywallet', array(), 301 ); eZExecution::cleanExit(); Cheers, Seb eZ Publish Freelance web : http://www.webaxis.fr

Author

Message

Sébastien Antoniotti

Monday 14 December 2009 2:02:10 am

Hi,

I have a custom module who creates eZ objects based on post data.

After the publication made by the module, I would like to redirect the user to some view and disable the possibility to re-post the form (with F5 by example).

The problem is that $module->redirect... does the redirection but post data are still here.

I think a header redirection can do the job but I haven't found how to redirect properly to a custom module/view...

any ideas ?

eZ Publish Freelance
web : http://www.webaxis.fr

Łukasz Serwatka

Monday 14 December 2009 2:19:01 am

Hi,

There are few possibilities. Easiest will be set session variable after object was created and check it before. Or set a remote_id for created object which will be a hash included in the POST array and check if object exists with such remote_id if so then you skip creation process.

Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog

Sébastien Antoniotti

Monday 14 December 2009 2:47:23 am

Thanks Lukasz for the advice !

Meanwhile I found the following solution which is to redirect in 301 on the confirmation page.

In this way, post data no longer exist.

// redirect
eZHTTPTool::redirect( eZSys::indexDir().'/member/mywallet', array(), 301 );
eZExecution::cleanExit();

Cheers,

Seb

eZ Publish Freelance
web : http://www.webaxis.fr

eZ debug

Timing:	Jan 29 2025 13:31:32
Script start
Timing:	Jan 29 2025 13:31:32
Module start 'layout'
Timing:	Jan 29 2025 13:31:32
Module start 'content'
Timing:	Jan 29 2025 13:31:32
Module end 'content'
Timing:	Jan 29 2025 13:31:32
Script end

Main resources:

Total runtime	0.0140 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.2656	151.2266
Module start 'layout'	0.0051	0.0029	739.4922	36.6797
Module start 'content'	0.0080	0.0045	776.1719	90.1875
Module end 'content'	0.0125	0.0014	866.3594	33.9922
Script end	0.0139		900.3516

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0024	17.3209	14	0.0002
Check MTime	0.0011	7.5468	14	0.0001
Mysql Total
Database connection	0.0006	4.6165	1	0.0006
Mysqli_queries	0.0025	17.9967	3	0.0008
Looping result	0.0000	0.1143	1	0.0000
Template Total	0.0011	7.8	1	0.0011
Template load	0.0008	5.8487	1	0.0008
Template processing	0.0003	1.9251	1	0.0003
Override
Cache load	0.0006	4.1301	1	0.0006
General
dbfile	0.0002	1.6111	8	0.0000
String conversion	0.0000	0.0580	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