Well, if you really have trouble with this, safest bet imho is mount
the page using HybridUrlCodingStrategy and make sure that the page is
delivered with Cache-Control: no-store header (set inside
Page.configureResponse).
You need most recent 1.3 to be able to mount the page using
HybridUrlCodingS
Did anything ever happen on this? Trying to resolve issues with Ajax on
bookmarkable pages when I use back button to go back to previous bookmarked
pages. Ajax URLs don't seem to include context for the pagemap, and so are
being applied in context of most recent page, instead of the page they were
How about automatically removing all users (except for those that will
continue to monitor the list, and perhaps nable) and not allowing
anyone else to sign up?
Maurice
On 8/5/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> We already have that in place: every day anyone posts to wicket-user@
>
We already have that in place: every day anyone posts to wicket-user@
he'll get an auto-response telling the mailinglist is shutting down.
However, the message still gets through.
I'm trying to stop that last part too, but am not sure if the
auto-response is sent *before* the moderation has occurr
Is there anyway to setup an autoresponder on the sf.net side?
On 8/5/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
>
> I see that we get less and less messages sent to [EMAIL PROTECTED]
>
> So I propose to put emergency moderation to effectively shut the list
> down completely.
>
> I think we ne
I see that we get less and less messages sent to [EMAIL PROTECTED]
So I propose to put emergency moderation to effectively shut the list
down completely.
I think we need a couple of additional moderators to monitor the list
and reply to messages sent to wicket-user telling them to resend to
[EMAI
