On Mon, Oct 19, 2009 at 1:23 AM, Markus <[email protected]> wrote:
>
> On Oct 18, 11:43 pm, The Editor <[email protected]> wrote:
>> Why don't you either
>>
>> 1) set defaultPage: action.login, or
>> 2) set defaultPage: main.login and then on page main.login put
>> [(forward mypage&action=login)]
>
> Thanks for pointing me to the (almost) obvious. :)
>
> 1) As I noted, I don't want users to land on the "meaningless"
> action.login page after logging in.
>
> 2) Great idea, though it's not working for me. It forwards me to
> "mypage%26amp%3Baction%3Dlogin" and that is blocked. Probably the same
> issue Hans and you are discussing in the other thread?
I'm still working on Hans issue, which though related is different.
This one is caused by the fact & is now escaped when it gets to the
forward function. And then with Hans patch (which you seem to have put
in), it then gets url encoded to make it worse.
Try undoing Hans patch just for now, and do this instead in engine.php
line 1700:
if (strpos($nextpage, '://') === false) {
$nextpage = str_replace('&', '&', $nextpage);
I'll deal with < and > later but they are special cases. I'm more
worried about getting every day ordinary stuff working. We'll figure
out the complex stuff later.
Cheers,
Dan
P.S. You could also put this on a page just to be a bit nicer...
[if login]<(forward mypage)>[else]<(forward mypage&action=login)>[if]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---
