1. Modify Css / Styles / Layout
    1. Layout (Menu Items, General)
    2. Frontend Css
    3. Admin Css
  2. Templates
    1. Pages
      1. page.order.php
      2. page.confirm-order.php
      3. page.processing.php
      4. page.thankyou.php
      5. page.cancelled.php
      6. page.purchase-history.php
    2. Order
      1. itemised.php
      2. summary.php
      3. transaction_details.php
    3. Global
      1. orderinfo.php (Widget)
      2. openingtimes.php (Widget)
      3. additives.php (Widget)
      4. navigation.list.php (Widget)
      5. navigation.dropdown.php (Widget)
      6. search.php (Widget)
      7. totals.php (Widget)
      8. pickup_choice.php (Mixed)
      9. login.php (Module)
      10. profile.register.php (Module)
      11. profile.update.php (Module)
      12. pages.pickup_note.php (Module)
      13. formfields.inputs.php (Module)
      14. formfields.values.php (Module)
    4. Cart
      1. cart.container.php
      2. cart.shopclosed.php
      3. cart.empty.php
      4. cart.pickup_note.php
      5. cart.checkout_button.php
      6. cart.empty_cart_button.php
      7. cart.minimum_order.php
      8. minicart.php
    5. Loop (Menu Items)
      1. header.php
      2. no_results.php
      3. posts.title.php
      4. posts.thumbnail.php
      5. posts.prices.php
      6. posts.content.php
      7. posts.permalink.php
      8. additives.php
      9. pagination.php
      10. theme-wrapper.php
    6. Search Results
      1. search.php
    7. Single Menu Item
      1. single.php
    8. functions.php
  3. Filters, Actions, Functions
    1. Global WPPizza functions
    2. WPPizza options (Filter)
    3. Currency (Filter)
    4. After every order (Action)
    5. Getting orders (Function)
  4. Constants
    1. Admin Name
    2. Admin Menu Icon
  5. Codesnippets
    1. Create your own sales report
    2. Order history - todays orders
    3. Email/Print templates
    4. Email Subject Line
    5. Add attachment to email
    6. On order status update
    7. Unconfirmed orders
    8. Customise order id
    9. Changing post type arguments
    10. Gateway filter frontend
    11. Users previous orders
    12. Dynamic menu item prices
    13. Update prices in bulk
    14. Prices output loop
    15. Pickup opening times
    16. Checkout Formfields
    17. Additional validation function
  6. Extensions / Gateways
    1. Add Ingredients
    2. Autoprint
    3. Confirm | Reject | Notify
    4. Coupons and Discounts
    5. Cross-Sells
    6. Delivery By Post/Zipcode
    7. Goodcom Printer
    8. Mailinglists
    9. Pdf Invoices
    10. Preorder
    11. Gateway - Stripe

1.2.Frontend Css / Styles / Layout

Although the css has been written so that it works with many themes out of the box (see – all themes use the same default stylesheet) it is also deliberately kept quite bland.
So the chances are, you will probably want to adjust some things (i.e css) here and there to work and fit in with your particular theme.

There are several option you have if you want to do this (for your own sanity, I would suggest you use just one of them and stick to it for any changes you need to make now or in the future):

  • Option 1: if the theme you are using provides an option to enter your custom css somewhere, you could enter your additional css declarations there
  • Option 2: you can add your custom css in WPPizza ->Layout -> Custom CSS. If your webserver permissions allow it, adding declarations into that field will create a file named If writing permissions are missing, inline css will be generated instead. (ensure you are entering valid css)
  • Option 3 (see below): you can use a dedicated wppizza.custom.css file or completely replace existing WPPizza css files with your own

Option 3 Details: using dedicated css files – using wppizza.custom.css to only override selected declarations

  • CREATE the following directory structure in your child theme: /[absolute]/[path]/[to]/wp-content/themes/[my-child-theme]/wppizza/css/
  • CREATE a file called wppizza.custom.css in that directory (or copy it from wp-content/plugins/wppizza/templates/css/ to that directory)
  • ADD your required css declarations to that file (wppizza.custom.css will be read AFTER all other wppizza css files)
  • make sure WPPizza -> Layout -> Style -> Include CSS / Stylesheet is still checked/enabled
  • Note: wppizza.custom.css will only be read if it resides in the above mentioned directory. simply editing wp-content/plugins/wppizza/templates/css/wppizza.custom.css in place will not work

using dedicated css files, completely REPLACING selected css files

Note: As it is possible (using the relevant shortcodes) to use different layouts for different pages (or indeed each category displays), the WPPizza frontend css used consists of more than one file.
Namely :

  • [plugin-path]/wppizza/css/wppizza.css (main wppizza style)
  • [plugin-path]/wppizza/css/wppizza.default.css (selected declarations when using default style)
  • [plugin-path]/wppizza/css/wppizza.responsive.css (selected declarations when using responsive style)
  • [plugin-path]/wppizza/css/wppizza.grid.css.php (selected declarations when using grid style – note: this is a php file to account for dynamically setting gridsizes etc! )
  • [plugin-path]/wppizza/css/wppizza.rtl.css (if the current language is rtl)

if you want to overwrite any or even all these completely:

  • CREATE the following directory structure in your child theme: /[absolute]/[path]/[to]/wp-content/themes/[my-child-theme]/wppizza/css/ (same as above)
  • COPY any/all of above mentioned files from [plugin-path]/wppizza/templates/css/[one of the files above] to /[absolute]/[path]/[to]/wp-content/themes/[my-child-theme]/wppizza/css/[one of the files above]
  • ADD/EDIT your required css declarations to those files as required
  • make sure WPPizza -> Layout -> Style -> Include CSS / Stylesheet is still checked/enabled
  • Note: wppizza.custom.css – as outlined previously can still be used additionally if you so wish and will be loaded after

although you could also use your main theme and create the above mentioned directory structure there, using a child theme is by far the better and recommended way to do this – see WordPress Child Themes)

Suggest Edit

documentor id 5