Closed (fixed)
Project:
Drupal core
Version:
x.y.z
Component:
base system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
25 Mar 2006 at 20:14 UTC
Updated:
18 Apr 2006 at 08:00 UTC
Jump to comment: Most recent file
Comments
Comment #1
Steven commentedWell, here's a patch which restores the destination... but for some reason it doesn't work for me for the log-in block. Somewhere along the it seems to get lost.
FWIW, this bug was already there before that 404/403 patch, if you used a custom 404/403 handler. Now it happens for everyone.
Comment #2
Steven commentedTo clarify: the patch above restores the destination, and it correctly appears in the form action="..". But it is not being used by the form API.
Comment #3
chx commentedWhat about this?
Comment #4
chx commentedSteven drilled down to the core of this issue but run out of time, so I post instead
Comment #5
Steven commentedHere's a slightly improved patch. Instead of a non-existant path like "^" or "#", I just changed menu_set_active_item() to distinguish NULL from an empty string. This does not affect any usage of menu_set_active_item() in core. The benefit is that there is no longer a 404 in the watchdog after submitting a form on a 404/403 page.
Tested to work for both clean and non-clean URLs.
Comment #6
chx commentedisset is faster than is_null.
Comment #7
Steven commentedCommitted to HEAD.
Comment #8
(not verified) commented