[dokuwiki] Re: [PATCH] New request-parameter redirect_id
- From: Christopher Smith <chris@xxxxxxxxxxxxx>
- To: dokuwiki@xxxxxxxxxxxxx
- Date: Wed, 20 Aug 2008 20:24:08 +0100
On 20 Aug 2008, at 14:58, Michael Hamann wrote:
Christopher Smith wrote:
Still on the not needing to change the core, perhaps a new event
could be created to wrap the current redirect, along the lines of
name: ACT_REDIRECT_ONSAVE
data: array/object containing three values, page id, fragment-id,
more
preventable: yes
action: redirect to url created by combining the three data values
result: return value for act_save if no redirect takes place
notes: after advise will not occur unless action (redirect) is
prevented.
That sounds good, but as I noticed yesterday there is a similar
situation after act_draftdel(), at the moment there is no redirect
at all after act_draftdel(), but I would like to add a redirect
there, too. So perhaps one would need an event there, too? Or one
might use the same event with other data because also in the core
the action to be executed is the same.
If the same event was to be used, $ACT would need to be added to the
data and a more general name, say ACTION_ACT_REDIRECT. I prefer this
to my previous suggestion. Any action which ends in a redirect would
then call this event.
- Chris
--
DokuWiki mailing list - more info at
http://wiki.splitbrain.org/wiki:mailinglist
- References:
- [dokuwiki] [PATCH] New request-parameter redirect_id
- From: Michael Hamann
- [dokuwiki] Re: [PATCH] New request-parameter redirect_id
- From: Christopher Smith
- [dokuwiki] Re: [PATCH] New request-parameter redirect_id
- From: Christopher Smith
- [dokuwiki] Re: [PATCH] New request-parameter redirect_id
- From: Michael Hamann
Other related posts:
- » [dokuwiki] [PATCH] New request-parameter redirect_id
- » [dokuwiki] Re: [PATCH] New request-parameter redirect_id
- » [dokuwiki] Re: [PATCH] New request-parameter redirect_id
- » [dokuwiki] Re: [PATCH] New request-parameter redirect_id
- » [dokuwiki] Re: [PATCH] New request-parameter redirect_id
- » [dokuwiki] Re: [PATCH] New request-parameter redirect_id
Christopher Smith wrote:
Still on the not needing to change the core, perhaps a new event could be created to wrap the current redirect, along the lines ofname: ACT_REDIRECT_ONSAVEdata: array/object containing three values, page id, fragment-id, morepreventable: yes action: redirect to url created by combining the three data values result: return value for act_save if no redirect takes placenotes: after advise will not occur unless action (redirect) is prevented.
That sounds good, but as I noticed yesterday there is a similar situation after act_draftdel(), at the moment there is no redirect at all after act_draftdel(), but I would like to add a redirect there, too. So perhaps one would need an event there, too? Or one might use the same event with other data because also in the core the action to be executed is the same.
- [dokuwiki] [PATCH] New request-parameter redirect_id
- From: Michael Hamann
- [dokuwiki] Re: [PATCH] New request-parameter redirect_id
- From: Christopher Smith
- [dokuwiki] Re: [PATCH] New request-parameter redirect_id
- From: Christopher Smith
- [dokuwiki] Re: [PATCH] New request-parameter redirect_id
- From: Michael Hamann