How to overwrite Woocommerce template using Avada Child Theme

3 comments

1. Solved using this in functions.php

   <?php
   add_filter('wc_get_template', 'ovr_product_meta_template', 10, 5);
   function ovr_product_meta_template($located, $template_name, $args, $template_path, $default_path) {
       if ('single-product/meta.php' == $template_name) {
           $default_path = get_stylesheet_directory();
           $template_path = 'woocommerce/';
           $located = wc_locate_template($template_name, $template_path, $default_path);
       }
       return $located;
   }
   ?>
   

   Log in to Reply

2. I came to this post because i’m having the same question. I did some research in the theme files to figure out where the source of all evil lies.

   First off: It’s no use replacing the templates for the my-account page in the child theme, nor the main theme. Reason: there’s an override in place on the entire my-account page from the Avada / Fusion Core files.

   I’ve checked the theme’s functions.php, avada-functions.php and the various my-account.php and my-address.php; nothing. Then I went and started opening several random files and folders until I came to this file: Avada/includes/woo-config.php.

   It appears there are several hooks in place, which overwrite the original woo-commerce template files with static code setup, like below. The ‘woocommerce_before_my_account’ hook (further in the php-file) is used to display the content of the my-account page.

       //function under myaccount hooks
       remove_action( 'woocommerce_thankyou', 'woocommerce_order_details_table', 10 );
       add_action( 'woocommerce_thankyou', 'avada_woocommerce_view_order', 10 );
       /* end checkout hooks */
   
       /* begin my-account hooks */
       add_action( 'woocommerce_before_customer_login_form', 'avada_woocommerce_before_customer_login_form' );
   function avada_woocommerce_before_customer_login_form()
   {
   
       global $woocommerce;
   
   if ( get_option( 'woocommerce_enable_myaccount_registration' ) !== 'yes' ) :
       ?>
   
   <div id="customer_login" class="woocommerce-content-box full-width">
   
   <?php
   endif;
   }
   
       add_action( 'woocommerce_after_customer_login_form', 'avada_woocommerce_after_customer_login_form' );
   function avada_woocommerce_after_customer_login_form()
   {
   
       global $woocommerce;
   
   if ( get_option( 'woocommerce_enable_myaccount_registration' ) !== 'yes' ) :
       ?>
   
   </div>
   
   <?php
   endif;
   }
   
   function avada_top_user_container() {
       global $smof_data, $woocommerce, $current_user;
   
       echo '<div class="avada_myaccount_user">';
           echo '<span class="myaccount_user_container">';
               echo '<span class="username">';
   
                   if ( $current_user->display_name ) {
                       printf( '%s, %s:', __( 'Hallo', 'Avada' ), $current_user->display_name );
                   } else {
                       echo __( 'Hallo', 'Avada' );
                   }
   
               echo '</span>';
   
               if ( $smof_data['woo_acc_msg_1'] ) {
                   echo '<span class="msg">';
                       echo $smof_data['woo_acc_msg_1'];
                   echo '</span>';
               }
   
               if ( $smof_data['woo_acc_msg_2'] ) {
                   echo '<span class="msg">';
                       echo $smof_data['woo_acc_msg_2'];
                   echo '</span>';
               }
               echo '<span class="view-cart">';
                   printf( '<a href="%s">%s</a>', get_permalink( get_option( 'woocommerce_cart_page_id' ) ), __( 'View Cart', 'Avada' ) );
               echo '</span>';
           echo '</span>';
       echo '</div>';
   }
   

   This unfortunately is not the solution, but it is an explanation on why the custom or edited original my-account does not work. I’ve created a ticket with Avada’s Theme-Fusion authors with this question. When I’ve got a response, i’ll check in again.

   Log in to Reply

3. Since the theme Avada is always up to date with the latest and also upcoming releases of WooCommerce they setup a compatability folder for the release about to be old. At the time of this writing 2.7 is about to come out and Avada has created a folder called compatability inside the folder woocommerce. Under that folder the version about to be old is represented with a folder, in this instance a folder named 2.6 exists by default.

   Inside the class Avada_WooCommerce you can find the filter called woocommerce_template_path that is hooked into by Avada, defining a function that checks if the current version is 2.7 or 2.6 and returning the path to the template folder. Since 2.7 is not yet released, 2.6 is running and for that, the folder is set to woocommerce/compatability/2.6.

   So if you are running 2.6 and want to override the templates in your child-theme, create a folder in your child-theme folder that is called woocommerce/compatability/2.6 and place your overriding templates there.

   If you then upgrade to WooCommerce 2.7 when it comes out, remember to place the overriding templates in the usual folder, woocommerce.

   Took me some time to figure out and I hope it helps!

   Log in to Reply