Quote:
Originally Posted by capink
I made a quick test with set_metadata and it was slower than single field edit even for one book. It compounded the problem and calls Last Modified plugin multiple times per field per book.
Edit: It seems set_metadata() is calling set_field() for every field, even if the field value was not changed.
|
set_metadata() completely wrecks havoc with Last Modified plugin because it overwrites all the fields, even if the value has not changed, and emits db event, falsely notifying Last Modified plugin about modification in those fields.
Problem is, set_metadata() is used by a number of plugins (e.g. Import List). The solution for this mess is to retire the Last Modified plugin, because in the current state, it cannot do its advertised job.
If anyone knows what is required to retire a plugin, please tell me. Is it enough to simply remove from the Index of plugins thread? Or is there something else I have to do?