you’re welcome

one more – unrelated – thing . as the theme you are using is somewhat responsive, the following might or might not be useful…..just an idea. your call of course

https://www.wp-pizza.com/topic/making-the-default-css-responsive/

i’m somewhat understanding the issue i believe.

however, there’s something quite strange (superflous) going on from what i can tell

staying om the same page (http://scoopsdelivers.com/locations/scoops-allendale/)

you have only 2 different price groups / meal sizes

a) one size (cookie sundae, cookies, nachos (? nachos with snickers ?)
b) small , medium , large (flurries, shakes , sundaes)

staying with b) here.
the chocolate option has a different id for the flurries, shakes and sundaes respectively .i.e it appears – and from what i can read above – you entered all those toppings 3 times. …..why ?

if flurries, shakes and sundaes are all supposed to have the same set of toppings, why are they entered 3 times . any particular reason i’m missing ?

having said that – and more particularly in answer to your initial question – every topping as you know has its own id.
so if you have 2 groups (“one size” as well as “small,med,large”) than the css will have to be set for those toppings in each group individually (again, because the name might change for example).

however, if you only have 2 distinct different groups (as you should have from what i can see – again at least just talking about this page – it really should not be that time-consuming/tedious to add a couple of css declaration.

so, in short, you have to set the css per id/class but i think the tediousness you are referring to comes from declaring too many unnecessary meal sizes

>but that way would have me search for each ingredient class

its just a right click->inspect element (on chrome ) or similar to get that id .no ?

more importantly (taking the shakes and sundaes here – http://scoopsdelivers.com/locations/scoops-allendale/ – for example )

having had a quick glance (I might be wrong though) both seem to have the same set of ingredients/toppings and respective prices.

if that is the case, I must admit i dont even understand why you have the same set of ingredinets/toppings 2x as opposed to reusing the same lot

(again, that’s just after having a quick look, i might have missed something here of course)

sure.
every ingredient is wrapped in an li element with the appropriate class (such as class=”wppizza-ingredient-22″ where the 22 refers to whatever ingredient has the id 22)

just use whatever css declaration you need to display whatever image you want

> since the sorting happens by the itemnr.

no, the sorting happens by order number ….

actually , i need to check something. not quite yet available

i wasn’t actually going to do much about that anytime soon to be honest.
however, messing around with things a bit, i actually found a bug here that’s somewhat related to the whole textbox thing.

no promises, but i see what i can do

incidentally, i just installed “wp super cache” here locally which I have absolutely never ever used before, and it took about 2 minutes to get this working…..

something isn’t right your end….

now be available as an option in wppizza->settings in v2.10.4

Hi

for starters, this is only an issue really if you are actually linking to *single* menu items as – when using shortcodes/categories – the url will be whatever the page is named and the menu items will be displayed on that page according to the shortcode and/or category chosen

if you do however link to single item pages (i assume you’ve edited the templates or using the search as – by default – there are no links to single menu items anywhere, you could use the inbuilt filter to change this in your themes function.php like so

add_filter('wppizza_cpt_args','my_wppizza_cpt_arguments');
function my_wppizza_cpt_arguments($args){
/**change single item post slug from wppizza to myslug (should be translatable)**/
$args['rewrite'] = array( 'slug' => __('myslug') );		
return $args;
}

you will have to re-save your permalinks once

having said that, i agree that this should be an option to set in the plugin, but until now I haven’t got round to it, as it wasn’t really required much. (as i mentioned , in most cases single item pages aren’t really necessary and on top of that you would have to mess around with single post templates to make this play nicely with your chosen theme)

furthermore, the code above hasn’t really been tested as yet , so – at the moment – use it at your own risk as there might be something I have as yet overlooked that could screw things up….

Either way, if you do use it , let me know if you experience any problems. I’ll do some testing myself which essentially would do the same thing except that it would be editable in the plugin itself.

However 2 sets of eyes are better than one so any issues you find, let me know

thanks