>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

Can you post a screenshot of your postcode plugin options/settings please

Option 1: you name the ingredient accordingly. i.e call it “ohne Olives” in the first place
(you may want to also then enable option: ‘Omit “1x” in cart, order and account history?’ – though the 1x is still shown initially when choosing. I may look into this at some point )

Option 2: The much easier option is to simply add a textfield ( custom groups => add textbox to item) where the customer can write this sort of thing.

PS:
Personally I always found Option 2 above complete overkill (and it would not make the administration of it all any simpler). I believe it only manages to confuse people and is only really that useful for some specific situations.
Customers (most of them anyway) are quite capable to say if they do not want something from a menu item (or perhaps they should order something different to start off with – but that’s somewhat academic here).
Just my 2 cents worth though

The choice is yours of course

Ok, so:
Elementor adds lots and lots of surrounding elements to the orderpage widget (about a dozen or more)
Interestingly, after payment (i.e on the so-called “thankyou page”) it does not add those wrapper elements anymore.
Why ? I have no idea.
That said – given the popularity of elementor – I’ll have a look as to whether it’s something they should perhaps be doing or I should perhaps be doing and/or find a workaround/fix if applicable. I simply do not know yet where the issue is exactly
so will probably not be something that can be done quickly as it may have many implications elsewhere.

That said, if the only page where you are having issues is your thank you page, there is certainly an easy fix by simply adding the following (adjust as required) to your css somewhere (see https://docs.wp-pizza.com/advanced/?section=frontend-css-styles-layout). This is a very specific override to that widget there so should be quite safe to use

.wppizza-order-wrap-thankyoupage{
padding-top: 100px;
margin: 0 20%;
}

PS: if you enable debug on your site you will see that elementor throws lots and lots of database errors. which may – or may not – be related. Just mentioning it though that really is something for them to fix.

That’s it from me for now on this subject