Webmaster Forums - Website and SEO Help

Microsys Products and Webmaster Tools => Launcher => Topic started by: AlexanderP on April 07, 2012, 01:58:10 PM

Title: Feature Request: Config option to limit the number of backups
Post by: AlexanderP on April 07, 2012, 01:58:10 PM
Hi Thomas,
could you please add an option to limit the number of backups.
Best regards from Vienna,
Alexander
Title: Re: Feature Request: Config option to limit the number of backups
Post by: Webhelpforums on April 07, 2012, 02:47:27 PM
Hi,

Every time you start Launcher, the "Save" menu options reset meaning default is not to make backup when saving.

I was in doubt about how to best implement this, but with the current system, it is easy to add a new backup (but no automatic backup)
Title: Re: Feature Request: Config option to limit the number of backups
Post by: AlexanderP on April 08, 2012, 12:53:16 AM
Hi,
sorry I wasn't clear with my request. Correct every time I change & save the config I create a new backup. Perfect.
There are now 12 backup folders - that's a little to much backup. It would be great if Launcher checks every time I press save how many backups still exists and if the number of backups is more than x The oldest backup will be deleted before a new backup is created.
Title: Re: Feature Request: Config option to limit the number of backups
Post by: Webhelpforums on April 10, 2012, 08:57:31 PM
I will consider if I can make a different backup system that is smarter. But I rather have to many backups than to few :)

(Especially since making a backup requires an active action by user.)
Title: Re: Feature Request: Config option to limit the number of backups
Post by: scottlosjoy on December 28, 2013, 02:24:16 AM
In the past couple of months I have lost most and today I lost all of my shortcuts (except the one I was adding) when saving after adding a new shortcut.
Title: Re: Feature Request: Config option to limit the number of backups
Post by: Webhelpforums on April 28, 2014, 07:59:18 AM
Update: I believe this issue has been fully resolved in version 2.1