Forum Replies Created
-
AuthorPosts
-
personally – although that’s just my preference – i would create distinct menu items to start off with anyway as opposed to making people click on things several times, just to add some milkshake or fanta
i.e i would have a menu item “cola” another “fanta” another “banana milkshake” etc etc. so the customer just clicks on cola and adds it to the cart without having to jump through hoops…
(i.e just like your “mineralwasser”, “orangensaft” etc)again, just personal preference, it’s entirely up to you of course
i’m confused. that’s exactly how it is.
looking at the folowing“alkoholfreie getraenke” has the following toppings
banane, cola, erdbeer, fanta, schoko, sprite , vanille
(https://i.imgur.com/BJY9euH.jpg)there you assigned “cola fanta sprite” to a custom group .
they appear in a custom group under “getraenke” here http://i.imgur.com/8kNYJFC.jpgthe “leftovers” (i.e banane, erdbeer etc) appear in the standard group labelled zutaten fuer 0.00)
so the “cola fanta sprite” have been taken out of the standard group – as statedif you do not want to show banane, erdbeer etc there , you have to exclude them in a separate exclusion group
alternatively – and perhaps better – assign/create a wppizza->size for your milkshakes and another one for your other “drinks” and only add banane, erdbeer etc to your milkshakes and the others to the “drinks” (if you do that , you do not have to mess around with exclude groups)
all a matter of how you set it up
not sure what you are seeing i’m not seeing or perhaps missing ?!
so for example for this item here
http://i.imgur.com/oHITwgI.jpgyou probably want to create an additional “exclude” group and assign “cola, fanta and sprite” there to that same item so those 3 do not appear as selection for your milkshakes
as in the help/howto described somewhat:
you are creating a “pool” of ingredients associated with each “size group”
if your menu item belongs to that “size group”, all of those toppings belong to that menu item.you can set “custom groups” to manipulate individual groups of those topping .
any topping not in any custom group, will stay in a default groups (unless specifically excluded by an exclude group)you misunderstand how this work.
all ingredients you have set under “ingredients” will be applied to ALL menu items in that group/size (provided of course add ingredients is enabled for a particular menu item)
if any of the ingredients are NOT in a custom group, they will be in a default group (i.e labelled something like “ingredients for x.xx”)
you should probably create a “drinks” size to start off with, add all your drinks to that group and then add ingredients (flavours i guess) for your drinks……
alternatively (or additionally, depends on your scenario) you can also set additional “exclude” groups to – well – exclude toppings from specific items
huh ? what do you mean by there is “no way to remove / add toppings” ?
that’s the point of the whole thingi must be missing something..
re 1: just set the relevant restrictions in the custom groups
re 2: if you want to add a menu item as ingredient, you’ll have to add it as ingredient
have a look here https://support.wp-pizza.com/twentytwelve/ at the “pizza half and half”.
hawaiian, italien, sicilian etc are just added toppings (just change these to the pizzas you want to be able to choose from)you seem to have assigned things to the wrong item
http://i.imgur.com/IV0vQHt.jpg -> “assign to the following menu item” is set to “14 chicken doener teller”
http://i.imgur.com/R6O0eYS.jpg -> frontend of “01 doener kebab”
i.e your custom group is assihed to “14 chicken doener teller” . and not to “01 doener kebab”
> is there any possibility to set different opening hours for self pickup
at the moment. no (not without hacking things in various places and adding a bunch of filters/action).
perhaps in version 3.x , but that is a while away yet.
i’ll make a note of your request though. maybe i can reasonably easily make that do-able in v3.x but I cannot promise anything>i would also like to have a different shop style
that’s what themes are for . wppizza provides the functionality (and some basic layout options of course). However styling is really the responsibility of themes though most of it should quite easily be accomplished with a few css declarations added as neededto start off with , i would need a link to your site please
thanks
>Yes i have enabled shop and bccs
but you have not selected the “shop and bccs” for the template you want to use but it’s still selected for the standard template.
just activate the licence in the cloudprint “license” tab of the plugin and it will automatically show up
you are right actually.
I was convinced it uses the templates sent to the shop as set up.
However, having had a look at the code, it always uses the template in the templates directory.I will change that, but this might take a few days…
the cloudprint plugin just prints a copy of the order you send to the shop.
so however you have set up the templates (wppizza->templates -> emails : shop/bccs) , that’s what cloudprint receives
>Maybe that’s the reason
might well be
did you set the Silent url ?
see setup here
https://support.wp-pizza.com/downloads/wppizza-payeezy-gateway/if so, enable logging (if you have not done so yet) in the gateway settings and check if there are any logs in the logs/ directory of the plugin (after logging is enabled of course and you have done a test order)
sounds more like you did not enable it .
check your layout settingsand what about the customers that actually want to order something >100 ?
if you really worried about fake orders, only accept pre-payment by credit card.
very simple and very effectivefurthermore, I believe you are trying to find a solution to a non-exiting problem as I have not heard of one user of wppizza that had this problem as the user has to physically click on things in various places to even be able to add anything , then add order details etc etc – i.e behave like a normal customer
although i suppose you could hide some of the dropdown options with some css or javascript
-
AuthorPosts
