You theme contains outdated copies of some WooCommerce template file

Hi, Josh!

By default, Enterprise Pro doesn’t contain a woocommerce/ folder with custom WooCommerce-specific templates. If you or a developer have added template files there, it’s possible they may need to be updated, though.

You can find out more about how to update the templates here: https://docs.woothemes.com/document/fix-outdated-templates-woocommerce/

If you don’t have a woocommerce folder in the enterprise-pro theme directory, feel free to share the templates that WooCommerce is reporting as out of date. (You should find a list at WooCommerce → System Status.)

Hi Nick,
We had put a version number in the single-product.php file.

* @package genesis_connect_woocommerce
 * @version 0.9.8

Is it okay to remove that?
Thanks,
Josh
<?php
/**
* This template displays the single Product
*
* @package genesis_connect_woocommerce
* @version 0.9.8
*

Seriously we need an answer from Studiopress about this. I am against switching to Storefront and want to keep with Genesis.

Can studiopress update the plugin when new version numbers come out from Woo, and align those version numbers with Woo so we aren’t left wondering if things are about to break.

Is it safe to update the templates I have moved into:

child-theme/woocommerce/archive-template.php

Can I update the version number to the correct one to remove the error?

Even if genesis-connect is updated, how do I go about updating my customized files in the child theme folder?

If we could please have some insight, thank you.

Any updates on this? Thanks!

Like!
I reposted this on the Facebook Genesis (closed) Group.
It’s not clear to me how to best get a response from StudioPress.
Hopefully we can get an answer soon.

Another option is to submit a ticket on this at https://my.studiopress.com/help/.

Sorry for the late reply, @joshfialkoff and @ktphdeveloper.

In my tests, updating the version number in the custom template at your-child-theme/woocommerce/single-product.php to 1.6.4 has no side-effects.

I also reviewed the latest single-product.php WooCommerce template for new additions, and it does not appear that any changes are required to the Genesis Connect template beyond bumping the version number.

I’ll feed this back to the StudioPress team to see if the version numbers in the plugin’s template files can be bumped in a future version for those modifying them.

Great so just my thoughts,

? The plugin is monitored and when required updated to fit any updates in the woocommerce plugin.

? Create a changelog or somewhere so we can know which templates were effected, and if we need to adjust any templates we moved into child theme > woocommerce folder > e.g. single-product.php

? List the current template version number so we can update any templates we moved into child theme > woocommerce folder > e.g. single-product.php

This would help us avoid the Outdated template notice, as well as give us peace of mind that the Genesis Connect plugin and our custom templates are working 100% in coordination with WooCommerce.

Being able to use Genesis with Woocommerce has let me develop front end styles that match our designers layouts/designs. Basically WordPress + Genesis + Woocommerce kicks all other platforms in the bum. Love it.

Your thoughts on my commentssuggestions…?

Thanks!

Thanks so much for getting back to us.

Great feedback @KTPH. I agree 100%.

Thanks for the feedback. I agree that WordPress, Genesis, and WooCommerce make a great combo!

If you’re customising the default Genesis Connect templates, you’ll likely need to review changes to the relevant WooCommerce template manually each time you receive a new outdated template notification. (Even though the plugin could provide pointers as to what has changed, it wouldn’t necessarily account for any modifications you’ve made.)

I’ll be sure to pass this feedback to the StudioPress team, though – thanks again for taking the time to share it.

@ktphdeveloper

I feel there is an even better option. Take the taxonomy.php that comes with Genesis Connect for WooCommerce and move it to your local WooCommerce directory inside your child theme.

Then modify it so you unhook the “genesiswooc_product_taxonomy_loop”. That leaves you with a blank page where you can create your own custom loops.

Then get the Views plugin and use it to create your own custom view where you can set all kinds of filters in terms of how your products are outputted. This gives you full control over what products are shown, what order they are shown in etc. You can even create custom meta fields for your products and then filter using those.

All you have to do is then insert your View into the taxonomy page so it replaces the Genesis Woo loop.

This gives you the best of all worlds, Genesis, WooCommerce and custom queries.