No, I mean physically hit myself…
Well, er, I’m afraid I didn’t understand it. You use a bookmark to a
queue view, you see the queue, you press “reload”, and you get up some
totally different filters? That just shouldn’t happen, I’d say.
That patch you mention, does it do cookies, or what…?
No, it’s only for preserving form data through a login session.
If you hit a link (or a bookmark) and you’re not logged in, I think you
will loose all data from the link/bookmark in rt1.
I thought this patch was included in rt1, but maybe not - we introduced a
feature freeze looong time ago because we wanted a stable 1.0, quickly
followed by a 1.1 release. Just that 1.1 never came, now we’re working
towards 2.0 instead.
There was a patch for allowing queue selection to be set through cookies,
but I daresay it’s obsolete, as patches usually don’t persist long
in a ever-changing codebase.
I think the 2.0 design is so modular that most “bigger” features will be
trivial to contribute a bit more stable “modules” rather than patches. I
also hope we will get one working development branch which is
+47 22 925 871