although i suppose you could hide some of the dropdown options with some css or javascript

>menu drop downs don’t work.

because there is nothing to order (right now anyway)
if you go here
http://foodking.co.uk/sthelens/menu/burger-king/
you’ll see there’s no item that could possibly be ordered, so no link to any of the pages show up in the nav menu

that’s deliberate and not something that “doesnt work”

there are various issues here:

a) yes, i did have a think about adding some sort of loop/item template editing in the past and something might make it into wppizza v3 (which I am doing at the moment). And perhaps something like adding template_type=default template_id=3 to the shortcode might be doable…that will become clearer at the time.
That said, there always tend to be some surprises when one is actually doing things that suddenly make options that seemed good ideas in theory, impractical in practice. We will see on that

However:
b) adding a textarea where you can add some html which then wraps some other html not only seems strange to me (why not just edit the underlying template in the first place )
but will also not work as I believe you think it works as – in the case of the default layout for example – there is a lot of nesting of elements going on. Not to mention that SKU’s are dynamically generated and inserted. (amongst a bunch of other things ) .
Maybe you want to use the grid template to start off with though, where the sections are quite distinct, and edit that one.
Furthermore, there are already an absolute ton of classes and id’s added you could be using to do your layout as opposed to wrapping elements in yet more elements

c)

I’d much rather prefer that you control everything in the source code than me

Me too, but if you want to customize things for your “one-off” scenario than that’s something that you have to do

d)

there is the risk that it could be overridden or things have changed.

ignoring here wppizza v3 (a lot will change there , but there will be ample warning when we get there and is months away yet anyway).
Why would there be a risk that stuff gets overwritten (assuming you are not editing corefiles which you should not be doing of course)?

I thinks that’s it for the moment from me here in a “off the top of my head” kind of way

PS: I totally agree that css is not what you want to use for hiding things here !

sure, as long as it’s not disabled (which is the point of the timed menu)

i.e if menu item disabled -> no order during times it’s disabled . preorder or otherwise.
at other times, item behaves like all other items

you can if you want, but
a) it doesn’t do anything as it is, you will have to write some code
b) things like WPPIZZA_EXTEND_CUSTOM_JS ,wppizza_extend_custom_js, the plugin name , description etc should probably be something more descriptive.
c) (i just updated the code in a couple of place) replace the “myprefix” with something sensible

PS: i don’t even understand why your farmer would want to restrict this in the first place, but then again I do of course not know the exact details as to why this sort of thing might be desirable..

did you enable any of the radio buttons there so it is actually used ?
(such as email recipients: shop and bccs and/or customer and/or additional recipients)

see also the help tab at the top right of the screen for more info on those

sorry, but you have chosen to work with a 2 year old version, while (it seems) updating WP.

the plugin gets updated not only to add more features but also to fix bugs and make it play nicely with new versions of wordpress.

if you do not update the plugin but WP only, you run the risk of things breaking. there isn’t anything i can do there.

that said, because you have not updated, the most likely problem is your db is using an outdated scheme/collation so you should fix that (see here https://support.wp-pizza.com/topic/error-sorry-we-could-not-find-this-order-2/)

regarding your install trying to connect to root: this has nothing to do with the plugin but is somewhere in your setup