Nico Klasens <[EMAIL PROTECTED]> wrote: > > Well, you shoudl not use teh referrer variable for this. It > > was not intended to be used like this. > > The referrer parameter was intended to fix the issue that not all browsers > are sending the http referrer header. The idea was to tell the editwizards > to return to the page where the wizard was started from.
Not only that, but more importantly, 'referrerdir' which is evaluated from 'referrer' is used to search overriding XSL's which are supposed to be next to the calling page. In extending XSL's you could e.g. use it to refer to CSS's which are relative to that as well. Also 'templatedir' can be used if you want similar functionality but relative to something else than the 'calling' dir. > In some cases you want the wizards somewhere in the middle of an edit > flow. With the fix to make the referrer explicit it is also possible to > pretend that another url is opening the page to redirect the wizard > somewhere else. Will the referrer parameter in the 1.8 release be > deprecated and replaced by a couple of other more logical parameters? I'm not sure if 'referrer' and 'templatedir' are illogical. Though 'referrer' is constantly misunderstood for 'returnpage', probably because that is not implemented. I'd say that 'referrer' should only be the default value for 'returnpage', but you could simply specify 'returnpage' if you want to go back to something else than that. Perhaps it will be enough to implement this 'returnpage' feature (seems extremely simple), and simply cleary document where these kind of options are for. I just checked and it seems that referrer and templatedir are not documented at all. Michiel -- Michiel Meeuwissen | Mediapark C101 Hilversum | +31 (0)35 6772979 | I hate Internet Explorer nl_NL eo_XX en_US | mihxil' | [] () |
