Previous TACL version didn't show any entries; V4.2.1 shows same date_all entries

[bendover22]

trafficstars

/* Thanks for your report! Please provide these info when you found bugs. */

Required: Linux Mint 18.1 Fx 65.0.1 64bit TACL 4.2.1 (Mar. 6, 2019) Optional:

• step to reproduce the problem.
• other descript you want to tell me. :)

The TACL version BEFORE 4.2.1 wasn't showing any saved entries, that would've been from several sites, including Github. The popup window was blank where saved entries normally are. I think? that started after updating to the version BEFORE v4.2.1.

Updated to 4.2.1 - it now shows some entries that were "saved" while using the previous TACL version. I didn't change any TACL settings between the last version and v4.2.1.

V4.2.1 also shows ALL entries saved under the PREVIOUS version as having the exact same (incorrect) date & time - to the second, for every (old) entry it's now showing. 12/31/1969 6:00:02 PM. I think a similar issue was reported 1 or 2 yrs ago.

Happy to report, for THIS Github post, made under 4.2.1- shows the correct date & time & only a single entry (no duplicates)!!

Many past entries (now shown under 4.2.1) have 2 to 4 EXACT duplicates of an entry on a given site (like Github). Not drafts saved at different times (with different content). They're exact duplicates of the final entry submitted (mainly Github, but that's mainly where I've entered form text lately).

On a few forums (support.mozilla.org) - the previous TACL version apparently saved NO entries - no URL, content or date. The current v4.2.1 isn't showing entries for support.Mozilla, that I made around the same time as ones it now shows for Github, after updating to v4.2.1.

I will create a new profile & re-test v4.2.1 w/o any other addons.

[bendover22]

I created a clean profile & installed a fresh download of TACL 4.2.1. Copied TACL's s storage.js to new profile.

It still shows older entries - made under 4.2.0, all with same date = 12/31/1969, 6:00:02 PM. It still shows entries saved under v4.2.0 with multiple, identical copies.
Didn't really expect it to display the database any differently, but gave it a shot.

I could understand if each duplicate was a "draft" copy - saved at different times (& showed the times) & you could pick a previous point in the saved entry, but that's not what it was doing. For now, the duplicate entries and the 1969 date issues seem fixed in v4.2.1 (Fx 65.0.1 in Linux Mint). '69 was a good year for some... & not good for others.