Hi @capink, thank you for looking but I think I had a little PEBKAC, though. I hope I can clarify what happened:
Even though I had appreciated BetterRed column-heading naming approach (Last Action), as it avoids confusion and is perhaps more accurate semantically, I chose to insist on the 'modified' nomenclature.
The reason for this insistence was that I had decided to forget completely the built-in Modified (last_modified) column, by hiding it for good in the book list, and replacing it with an almost identical column from this plugin: #m = Last Modified.
However, probably due to my constantly alternating book list layouts with the View Manager Plugin, I realise that at some point I was actually sorting by the built-in column Modified, instead of Last Modified, lol. So the timestamp reset I was seeing upon customising custom columns was NOT being originated by the plugin.
Also, when I tried to add the built-in 'Modified' to the plugin exceptions, I was using the incorrect lookup name "modified" instead of "last_modified". What a mess on my part, sorry!
Anyway, in order to prevent any further mistakes, I changed the headings and lookup name for this PI column. This is what I had before:
Now I have:
I should note that I've just tested v0.84 against v0.85 and I can confirm that, at least with the plugin settings as shown below, there occurs no timestamp reset, as I wrongly assumed.
