Just out of curiosity, I had a dig around. So below some comments which may (or may not) be helpful
Not exhaustive research though. Maybe it helps someone somewhere.

>If I upload the pictures directly it seems to work.
Yup. If you upload pics the regular way with wordpress, it generates 4 distinct separate images scaled and/or cropped.
exmage-wp-image-links (other/similar plugins may do the same) simply uses the image you added which then gets resized via css and image attributes. No actual resizing/cropping is taking place.
Since WP 6.7 WP adds the ‘auto’ attribute – if it’s missing and in certain circumstances – to the image sizes attribute.
So if the actual (thumbnail) image is meant to be square – but the actual image is not – it will simply be distorted to make it square.

As it turns out, you can actually turn this off with the filter below, but this might have implications elsewhere.
I did not want disappear all the way down that rabbit hole – so if you do that , make sure to check all your images / pages .
Perhaps it works or perhaps it’s just a starting point . All depends on your particular site setup and many other factors. Suffice to say, it’s out of my (wppizza) hands and evidently something that WP introduced to the detriment of these kind of plugins…

//remove auto from image sizes attribute (if set to lazy) 
add_filter('wp_img_tag_add_auto_sizes', 'myprefix_img_tag_remove_auto_sizes');
function myprefix_img_tag_remove_auto_sizes(){
return false;
}

Forget the screenshot.
I think there’s simply a misunderstanding here. From what I can see, this works all just fine and as intended.

A few things:

>When selecting the pick-up option, the “Our Menu” page does not appear as expected.
From what I can see (correct me if I’m wrong) you put the wppizza_dbp shortcode on your homepage.
If you put it on a page that does not have a cart/menu item on there it simply sets the choices made by the customer in the background so a subsequent visit to your wppizza menu page will take this into consideration. Nothing other than that will happen .
The idea of the shortcode is to offer an alternative to the popup (plugin settings). It cannot have any idea if or indeed where you want to redirect to.

That said, there’s of course always the possibility that I misunderstand the problem you are referring to. If so , let me know.

Furthermore, thinking out loud here , perhaps I could add an attribute to the plugin short code options in th enext update that would allow you to set a redirection pageid or something when the “OK” was clicked.
I’ll think about that

>However, the new version has more problems than the old one
How so ?

there is no such thing.
wppizza is a regular wordpress custom post type which is therefore adding it’s db entries in multiple tables alongside other db entries.
However, wppizza does not really care about themes (unless you customised them somewhat in which case I would recommend the paragraph here regarding portability https://docs.wp-pizza.com/developers/?section=filters-actions-functions) so you can simply switch between themes as you wish – though themes will need their own setup of course

> the pre-selected items are already the main ingredients
in which case they should not be an additional selectable ingredient .
E.g a (typical) Pizza Margharita is a pizza topped with tomato, mozzarella, and fresh basil.
Unless you want the customer to be able to add “extra mozarella” – in which case you would add an “extra mozarella” ingredient – it would simply not be available as an add ingredient (you would probably want to write “pizza topped with tomato, mozzarella, and fresh basil” in the product description instead though)

out of curiosity, if you want to make a duplicator package available for me somewhere, I can have a look (i assume you know what i am talking about)

as you are using a commercial theme I can only advise you to the usual troubleshooting as per
https://docs.wp-pizza.com/troubleshooting/

if you disable all plugins except the main wppizza one and only get the issue with the theme you are using but not any default theme , you will have to speak to the theme author.
I will not be able to advise you as to what your theme’s issues may be (as it is commercial, I will not be buying it as i have no use for it)

PS: You should make sure to also check your javascript console too for some clues

>but the widget loads in an empty Theme site
what widget please ?

That said, if you are using the “Avada” theme, then the fault is there and they need to fix this – they know about this but seemingly refuse to do anything about this .
(Regardless of what they say, they are simply using the ‘the_content’ filter multiple times on the same page – with the results you can see )

that would indicate you either have a serious issue somewhere (see your debug.log – https://docs.wp-pizza.com/troubleshooting/ ) or you have been/are caching your pages (or both)

Just for info:

It appears that WP 6.7+ does not want to read two text domains in the same plugin (anymore).
The wisdom of that escapes me, but alas this is what it seemingly is.
The good thing is – talking about wppizza related stuff – that this only affects the main wppizza plugin.
All/any wppizza extensions should be unaffected I believe.

I’ll see if I can still somewhat keep admin and frontend translation files separate in a different way and will release an update asap.
Worst case scenario, I’ll have to merge the 2 language files – which would not really be that dramatic, just a bit of a nuisance

We’ll see how it goes. I would think it will all be good again in the next few days – allowing for some testing .

Thanks for the heads-up (for temporary workaround see above)