jehosophat

@rr,
Have you tried each and every solution that @mikejolley documented above?

Who provides your hosting service?

If for example you were to add a user to your wp install, do you get notification emails?

As noted previously, some hosts simply do not play well with WP – it’s not a woocommerce-specific issue. Have you tried an installation on a different host?

Hi BB,
Color me confused. There’s lots of support happening here on the www.ads-software.com forum. Even one of the devs responds often to questions here. If you had a question or comment on the free program, the wp.org support forum is the place for it. Woo clearly states that free program support is given here, while paid plugin support is given on their support forum.

So i’d suggest you post your question/bug here so it can be taken care of…

ps i’m in no way affiliated with woo.

Let’s break this down a little. Let me say from the outset, I have nothing to do with the Woo product team.

If what you mean by “the Woo Commerce product add-on” is the free plugin, or it’s one of the the pay plugins, by your own description, you’ve received heaps of support on the Woo support ticket system.

Your main complaint seems to be that it took them a while to find the bug for you, and for heavens sake, why couldn’t they have figured it out sooner…

Second complaint seems to say, ‘why can’t they get it right the first time, why do they have to have so many maintenance releases?’.

There’s no such thing as a perfect release, especially a major one like 2.0.

You seem to equate the number of maintenance releases with a shoddy product. On the contrary, it shows an active development team repairing bugs as they find them.

And as a relevant aside, any web designer (customer) worth his salt always applies and tests updates in a development environment, before applying updates to a production system.

Well let’s break it down, then.
(1) identify in what sequence the css files for your site get executed, and particularly when the Woo css is applied.
(2) ensure that any *additions* to your css configuration, which are aimed at repairing the float and other issues, are executed after Woo/last (even if you have to create another CSS file, to control this timing issue).
(3) enqueue this new css file in your theme’s functions file. Using priority will help to ensure this file is last.
(4) using firefox/firebug or google chrome, identify the css changes needed for your site and introduce them into that last css file, as you test.

This method allows css overrides to be introduced without touching Woo code in any way, making them independent of future Woo upgrades.

And Bob’s your uncle, Fanny’s your aunt.

#odinkinder,
How is this Woo’s problem? Incompatibility with your theme is the theme author’s problem, clearly.

Also, when you apply the Css customization you will be authoring (probably take less time than all of the to-ing and fro-ing), you should apply these to a css file you own (bottom of your theme style.css, for example), and thus the changes will be unaffected by future Woo updates.

@dan,
You’re absolutely right that paid support should be responded to within 24 hours. However, the problem you describe should not have been the 4-alarm fire you’re now having.

First, as a developer of experience, you should never apply an update of any kind directly to a live site, without extensive testing. This is akin to testing in a production environment. Rather, you should always have a development environment for each website, where you can install any updates and test them for stability, before applying them to a production environment.

Secondly, the fact that only one of your installations has this problem, points to the possibility that there may be a theme or other plugin conflict. You can test for this by temporarily deactivating all other plugins, and switching your theme to 2012, then retest.

As previously noted, you have every right to expect prompt response from Woo. However, you can minimize your exposure to future update problems by using a separate development environment as your test bed.

Wow. So because a currency is not in the list, you’re nuking the plugin through your review. Seems a bit excessive.

Well, Mufasa has popped up to proclaim the wonderfulness of wp-e-commerce ( https://www.ads-software.com/support/topic/beautiful-wp-e-commerce-example?replies=1 and https://www.ads-software.com/support/topic/freebie-wp-e-commerce-plugin-facebook-plugin?replies=1).

How about paying attention to customers??

No support at all from wp-e-commerce. Endless questions on the ‘support’ forum’ are not answered. Endless comments on ‘support’ forum about no answer on ‘premium’ forum.

Interesting, this post is not showing up in the ‘top ten’ on the main plugin page, although it is quite active…

Case in point – newest premium version of Gold Cart explodes on contact. Check the getshopped forum.

They have developed a new website for themselves instead of fixing the many bugs in the product. This broke the ‘support’ forums for weeks. Important things are broken with every product release.