Oops. Had one minor bug. Here is a new version. Let me know if it does/doesn't work.
Thanks, Paul > -----Original Message----- > From: p dont think [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 27, 2003 5:34 PM > To: 'Chris Winterrowd' > Cc: '[EMAIL PROTECTED]' > Subject: RE: [SM-USERS] multilogin and timeout plugins > > > > (prefs_stored_with_imap_addr.squirrelmail.tar.gz).. > > > > > > Looks like I did this back in the days of 1.4.0. Not sure if it'll go > > > cleanly against 1.4.1 or not. Let me know if it doesn't go in cleanly. > > > > It went in for what I need -- ./plugins/calendar/calendar_data.php blew > > up, but I don't use calendars here - and I didn't have smallcal, so I > > don't know if that would have worked. Thanks!! This makes multilogin a > > possibility for me! > > Is this still working for you? I might release it as a "plugin" if so, or bundle > it with Multilogin. > > > >> I would greatly appreciate a plugin that would do this. The only other > > >> solution I have been curious about is this - instead of the whole > > >> Quicksave plugin workaround (this seems kind of messy to me), is there > > >> a way the timeout_user plugin could perform the timeout _after_ it > > >> allows a message to be sent, or if it could instead of sending the > > >> message, execute a "save as draft" and then close the compose window > > >> and timeout the user? > > > > > > You mean have the timeout_user plugin "press the send button" > > > automatically? Yikes. I like the other idea of saving a draft. I can > > > look into this. > > > > Yikes Indeed! What I was thinking was to allow the user to click "Send" > > (when finished composing) or "Save as Draft" and even if they had timed > > out, it would perform that last task before logging them out. On second > > thought, I realized the compose window would go away anyway because the > > way the timeout occurs (it forces the browser to do the refresh).. it did > > not occur to me since I use Compose in New Window. > > > > I've been spending some time thinking about a better way to do this and > > I'm curious if there is a way to set a timer in the php session and do the > > timeout "server side" so depending on what action the user is trying to > > perform, timeout will either allow a final action prior to timing out > > (such as send, or save as draft) or disallow it entirely and time out. > > > > All this said, in the interest of keeping this simple, I really like the > > idea of doing a "Save as Draft" if a timeout is taking place - it makes > > recovery much simpler. If you think this is worth investigating (and not > > too difficult to implement), I'd be willing to do my best to help! > > Attached please find a new version of timeout_user. It addresses both of these > issues: when composing a message, the plugin will first save it as a draft > and then time out. When browsing away from SM and coming back after the timeout > duration has expired, the signout screen is shown (you *can* browse back to > SM if it's within the timeout duration). > > Let me know if you need anything else. > > - Paul > > PS - I'll go look now, but if you can remember the thread subject where people > were talking about "breaking" the back button, I'd appreciate you telling me.
timeout_user-1.2-0.5.tar.gz
Description: Binary data
