this is most likely a priority / race-condition issue
i’ll try to reproduce this here somehow first of all -and will get back to you when i can have something sensible to say about this
at the moment – as you might guess – this works just fine here in any scenario

your version of the postcode plugin is still 4.0.23 (April 2019) so first of all i would suggest updating it to the latest version (currently 4.0.28 / April 2020)

all of what you are saying is correct.
the changes are also quite deliberate and furthermore are specifically mentioned in the changelog of the plugin

as of v3 of the plugin , you cannot say as “soon as possible” anymore if the shop is *not* open at that specific time
so the customer is forced to make a selection when the shop is closed actually closed

this is actually a good thing, and based on feedback of this being an issue in the previous version, as people will not expect an order to be delivered in the next 30 minutes (or whatever your normal delivery times are) and then complain to you that they never got their order (which you would not be able to fulfill of course as you were closed at that time)

The only scenario now when “as soon as possible” can be applicable – but you’ll have to specifically enable this now in the plugin settings/options- is when your shop is actually open at that time so “asap” can actually be something sensible (like in the next 30 minutes or as soon as you are able to , within reason

PS: It was also marked as a major update by virtue of increasing the plugin version from v2.x to v3.x

>Would I be able to use this extension to offer gift cards to customers?
No, not really. Sorry.

>Is there a better solution?
To my knowledge at least , no such thing exists as of the date of writing this reply I’m afraid
(unless someone else has developed this , but I’m not aware of this being in existence)

As mentioned, this looks like it went wrong when you did the upgrade,
so i would suggest you do that again (with plenty of memory) and check your debug.log to see if there were any fatal errors

if that all goes to plan, you could afterwards make a backup of your wppizza_orders and wppizza_meta tables
and then perhaps delete all the orders in there that are 2 or more years old (are do you really need permanent access to orders from 2 years ago ?)

the memory exhausted error you are experiencing is most likely caused by the dashboard widget and when going to the reports page as both of those need to get information from every completed order to display their (total) values

as mentioned, there maybe a way to somewhat get this memory consumption down a bit – and i’ll look at that in the near future – but for the time being, if you have lots of orders , it will consume quite a bit of memory when generating the reports/dashboard info (though the dashboard info is cached up to a point)

>but thought I’d ask!
sure, no harm done
but no, it doesnt do that and there are no plans to implement that from my side

sounds to me like your upgrade from v2 to v3 went wrong
especially if you already have a lot of orders and perhaps lots of other plugins running or a theme the consumes lots of memory itself, you will need LOTS of memory during the upgrade as the upgrade has to go through every single order in the db and change values to make this work…

>Furthermore it is not recommended to set the memory limit that height.
that’s also an arbitrary comment by someone that has no foundation in anything as memory needs will always depend on a list of many things
(though I am aware that the wppizza dashboard widget can be looked at to perhaps get the memory requirements down a bit when it updates every hour or so)

that should actually be automatic (but i checked this here and it isn’t in all cases/setups i noticed)
i’ll update the plugin to that effect , no problem

thanks for flagging it

the last function documented here might give you an idea
https://docs.wp-pizza.com/developers/?section=create-your-own-sales-report