On 11/17/14, Daniel <dan...@albury.net.spam.au> wrote:
> On 18/11/14 00:39, Lee wrote:
>> On 11/17/14, okj...@gmail.com <okj...@gmail.com> wrote:
>>> On Sunday, September 21, 2014 9:30:23 PM UTC+2, EE wrote:
>>>> Why is it that with SeaMonkey 2.29, the new .jsonlz4 bookmark backups
>>>> will not restore, and the manual .json backups will now not restore
>>>> either?  Why change things so that backups are not restorable?
>>>
>>> Why isn't this question answered, and why does the problem with bookmark
>>> backups prevail in 2.30 ?
>>
>> I haven't tried restoring a .jsonlz4 bookmark backup, so I don't know
>> if it will restore or no, but as a work-around, in about:config you
>> can set
>>    browser.bookmarks.autoExportHTML
>> to true so that SeaMonkey will save your bookmarks at exit to
>> bookmarks.html in your profile directory.  Which isn't nice as the
>> last however many files saved in the bookmarkbackups directory, but if
>> you do regular backups it's pretty close.
>>
>> Regards,
>> Lee
>>
> Just FYI, Lee, I've had my SM prefs set as you indicate but I've had no
> bookmark files created (unfortunately!!) since about January. (on either
> Win7 or Linux)

before exiting SM:
11/15/2014  07:35 PM           966,972 bookmarks.html
after:
11/17/2014  10:53 AM           966,972 bookmarks.html

at the very least, it updates the timestamp for me :)

... are you expecting multiple files?  All you get is the one file,
which is why I said
>>        Which isn't nice as the
>> last however many files saved in the bookmarkbackups directory, but if
>> you do regular backups it's pretty close.

Lee
>
> --
> Daniel
>
> User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:32.0) Gecko/20100101
> SeaMonkey/2.29 Build identifier: 20140829003846
> or
> User agent: Mozilla/5.0 (X11; Linux x86_64; rv:34.0) Gecko/20100101
> SeaMonkey/2.31 Build identifier: 20141020202138
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to