okay, doing a default install on the original database with NO custom template - leaving it to show the template default does not stop this issue.
It's not a template file, it's not an errant old file. The only left is the database but I can't see how anything there can cause these warnings. Maybe this is just an odd happening - over the years I've seen a lot of strangeness from an old database and I can certainly give the cart owner instructions just to the error logs regularly - for me it's really a great indicator for some clients do some cleanup or easy maintenance.
But as we are dealing with the new version, I think we should go deeper into this and I'm at the end of my ideas. Shall I just let this die?
Bookmarks