having had a quick test here, i get the same result (i.e multiple checkout pages if using that shortcode on the order page)
as – in large parts and for consistency – that particular shortcode uses the same coding as the actual orderpage I really do not know if this is doable, but i’ll give it a go but as mentioned I cannot tell you when or if this will be possible I’m afraid…

ok. thanks for narrowing things down
the shortcode [wppizza type=orderhistory] is really designed to be on its own page.
that said, i can somewhat see why one might perhaps want this to be on the orderpage too (though generally – in myopinion only though admittedly – once a customer is on the orderpage I am not sure if it’s such a great idea to confuse the customer with more stuff on the page that might stop him/her from completing the order right there and then . again, just my 2 cents)

In any event, i’ll see what i can do. it will have something to do with some ajax call executing multiple times, my guess being you get 3 times that page if you had 3 previous orders, 4 times if you had 4 previous orders and so on

Cannot give you an ETA though right now when (or even if) this will be doable I’m afraid

You won’t find it in the “WordPress Environment” or in any directory. That’s not how WordPress filters work .
You must familiarize yourself with this

see here for a starting point
https://docs.wp-pizza.com/developers/?section=filters-actions-functions
– or in fact any WordPress actions/filters tutorial you can find with a quick search

(at the most basic level, the filter/code above belongs into your [child]theme’s functions.php )

simply go wppizza->reports , set the range you want and export
(PS: I am aware that – currently – the Range selector dropdown at the top left on that page only works when using the keyboard and not when using the mouse to select from one of the available options. That will be fixed in the next update of the plugin)

Sorry,but I dont understand what exactly you mean by “manage the user directions” (looking at your IP i assume you are referring to a user address ?! )

what exactly are you trying to manage ?

it really all depends on the amount of content you have and the device used (i.e ratio / width the screen has)
i dont know anything about the Mate20 Pro.
However ,having played with a few things, it seems to me it has a width of about 430 or so

i can see 2 options.
a) the media queries in the original css kick in at 420 i.e it’s set to do

@media only screen and (max-width: 420px){/* css stuff */}
you could change this to 440 for example (or something around that number). i.e
@media only screen and (max-width: 440px){/* css stuff */}
and the whole reshuffeling of things will occur earlier

another option would be to restrict the width that the title can take up , before it starts to linebreak
so, something like

@media only screen and (max-width: 440px) and (min-width: 420px) {.wppizza-article-h2{display:inline-block; max-width:120px}}

or similar – you’ll have to play with it a bit and or target only the items/categories where you need it

(or – as mentioned previously – use the “responsive style” layout to start off with which will eliminate a lot of this messing around. But I understand that you might not want to do that of course. )

PS: I would also suggest you add the float: none !important; i referred to earlier in this thread to center things under 420
but that’s up to you (if you dont like it centered that also just fine of course)

coming back to the added css i suggested , you might even want to add this
float: none !important;
so the whole thing would read like this

.wppizza-article-default .wppizza-article-sizes { position: absolute;top: 0;right: 0;}
@media only screen and (max-width: 420px){
.wppizza-article-default .wppizza-article-sizes {position: unset !important;float: none !important;}
}

that will keep th eprices centered on small screen devices (if you want that). obviously , you can tweak this as you wish

>I’ve rolled back to a backup before the update, so that you can see, how it was and I want it to have in the future as well
the thing is, i dont think you want it like that .(hear me out)
have a look at it on a small screen , you will see that yoru prices are *above* the title.

i have had quite a few reports where people ordered the wrong thing becuase they clicked on the price BELOW the title assuming – as would be pretty much expected throughout any ecommerce site – that the price below belongs to the title above it.

this is precisely the reason why this got changed ……

if you use the new version and add the below as the last of your custom css

.wppizza-article-default .wppizza-article-sizes { position: absolute;top: 0;right: 0;}
@media only screen and (max-width: 420px){
.wppizza-article-default .wppizza-article-sizes {position: unset !important;}
}

you will get the benefits from the above problem not happening on small screen devices , plus your “original” so to speak (i.e desktop/bigger screens) to be unaffected….

i.e you are doing

.wppizza-article-default .wppizza-article-additives{ display: block; /* etc */}
if you do/revert to
.wppizza-article-default .wppizza-article-additives{ display: inline-block; /* etc */}
additives are next to the title (as they are by default) and things dont move around all over the place

if you DO want the additives to be below the title (i.e keep the display:block)

then you could *add* this
.wppizza-article-default .wppizza-article-sizes { position: absolute;top: 0;right: 0;}

BUT MAKE SURE you reset/remove this one again below 420px (as that’s where the media query kicks in that moves things underneath each other to cater for mobile devices )

>But with the custom css it worked very fine over a year and some updates
sure , as unless it is strictly necessary (and in this case it was unfortunately) , i do not change these kind of things

that aside.
i get a a ton of javascript errors on you site (you have done something like this <!--?php . that’s really not a good idea as it will still be read and parsed in all sorts of places)
i suspect you did that to disable your custom css (as i asked , and thanks for that)
However, looking at what we have now, i think it will be better in this case if you just leave things as you had them – including the css you were overriding – and I will see if i can come up with a line or 2 of css you can additionally add (or change) to get you back to where we were from a layout perspective