How to Edit WooCommerce Product Templates with Toolset Starter Theme

   Amir

Announcements

March 27, 2017
6

Last week we announced the compatibility of all theme integrations with WooCommerce. Our own Toolset Starter was left behind. We just updated Toolset Starter. See how it works and how you can use it to create custom WooCommerce sites without PHP.

To see the magic, you should have the following plugins active in your site:

  • WooCommerce
  • Types
  • Views
  • Layouts
  • WooCommerce Views

The theme installer can get the required plugins for you, but you need to provide a site key for that. If you’re developing locally, you might as well install and activate Toolset plugins first.

Then, activate our Toolset Starter theme.

As soon as you activate the theme, you’ll see a prompt to run the setup wizard. This is how the entire process looks like:

At the end, you’ll have layouts for every part of the site, including for WooCommerce products (single product and the Shop page). From there, it’s simple. Click on the Front-end Layouts Editor button, in the admin bar and edit any layout you see.

Need help? Add your comments and we’ll reply.

 

Comments 6 Responses

  1. WooCommerce 3.0 was released yesterday. Included is a new CRUD api, to create, read , update and delete data on a product.

    I believe the reason is that in future versions WooCommerce wil move away from the meta options table and have the settings in their own table to increase performance on stores with many products.

    Their new CRUD api creates an abstract layer between the physical location of the data and the plugins / code using that data.

    Do you have a plan on how to handle this in the toolset plugins? Because obviously the post meta table will be abandoned by Woocommerce

    • What you’re saying makes sense. We didn’t think about it and we’ll keep an eye on upcoming changes in WooCommerce. We have a lot of code that handles custom fields. Many themes and other plugins probably have a lot of code for custom fields also. I don’t think that WooCommerce will make so many themes and plugins broken. It may gain a bit of speed (nothing dramatic), but will cause a lot of problems to many websites.

    • Hi there

      Thanks for the feedback.

      In general, WooCommerce Views uses the WooCommerce APIs to get and manipulate their data, if needed. That includes checking whether a product is on sale, its price, etc.

      However, we do a couple of things that might be affected:
      – We check the current stock status of a product using its postmeta value.
      – We populte some extra fields for ourseñves, like computed price, stock status and sale status, by reading the WooCommerce values s they get saved.

      The first one will be updated shortly to adjust to their new API for reading data. We are currently evaluating whether the second element will need to be adjusted or it has not changed, as it mainly depends on the WooCommerce backend GUI and not that much on their data access API.

      Keep tunned, we will have news on this soon.

      Thanks again.

    • Hi Henrik

      Sorry to ping you again here. I just got word from our main WooCommerce Views developer, and he is indeed following the changes in WooCommerce quite a lot.

      He stressed to me that we are accessing their data in a compatible way, and that we are testing against their latests and beta versions to detect any possible issue in advance. We do know that some etra changes were introuced in WooCommerce 3.0, and although their docs are not fully updated, our latests release is fully compatible with them as we fixed every issue we found beore they even released 🙂

      Hope it helps.