I don't know what to say--but what if you had the page go to
action.back which had nothing in it but a bit of javascript that sent
the browser back two pages? So nextpage goes action.back. And then
they immediately get redirected back to the original location.
I tried this snippet and it worked for me:
function BOLTFback($args, $zone='') {
global $BOLTpluginHeader;
$BOLTpluginHeader[] = '<script language=javascript>
window.history.go(-2);
</script>';
}
And then put on the second page [(back)]. It returned me to the
original page at the right spot. Didn't tryi it with a form but you
might be able to tinker and get it to work.
Cheers,
Dan
On Fri, Sep 25, 2009 at 1:52 PM, DrunkenMonk <[email protected]> wrote:
>
> Actually, I still can't get forms to go back after submition. I tried
>
> in a config file:
> $BOLTformJs['back'] = "onPost=javascript:history.go(-1)";
>
> and
> action.test:
> [form js=back]
> [submit "submit and return"]
> [session msg Huzza!]
> [form]
>
> Which correctly returned me to the previous page, but the form
> returned an error. I'm thinking the link needs to be called after form
> processing, but I do not know how to put any triggers there, except
> for nextpage. If nextpage could be updated to work with javascript
> calls, this would be fine. You could probably do a lot of fun stuff
> with that, apart from what I'm trying to do...
>
> Otherwise I don't know how to implement this, short of a BOLTX plugin.
>
> DrunkenMonk wrote:
>> Yup. Theres a plugin to fix it and firefox 3.5 fixes it. Thanks for
>> the help.
>>
>> On Sep 25, 11:04 am, DrunkenMonk <[email protected]> wrote:
>> > It's difficult to find discussions, since firefox still manages to
>> > handle most webpages correctly.
>> >
>> > Now, I don't know much about low-level web-pages, but is it possible
>> > that Boltwire is telling firefox that the pages are "new", always, and
>> > as such firefox resets itself while other browsers assume the site
>> > doesn't know what it's talking about? a 205 code, or even 201?
>> >
>> > It would explain why boltwire is different to, e.g., bbphp forums...
>> >
>> > On Sep 24, 4:40 pm, The Editor <[email protected]> wrote:
>> >
>> > > Evidently so. It works for me on IE and Chrome, but not FireFox. Sorry
>> >
>> > > It may be firefox handles the javascript history object differently.
>> > > I'm sure there's got to be some discussion of this somewhere on the
>> > > web.
>> >
>> > > Cheers,
>> > > Dan
>> >
>> > > On Thu, Sep 24, 2009 at 10:33 AM, DrunkenMonk <[email protected]> wrote:
>> >
>> > > > That puts me at the top of the page. So it's a firefox issue, then.
>> >
>> > > > On Sep 24, 3:43 pm, The Editor <[email protected]> wrote:
>> > > >> I just went tohttp://www.boltwire.com/index.php?p=solutions, scrolled
>> > > >> down to the last solution, wikiwyg, clicked it, then hit the back
>> > > >> button in my browser, and it went back to the same spot on the page.
>> > > >> I'm using Chrome...
>> >
>> > > >> Try this: it worked for me:
>> >
>> > > >> MarkUp('links', 'back', '/\[back\]/ie', 'BOLTescape(\'<a
>> > > >> href="javascript:history.go(-1)">Back</a>\');'); // [back]
>> >
>> > > >> Just put [back] on a page where this is enabled.
>> >
>> > > >> Cheers,
>> > > >> Dan
>> >
>> > > >> On Thu, Sep 24, 2009 at 8:16 AM, DrunkenMonk <[email protected]>
>> > > >> wrote:
>> >
>> > > >> >> A bit annoying.
>> >
>> > > >> > I scoured the source of 5 different pages trying to find what they
>> > > >> > had
>> > > >> > and boltwire didn't.
>> > > >> > I upgrade it to: Very annoying.
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
