March 5, 2013 at 4:57 pm #24435
Is the new Woocommerce version 2.0 compatible with Genesis Connect for WooCommerce?
Janet Morrow | Mountain Ash Website Design | http://www.mountainash.org
Visit Our Site for more information and pricing.March 6, 2013 at 1:49 pm #24595
Make sure this is in your functions.php (one of these lines should have already been there, one is new)
add_theme_support( ‘woocommerce’ );
add_theme_support( ‘genesis-connect-woocommerce’ );
http://www.ExpandingDesigns.com – Custom WordPress websites built on the Genesis Framework.March 11, 2013 at 2:01 am #25430
I've implemented this as suggested and it's worked perfectly - it was the first line that was missing for me. Thank goodness this worked as I disregarded the warnings and upgraded to Woocommerce 2.0 too quickly without properly preparing for it.March 11, 2013 at 1:50 pm #25493
Much of the discussion about "is WooCommerce compatible?" is a little off the mark. Generally speaking, WooCommerce is compatible.
1) Re the line: add_theme_support( ‘woocommerce’ );
If you don't have that line AND if you are not using one of the default WP themes Twenty Ten, Twenty Eleven, or Twenty Tweleve, all it does it trigger the loading of /assets/css/activation.css in your WooCommerce plugins folder. That MIGHT override some classes in your CSS, but it might not. It depends on your theme and your site. If you don't record the line, WooCommerce will fire the notice in /admin/includes/notice_theme_support.php. You can also dismiss the notice if you don't have the line. But the line does NOT make your theme suddenly support WooCommerce.
2) Re the line: add_theme_support( ‘genesis-connect-woocommerce’ );
That's from the Genesis Connect for WooCommerce plugin. The logic is the same as in #1. If that is defined, it does certain things. If it is not defined, it displays a message. If you want the things that Genesis Connect for WooCommerce does, use this line.
3) There was an issue when WooCommerce 2.0 came out where rewrite rules needed to be flushed (by saving your permalink settings without change). If you didn't re-save your permalinks, you'd get 404 errors on store pages. That was fixed in the minor releases that quickly followed on the heels of 2.0.
Because of #1 and #2, if you do NOT want activation.css loaded, you have to use the line described in #1. If you want to use Genesis Connect for WooCommerce, you have to use the line in #2. The line in #1 is not required to make WooCommerce work with Genesis, as you can see on our demo site ( http://agency2.wpperform.com/shop/ ) which is running WooCommerce and doesn't have that line of code.
We have WooCommerce on our network and support it for any of the themes we offer, so it works fine.
May 4, 2013 at 6:07 am #39227
This isn't working on the Generate theme. I have the code in functions.php exactly as it's supposed to be (I even retyped the quotation marks), but attempting to activate Genesis Connect for WooCommerce still says:
Sorry! In order to use the Genesis Connect for WooCommerce plugin you need to do the following:
Install and activate the WooCommerce plugin.May 4, 2013 at 8:05 am #39238
@danieljlewis - I am not sure what you mean by "isn't working". Do you mean your attempt to use add_theme_support() isn't working? The line itself is not necessary to run WooCommerce. Try removing or commenting out any lines you added with add_theme_support() related to WooCommerce, activate the WooCommerce plugin, and see how it works.
As I mentioned in my previous comment, the add_theme_support() functions change which CSS is loaded. The change may not impact your site. If you haven't set up your store, you'll have better results if you put your energies toward store setup, because the CSS issues are easier to sort out once you have some content created.
May 4, 2013 at 8:54 am #39246
@bill Murray, I have the code in my functions.php just fine. It's inserted properly. What isn't working, as I said, is activating Genesis Connect for WooCommerce. When I attempt to do that, I get the above error message telling my to install and activate WooCommerce (which it is).
I have this working on a different site (multisite, actually) with a different Genesis child theme. But why can't I activate the Connect plugin on this single site with Generate even when I've followed the instructions?May 4, 2013 at 9:19 am #39252
That is the output when you don't have WooCommerce activated. If you want to use the plugin Genesis Connect for WooCommerce, you need to do 2 things:
1) Put the line in your functions.php or in a custom plugin
2) Activate WooCommerce
Only after doing both of those things can you activate Genesis Connect for WooCommerce.
If you've done #1 & 2 and are still getting that error, something else is going on. If you have caching activated, deactivate it and retest. Are you running the latest release of Genesis Connect for WooCommerce, which is 0.9.5? If so, that release, which came out after my earlier comment includes the line add_theme_support( 'woocommerce' ); so you wouldn't add that line to your functions.php.
May 4, 2013 at 11:32 am #39280
Yes, I've done those things and triple-checked them. I have the latest versions of everything and no caching plugins.May 4, 2013 at 2:52 pm #39299
I did the following...
1) activated the Generate theme
2) activated WooCommerce
3) activated our custom plugin that uses add_theme_support (the equivalent of putting it in your functions.php)
4) activated Genesis Connect for WooCommerce
and all is well.
So it does work. Therefore, we have to consider:
1) The error message that you are seeing is output by Genesis Connect for WooCommerce when this file, woocommerce/woocommerce.php, fails a check with is_plugin_active(). Did you rename the woocommerce folder or the plugin itself? Did you relocate your wp-content folder? If woocommerce isn't in that location, (ie, wp-content/plugins/woocommerce/woocommerce.php), you'll get the error.
2) As a precaution, did you try this with no other plugins activated, other than those relevant to this test, ie, WooCommerce and Genesis Connect for WooCommerce? If not, deactivate everything else and test.
3) When WooCommerce is activated, you'll see an entry named "WooCommerce" added to your top level WP dashboard menu. Do you see that?
May 6, 2013 at 9:27 am #39548
Thank you, Bill! This is a client's site, so I did check to ensure that he didn't have something that change the name of "wp-content." And when I did check that, I found something very weird!
WooCommerce was activated and running on this website, but the "woocommerce" folder was not in wp-content/plugins! FREAKY! But when I updated to 2.0.9 (includes a Mijreh fix for Multisite that I submitted to them), the woocomerce folder showed up in FTP. Then things started working again!
Not only did Genesis Connect for WooCommerce properly activate, but the Dynamic Pricing plugin finally started working, too!
Very weird problem! I'm starting to suspect gnomes. 🙂
Thank you for your help which lead me to the real cause of the problem.
This issue is now resolved for me.May 6, 2013 at 9:57 am #39554
You must be logged in to reply to this topic.