On 1/10/2019 10:56 PM, Frank-Rainer Grahl wrote: > The functionality was removed from Gecko. Unless the add-on does query the > database directly it won't work. There is a bug open about this in SeaMonkey > but the guy who wanted to re-add this dropped out submitting a few > non-working > early patches. If the add-on works correctly it would wonder me. > > FRG > > Rainer Bielefeld wrote: >> On 1/11/2019 6:30 AM, Rainer Bielefeld wrote: >>> I will try same profile with 2.49 >> >> >> Also does not work: >> <https://unofficialseamonkeynews.files.wordpress.com/2019/01/190111_901_expirehistory_screenshot.png> >> >> >> >> Entries for pages last visited November 2018 stay, even after some Browsing >> on >> different sites and 2 relaunches of SM. >> >> In between I lost all History entries, but that is something different, has >> nothing to do with the Add-On. I already observedthis loss several times >> when >> I switched between 2.49 and 2.53 with the same profile. >> >> How fast does the add-on delete old entries when you reduce "Days undtil >> ..." >> entry? >> >> CU >> >> Rainer
I installed Expire history by days [converted] 1.2.0 on 9 Feb 2016 in two of my SeaMonkey 2.40 profiles. I then reinstalled it on 6 Oct 2018 when I discovered that the converted 1.2.1 did not work. In one profile, the number of days set is 30. In that profile, I have no history entries older than 30 days. This is not because I reached the 10 MB limit on the size of places.sqlite. Using SpeedyFor 2.0.23, I vacuumed all sqlite files in that profile, after which places.sqlite required only 3.1 MB. In the other profile, the number of days set is 45. In that profile, for some strange reason, the oldest history entry is 48 days old. After running SpeedyFox, places.sqlite in that profile required only 1.0 MB. Conclusion: Expire history by days [converted] 1.2.0 seems to work in a profile for a setting of 30 days but leaves extra history entries for a setting of 45 days. I will test further. -- David E. Ross Trump again proves he is a major source of fake news. He wants to cut off disaster funds to repair the damage caused by the Woolsey Fire in southern California because he claims the state fails to manage its forests properly. The Woolsey Fire was NOT a forest fire. Starting in an industrial tract, it did not burn through any forests. See <http://www.rossde.com/fire.html>. _______________________________________________ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
