[SOLVED] CBSubs "error": loadSomething::subid XXX with planid Y could not load.

Hi,

I sense it's not really "errors", which is why I'm putting it in quotes here.

Anyway, I'm getting several of these in CBSubs' History Log, and I guess it has to do with the "basket timeout" recorded at the same time. See screenshot of History Log attached.

Baskets being abandoned does happen, and I appreciate the basket timeouts and them apparently getting deleted from the DB. But these subid errors seem obsolete - in a History Log that's already flooded with all other sorts of stuff, anyway.

Or should I be paying attention due to some deeper meaning of them and something being wrong at my end?

Thanks for some enlightenment. And, if these "errors" are indeed not errors but harmless/obsolete, thanks for potentially taking steps for an upcoming nightly to suppress what is otherwise only inflating logs unnecessarily, and eventually causing clients to worry.

P.S.: Screenshot of log attached.

The subscription information for the expired basket tried to load, but couldn't because the subscription doesn't exist yet or anymore. Nothing to be concerned about and is just a part of the abandoned basket logging.

Thanks - so it's as suspected: information with no relevance but "concealed" as errors, haha.
As indicated, would be nice if it were not logged much longer. Again, not least to keep clients' confidence high and their sleep tight.
Also, because it seems they are a bit harder to catch (the errors, not the clients) with a delete per CRON as they appear to have much in common with other "real" errors.


BTW - a bit off yet still near topic: any moves towards the function of disabling unused currencies, and those then hopefully not updated/logged any longer? How often do they update per day? Looks like multiple times? How many CRONs do I need? Lol...

Thanks - so it's as suspected: information with no relevance but "concealed" as errors, haha.
As indicated, would be nice if it were not logged much longer. Again, not least to keep clients' confidence high and their sleep tight.
Also, because it seems they are a bit harder to catch (the errors, not the clients) with a delete per CRON as they appear to have much in common with other "real" errors.

They're not errors, but just notices. This is indicated directly in the history log and in your screenshot. I don't recommend you or your client becoming to obsessive over the history log as it logs a lot of little info things and notices. Mainly needs to be checked in the event of an actual error (e.g. payment failed, basket errored, etc..).

BTW - a bit off yet still near topic: any moves towards the function of disabling unused currencies, and those then hopefully not updated/logged any longer? How often do they update per day? Looks like multiple times? How many CRONs do I need? Lol...

That feature ticket is currently marked for CBSubs 4.1.0. It has yet to be implemented, sorry.

krileon wrote: They're not errors, but just notices. This is indicated directly in the history log and in your screenshot.

Kinda sensed it before, and know latest now. But what stands out is the column at the left (= seen first) where it states "Error log". Dang!
No worries, I'm not too concerned about the log, and certainly not obsessed, lol. I only don't want the client to get even only near any of those states...

That feature ticket is currently marked for CBSubs 4.1.0.

Cool if it's in the works. Now prayers for 4.1.0 before Xmas... :whistle: