Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

WooCommerce: Customization Mistakes to Avoid


Published on

These slides belong to, a technical video course that shows you how to override WooCommerce pages and elements without using plugins. You can watch me code and learn by example.

A series of videos, screencasts, examples and exercises will help you feel more confident about WooCommerce customization, child themes, hooks and CSS/PHP snippets.

Watch and re-watch each video how many times you like, get lifetime access to me via the comment section, exercise as much as possible and keep learning.

Access your free videos or buy the course via

Published in: Internet
  • Be the first to comment

  • Be the first to like this

WooCommerce: Customization Mistakes to Avoid

  1. 1. WooCommerce Customization: Mistakes to Avoid
  2. 2. 1. No child theme ● Other methods, tools or plugins are not ideal ● “One stop shop“ for placing your customization ● Easy to backup / find / access
  3. 3. 2. Unreliable plugins ● Applies to paid plugins too ● Bad plugin > more conflicts ● Bad plugin > poor support ● Bad plugin > no updates ● Installs + reputation + last update
  4. 4. 3. WC-unfriendly theme ● /woocommerce folder no good ● woocommerce.php no good ● Not developed and maintained by WC itself or WC experts ● Not optimized for conversions ● Not updated immediately after WC
  5. 5. 4. Using plugins before: ● Analyzing project specs ● Searching for snippets ● Researching the developer & support forums ● Considering “Zero option”
  6. 6. 5. Customizing a live website ● Even if you are 100% confident (happened to me...) ● Better: test on staging / clone / development site with latest WP+WC versions ● Take a backup before/after
  7. 7. 6. No backups ● Not only need backups, but also “1-click restore”. And test them ● Good hosting > automatic daily backup (no need of plugins) ● Files are not enough > DB!
  8. 8. 7. Cache enabled while coding ● Mostly when customizing CSS (PHP usually fine) ● Could be a plugin or server-side caching (ask your hosting) ● Test in incognito mode
  9. 9. 8. Poor hosting ● Investing less $ means paying more $ when trouble happens ● 24/7 (helpful) support, staging, daily backup & 1-click restore, SSL ● WordPress optimized
  10. 10. 9. No project management ● Even small jobs require a little contract / agreement / T&C ● Who’s doing what e.g. product upload, content writing ● $ deposit a must
  11. 11. 10. Hoping it’s update-proof ● No customization lasts forever (plugins are constantly updated to follow WC updates, and so should your snippets)