PS: i found some edge case behaviour that might cause an issue in some cases and fixed that too with wppizza 3.12.5

though i very much doubt that that was the reason in your customers error messages, if you test things as outlined above, you might as well use that just updated version(might take a little bit to show up in your admins plugins page as an update being available though)
just thought i’d mention it here while we are at it

>For now we are back in business
ok, that’s something at least

>just the errors behind the scenes that you are aware of
just updated the wppizza plugin to 3.12.4 , which should take care of those behind the scenes errors (at least the ones which were false positives – i.e “cannot find order etc ” when your shop was closed anyway)

apart from those though i cannot see any difference between 3.12.2 and 3.12.3 that would allow people to order or not
maybe – when you are closed – update to 3.12.4 and try some test orders and let me know if you can in any way reproduce getting any kind of error

PS: in 3.12.4 you can keep the shop closed and open it just for you by going to WPPizza -> tools->Always open shop for UserID

and then enter your wp user id there (probably “1” if you were the person that installed wordpress or your ip address

that looks like javascript errors – the browser console would tell us more, but i appreciate that most users would not know how to access this .
seemingly also from a mobile device – might have something to do with this .
i’ll make a fake order (it will fail and will be clearly marked as “do not process” and you’ll get an error send to you , just ignore that , just try to find out if i can reproduce something)

in the meantime (FYI):
i can reproduce this here with your cloned site. that’s a good thing.
and it transpires that this is a bug in the main wppizza plugin if only one gateway is enabled which is not a cash on delivery or similar pay in delivery gateway (i’ll spare you the minute details here). i’ll update the plugin accordingly and release an update tomorrow or latest the day after i would think.

will that update fix all issues ? hopefully one would think (certainly fixes things here and i cannot reproduce any errors with that fix applied), but i would suggest – when that update is available and you updated your version – you’ll keep debug enabled for a few days in case there are more as yet unknown issues . it will help track them down more easily if this should be the case

other than that, having looked at some of your settings, though not in minute detail , i would probably also suggest you

– a) set the timezone in WP->settings to an actual place (i.e London/Europe or whatever is appropriate) as opposed to UTC -1 as time offsets change for locations during the course of the year
– b) assuming you are not a charity, look at your tax settings. you are probably not tax exempt (i might be wrong of course) so entering your actual tax rates and then enabling “Prices include Tax” would presumably be a more accurate reflection of prices/tax (wont fix past orders, but going forward is likely to be a good thing to do, especially if using the reports->export ability for tax purposes – if you need to )

just suggestions/observations though. entirely up to you of course how you want to do things exactly

for the time being , the only way to do that would be to do a “dummy” order by yourself for that timeslot so it’ll be taken away from the available ones
(I don’t understand why that question is marked as private ?)

>It was either 3.12.2 or 3.12.1 at least it narrows it down a bit !
close enough. i dont think 3.12.3 could cause this , as there’s nothing in that update i believe that could have anything to do with this , but we’ll see. i’ll check a few things on that front too

>We will need to take off debug mode before the morning though when we open
dont know why that’s strictly necessary, but by all means – kind of know what we are looking at for the moment anyway
feel free to turn it off right now and/or even delete/empty that debug.log. all the info needed we have (as it stands at the moment i think anyway)

>Debug now looks like this for reference
thanks, no need for that though. i can see this myself
let me see if i can reproduce this behaviour here first of all.
will get back to you when i know more – might take a bit of time though

i would suggest you increase the memory limit too
40M is fine for a simple blog that doesnt do much
anything more than that (like ecommerce for example) i’d do 128M minimum
though wppizza has quite a small footprint on that front – https://plugintests.com/plugins/wppizza/latest –
putting themes and different plugins alltogether will probably require more

that’s not just a wppizza thing, but generally the case.
i dont think any other ecommerce plugin – woocomerce at all – will recommend anything less than 128 here