[thiago.eec]

Originally Posted by Comfy.n

I'm pretty sure my case is hardly reproducible but anyway, I looked into my past calibre config folder backups, since they contain RG backups prior to the plugin built-in backup feature, to see if I could find something.

Here's what i found:

},
  "All": {},
  "general_info": {
    "autofill_done": true,
    "schema_version": 1.5,
    "timestamp": {
      "__class__": "datetime.datetime",
      "__value__": "2024-12-21T19:56:43.848078+00:00"
    }
  }
}
---
},
  "All": {},
  "general_info": {
    "autofill_done": true,
    "schema_version": 1.2,
    "timestamp": {
      "__class__": "datetime.datetime",
      "__value__": "2023-09-12T06:29:11.015881+00:00"
    }
  }
}
---
 },
  "general_info": {
    "autofill_done": true,
    "schema_version": 1.5,
    "timestamp": {
      "__class__": "datetime.datetime",
      "__value__": "2024-10-27T20:10:28.628124+00:00"
    }
  }
}

Out of 57 json backups with dates ranging from september/23 to december/24, only 6 of them contain the string "All". (I noticed that some have schema version 1.2 then at some point they use 1.5, but this doesnt seem relevant)

So I'm puzzled at why 51 dont have that node "All" and I've sent you the latest backup from october that didn't contain that and also the december one that triggered the error message upon trying to open the main plugin dialog.

Oh and I didn't edit manually the Json, last time I mentioned Json editing on MR was when I needed to transfer highlights from an epub opened outside the library.

I still think that the mentioned "Ctrl+A" action may be triggering this, but I was pretty sure that this was the first time I tried that, maybe not, lol.

Hi, @Comfy.n

Now that you gave me the hint, I did find two "All" entries in over 250 backup files. The last one from Sep 2024. I have a guess of in which scenario this might occur. I'll investigate.

For now, you might want to manually delete this "All" entry from your current database. Then the plugin will work again.