ActionRemove redirect

Author Message

Clemens T

Monday 07 January 2008 1:43:50 am

Hello all,

I'd like to know how to redirect the end-user after he removes an object. I'd like to redirect the user to another node (which I know before removal). RedirectURIAfterPublish and RedirectURI don't seem to work here.

Thanks!!
Clemens

Heath

Monday 07 January 2008 2:37:23 am

Hello again Clemens,

I don't think this feature exists yet in eZ Publish.

I think you may find the results you seek with the creation of a custom module view ie: /redirectdelete/delete) which uses the stock delete code to remove the node and then provides in addition a custom redirect.

Cheers,
Heath

Brookins Consulting | http://brookinsconsulting.com/
Certified | http://auth.ez.no/certification/verify/380350
Solutions | http://projects.ez.no/users/community/brookins_consulting
eZpedia community documentation project | http://ezpedia.org

Clemens T

Monday 07 January 2008 3:53:44 am

Heya Heath,

Thanks for the quick response!

Do you mean I need to create an extension with a module and a view which has custom PHP code (which uses the eZPublish base code) or will a template override do? Could you provide a little more detail please?

Thanks again!!
Clemens

Heath

Monday 07 January 2008 4:51:27 am

Your welcome Clemens,

<i> > Do you mean I need to create an extension with a module and a view which has custom PHP code (which uses the eZPublish base code) or will a template override do? </i>

Yes I am recommending the creation of an extension module view as you describe. Nor I do not think a template override can solve your concern.

Cheers,
Heath

Brookins Consulting | http://brookinsconsulting.com/
Certified | http://auth.ez.no/certification/verify/380350
Solutions | http://projects.ez.no/users/community/brookins_consulting
eZpedia community documentation project | http://ezpedia.org

Clemens T

Monday 07 January 2008 5:37:17 am

Ok, got ya! thx again

Chad Paulson

Friday 11 January 2008 1:50:32 pm

Correct me if I'm wrong, but what about creating a custom edit handler and using a hidden form element (could be named redirectURI or potentially anything).

Within the custom edit handler, you can redirect using the hidden form field, something like:

$module->redirectTo( $http->postVariable('redirectURI') );

For more information about custom edit handlers, check out the link below.

http://serwatka.net/en/blog/ez_publish_3_8_new_custom_edit_handler

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 31 2025 01:21:58
Script start
Timing: Jan 31 2025 01:21:58
Module start 'layout'
Timing: Jan 31 2025 01:21:58
Module start 'content'
Timing: Jan 31 2025 01:21:58
Module end 'content'
Timing: Jan 31 2025 01:21:58
Script end

Main resources:

Total runtime0.0276 sec
Peak memory usage6,144.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0053 588.1094151.1953
Module start 'layout' 0.00530.0037 739.3047220.6563
Module start 'content' 0.00910.0169 959.96091,001.8984
Module end 'content' 0.02590.0016 1,961.859437.9922
Script end 0.0276  1,999.8516 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002810.1898140.0002
Check MTime0.00114.0379140.0001
Mysql Total
Database connection0.00082.853010.0008
Mysqli_queries0.00227.989430.0007
Looping result0.00000.046710.0000
Template Total0.00124.210.0012
Template load0.00093.208210.0009
Template processing0.00030.957610.0003
Override
Cache load0.00062.243710.0006
General
dbfile0.003412.436980.0004
String conversion0.00000.035440.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs