1) I do not think this will be implemented into the plugin anytime soon (probably never)
However you could use the wppizza_shop_is_open filter to close thet shop for orders (pre or not) between required times
something like :

add_filter( 'wppizza_shop_is_open', array( $this, 'myprefix_force_shop_closed'), 101);//minimum priority of 101 or higher 
function myprefix_force_shop_closed($bool){
/*you need to do the between time conditionals here as required */
if([between date/time a and date/time b]){
return false;
}
return $bool;
}

the globally available ‘wppizza_openingtimes_formatted()’ function might be helpful for the conditional

2) Simply enable->save the “Close Shop Now” in wppizza->openingtimes. this will override anything else

3) I believe is now fixed as of Preorder – v3.13
(I’m sure this worked in the past, but appears I’ broke it at some point, so thanks for the report)

Hi

Your website referenced is running an (almost) 4 year old version of wppizza (3.13.7 , current version being 3.19.6) which of course all other wppizza add-ons depend on.
Furthermore , your wordpress version – as well as a multitude of other plugins – are about 4 years out of date.

Please make sure your website (wordpress/plugin/themes) is up-to-date first of all.

Of course let me know if there are still any issues once this is done.

Just to say I’m not ignoring you and am in the process of implementing the NotifyURL stuff here.
Need to do some more testing though. Hopefully available later today or tomorrow, depending on how it goes.

Although the NotifyURL is certainly a good idea to avoid above scenario (and I’m a bit puzzled why I did not implement this to start off with to be honest, but may be down to the state of things at the time….who knows), the customer will never have received an order confirmation from the shop (he was not charged either) and I cannot see how the order would have been marked as “complete” . Furthermore “authorised” does not mean “failed” so I do not understand what you are referring to in your post.
Of course I understand the issue and the above is all academic really, as it will be addressed with this next update in any case.
Thank for pointing it out .

>Would you be able to implement this change?
Sorry, but I do not offer customisations (please see: https://docs.wp-pizza.com/faqs/?section=customisation)
Furthermore, what you are describing is not exactly something that could be implemented in a couple of lines of code, so even if I were to offer customisations, I can guarantee you you would not like what I would have to charge for a one-off thing like this.

I could add a filter to the postcode plugin that could then be used by someone to filter code availabilities/validities depending on whatever conditions you want , but that’s as far as it goes I’m afraid.

PS: you can work around this one for the moment by copying one (or many) of the other ones and renaming them from “abz (copy)” to what you then need

sorry, I got confused with a different topic that’s about a different kind of redirect.
I’ll have a look..

wrong place.
That particular one is set in wppizza->layout

am not going to bore you with the details why that was moved there , though maybe something to look at again at some point as this was done years ago, but for now, it’s there

>Was referring to my old theme…
Ok, thanks for the clarification.

>Almost every commercial theme…
It’s not actually themes themeselves – or indeed woocommerce – that were the issue, but elementor (as you know of course)
but I’ll spare you the details as it’s quite irrelevant now

>Oh my God…that fixed the problem!
Glad to hear it

>I spent hours trying to solve it somehow and you have fixed it now
Only possible because you provided the info and details I asked for . So you can thank yourself too 😉

Don’t cry. It’s almost xmas. Time to rejoice and all that and if you have any more / other issues, get in touch. I cannot fix or amend things if I know nothing about them

Cheers

As of 5.3 of the postcode plugin the redirection should work (again)
furthermore – as mentioned above in this thread – there is also now a ‘redirect’ attribute added that can be used in the shortcode (see https://docs.wp-pizza.com/developers/?section=delivery-by-post-zipcode).

Hope that helps

Has nothing to do with wppizza. WPPizza does not set image sizes like that.
it only ever gets the thumbnail depending on what’s set as thumbnail sizes
and generates and outputs something like this:

<img width="64" height="64" src="http://[somedomain]/wp-content/uploads/2022/08/pizza-64.png" class="wppizza-article-image-thumb wp-post-image" alt="" title="Special Pizza" />

your theme – or some plugin – generates this:

<img loading="lazy" decoding="async" width="768" height="768" 
src="https://[somedomain]/wp-content/uploads/2024/10/pizza_pomodori.png" 
class="wppizza-article-image-thumb wp-post-image" 
alt="" 
title="Pizza POMODORI" 
srcset="https://[somedomain]/wp-content/uploads/2024/10/pizza_pomodori.png 300w, https:/[somedomain]e/wp-content/uploads/2024/10/pizza_pomodori-150x150.png 150w, https://[somedomain]/wp-content/uploads/2024/10/pizza_pomodori.png 768w, https://[somedomain]/wp-content/uploads/2024/10/pizza_pomodori.png 1024w, https://[somedomain]/wp-content/uploads/2024/10/pizza_pomodori.png 800w" 
sizes="auto, (max-width: 768px) 100vw, 768px">

you will also find that where your images look the right size the last declaration is

sizes="(max-width: 768px) 100vw, 768px"
instead of
sizes="auto, (max-width: 768px) 100vw, 768px"

i.e whatever generates the “auto” is your culprit. Only you will know whether that’s a theme or plugin. I can guarantee you though it’s not wppizza