haven’t yet checked this in detail, but my guess would be it’s because “Multi-Apply” is off.

i.e if it’s off, it only applies this to the first time the condition is met .
in your described case that’s for your 3 pizzas that are below the minimum price set, in which case the discount applied will be zero (as it’s no discount at all if you charge a fixed price of 3 x 4.49 as opposed to the “natural” 3×4.19)

as the condition was met, subsequent conditions met will be ignored.
If you enable “multi-apply” then it will consider ALL instances of the condition met.

Again, haven’t yet checked in detail, but I would expect that to be the issue at hand

not at the moment, but i;m hoping to get to have a look at this in the next week or two

what version of wppizza ?
have you tried (re)-saving your additives ?
what other wppizza related shortcodes (if any) are on that page ?

that’s pretty much what the “print” button is for that you can find in “Wppizza->orderhistory”
the output generated will depend on your settings in “WPPizza->templates->print”

i dont know much about german tax law, but presumably you need to include the values/tax rates etc related to an order, all of which can be selectively added as required in those template settings

PS: as it happens, i am also in the process of actually developing a little plugin that would allow you to selectively add a pdf invoice to any emails the system sends (the output of which is also depending on settings in wppizza->templates->print)
but that is a few days or so away yet from release

In essence, you found some old codesnippet (somewhere on here i guess) that was related to wppizza v2.x.
The “official” documentation – if you will – for v3.x can be found here https://docs.wp-pizza.com/

That said, not all the snippets that were mentioned here on this forum in the past have yet been copied/updated there (some do not even exist in v3.x anymore anyway but were accurate at the time before v3.x).
The docs will always be work in progress I suppose and will be amended on “as needed” / “as requested” basis.

In any event, the error you were getting is “correct” in so far that in v3 only 2 arguments are now passed on as the 2nd one contains all data now that was previously passed on in the additional arguments (there were actually 7 altogether)

So cutting a long story short: yes, there are now only 2 parameters so the filter should indeed be something like

add_filter( 'wppizza_filter_orderhistory_order_info', 'my_function', 10, 2);
or
add_filter( 'wppizza_filter_orderhistory_order_info', array($this/*or some distinct class*/, 'my_function'), 10, 2);

I hope that clears things up somewhat

cheers

I dont know what you did of course, but my *guess* would be that you simply doubled you lunch menu (with different soups as required) and enabled/disabled the relevant “lunch menus” for the given days
(ingredients themselves are not “timeable” so to speak)

other than that I can only suggest you look at how you did this on that “other ” site

> it seems that cloudprint can accept a parameter of zero margin.
all the wppizza cloudprint plugin does is send the order to cloudprint based on the template (settings) you have selected . it really is between cloudprint and the printer itself to do what you want it to do .
This is nothing the plugin has control over.

furthermore, the links you posted seem to refer to the settings of the device itself , not any parameters you can send to it to dynamically change them . not from what I can see anyway

>This snippet at Stack exchange ….. Seems to be trying to pass the parameter.
it also says there that it does not work

please also see here. maybe you can get some ideas from there as a workaround perhaps
https://support.wp-pizza.com/topic/question-google-cloudprint/

generally speaking, how things are printed once the order has been sent to cloudprint is entirely the printers responsibility. if it does not print margins (for example) then you will have to speak to the printer manufacturer . only they will know about this