>>>>> But in case that isn't your cup of tea. I'm thinking of making a >>>>> "backup" >>>>> plugin which you can select to backup/export your addressbook (will >>>>> probably >>>>> also offer a vcard conversion so outlook can easily open it), >>>>> Filters, Mail >>>>> Fetch >>>>> Options, Notes, >>>>> Calendar Entries, ect... (it will just auto detect which plugins you >>>>> have). And ofcourse why be able to back them up, if you can't also >>>>> restore >>>>> them, so don't fret about that not being in there. They would be >>>>> downloadable >>>>> as text/zip/tar/Gzip files. The plugin will be modular so that other >>>>> plugins >>>>> can hook into it to allow the export/import of their data also. >>>>> >>>>> Overall the concept is fairly simple. I have already rewritten my >>>>> virus scan plugin to be modular, the beta I have allows you to switch >>>>> between >>>>> using my perl scanner or clamav's scanner, or you can write a simple >>>>> addition >>>>> to allow it to scan using whichever scanner you have on your server. >>>>> >>>>> I hope to find time this week to start on it. It shouldn't require >>>>> too >>>>> much time at all to get up and running. Any one else interested / >>>>> have ideas? >>>>> >>>>> Jimmy >>>>> >>>>> >>>> On Sun, October 17, 2004 10:59 pm, Joe Aldeguer said: >>>> Hi Jimmy, >>>> >>>> >>>> >>>> I am very interested that sounds like a great idea to give individual >>>> users ability to backup their own mail files. By the way thanks a lot >>>> for the >>>> file attachment block plugin I use it to protect my users from >>>> themselves ; ) >>>> >>> >>> In case anyone is interested in trying out the backup plugin I was >>> talking about, here is a nearly ready beta of it. Allows backing up of >>> your >>> filters, addressbook, and mail fetch settings currently (but only if >>> you have >>> those plugins installed ofcourse). I definitely plan on adding alot >>> more options, >>> and alot more things to backup (like your entire prefs file, calendar, >>> notes, >>> bookmarks, ect...) >> >> Please keep in mind that the calendar backend will be changing. >> > > Ya, I've known about that, which is why I haven't bothered with writing > a > calendar module for this yet. > >> >>> You can download them in zip, gzip, or tar format. You can also >>> restore >>> them easily from the webpage. It is completely modular so anyone's >>> plugin can add >>> things to be backed up. >>> >>> Currently the backed up file is compressed, serialized, and "simple >>> >> >> Why muddle in the file system at all? You'd have to get a master list >> of >> prefs, but if you did, you could offer backup in a backend-independent >> manner, and >> avoid what is very likely to be complaints from people whose web server >> can't >> directly access pref files or some such hassle. Or do you plan to offer >> SQL backend >> users a quick and dirty query that grabs all prefs and downloads them, >> too? >> >> -paul > > You really don't need a master list, their are "ways" of obtaining the > preferences > for a user.
I wouldn't be surprised. If so, then why rely on copying a file backend prefs set at all? If you can use these "ways", then it would be much more reliable and backend-independent to get that magic list, pull each of those prefs, and then give the user a download (ala download.php). > The webserver should have read and write access to the > prefs, else > users couldn't save anything including their name/email ect... Yup, which is why I said "or something", because every time there is a plugin that touches file system files, as you well know, there is always *someone* who has problems. Plus, keeping things backend-independent is a very big plus. > reading the > prefs > file directly would be simplest way to go about it, and for mysql users, a > sql call > and a little parsing is all that it would take. Once we know the names of > all the > prefs, then use getpref and setpref accordingly... Yah, this is what I was thinking, but I mentioned the master list because that is a way to avoid the need to query each backend seperately and to keep the plugin truly backend-independent (and keep it *much* simpler). The master list of SM prefs is easy to get. Plugins would have to be added as we can figure them out. This got me thinking about a more robust interface for the <plugin_name>_version() function in setup.php, but that's another conversation... -= paul > If there is a special > circumstance where the webserver doesn't have write access to the file (I > would > believe that read access is mandatory) then this plugin isn't really > something that > admin would want to install anyways. > > I really don't have much major use for this plugin myself, they mentioned > it here, > and someone else once requested something like it, and I saw that it was > definitely > do-able, so I threw something together. I prefer to continue doing my > nightly > backups myself, this is more for people who don't keep backups of the > users data (or > do, but don't want to have to restore Joe's Users addressbook because he > deleted his > great grandmothers email address (I've heard it all)), but would like to > give their > users the option to keep up with their own backups of their settings, > ect... > > I'm really not sure if I will add in the "complete" backup of a users > prefs, its was > more of just a thought. I think allowing them to backup the addressbook > and filters > are the more important things. The rest will probably just be added on > request. > > Jimmy > ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_idU88&alloc_id065&op=click -- squirrelmail-users mailing list Posting Guidelines: http://squirrelmail.org/wiki/wiki.php?MailingListPostingGuidelines List Address: [EMAIL PROTECTED] List Archives: http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.user List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id)95 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
