[bobrouge]

Please Don’t add a smiley face when you update your theme after everything breaks. It’s your job to keep it compatible since it’s a store based theme.

Please follow the dev version of woocommerce and their release schedule like a professional.

[bobrouge]

You need to follow these steps.

1. go into your plugins section and disable woocommerce
2. go into your plugins folder by ftp and rename woocommerc to something else like “woocommerce-new-broken”
3. Download the older woocommerce from http://wordpress.org/plugins/woocommerce/developers/ , you want version 2.0.20 under section other versions.
4. upload it to your plugins folder and activate it in the admin and do not update it
5. Do not buy any more themes from swiftideas because it not acceptable to not be up to date with major version changes and altogether poor quality of code( if you bothered to look you would see).

[bobrouge]

Does it matter? I’m using the neighborhood theme but it’s the framework that doesn’t support child themes, not the theme itself. Surely you already know about this, then again given the quality of the code maybe not.

[bobrouge]

You can hide it using

.wc-new-badge{
	display: none;
}

[bobrouge]

My point was that your theme only partially support child themes because the swift framework itself does not.

Since the theme is so tightly coupled with the actual framework it is not possible to really use child themes effectively, this is bad practice and planning, it does not follow standards that WP strives for.

Something as simple as changing the header menu output (sf-header.php) had to be done via the changing files in the swift framework theme folder, which as I mentioned do not work using a child theme hierarchy. The only solution was to completely decouple the swift framework from the parent theme using define(‘SF_FRAMEWORK_PATH …) which defeats the whole reason to use child themes.