> > (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!
excellent. But beware, this is very much alpha in nature - has not been tested extensively! > >> 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. Yes, there are ways to accomplish that. A bit complicated given that the META tag works in most cases. It might be best to just keep it client-side. There are still possibilities for not trashing the user's email but keeping the timeout code client-side. I will try to look into this as time allows. > 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! I'll let you know when I have something. > > oh, btw, although quicksave is indeed messy, it is helpful in a number > > of other circumstances.... accidental logoff or closing of the browser, > > system failures, etc. > > I'm using it for my personal installation (it is handy), but since we have > so many browser compatibility issues (usually related to IE) I'm scared to You mean quicksave clashes with IE? > Thanks again! No problem. Thanks for your patience. - Paul ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
