Tired of plugin conflicts, upgrades that aren’t tested.
Woo likes to blame themes and other plugins instead of taking responsibility.
I will change my review when they change their upgrade ‘behavior’ and posting a change log for all to see.
I wasted 9 hours trying to fix a broken cart that would not allow customers to remove items, change quantities or check out as a guest. Luckily I have other sites with the exact same configuration (call it A/B testing). It turns out Woo changed the short code on my checkout and cart pages.
If you have my problem you should look for these codes:
Cart: <!– wp:shortcode — >[woocommerce_cart]<!–/wp:shortcode –>
Checkout: <!– wp:shortcode –> [woocommerce_checkout]<!– /wp:shortcode –>
I had a ton of garbage code on those pages after upgrading plugin to 9.02 that caused the cart to stop working. All on woo for lack of transparency.
]]>If you don’t plan to pay $240/yr for the JetPack features there is no point installing it. I’ve uninstalled from all my small hobby sites.
I loved the super-simple traffic stats that you got with Jetpack, but now they want me to pay more for stats than I pay for the domain and hosting.
Not cool Automattic!
]]>Took me an hour to remove this crab manually, as /wp-admin/, the recovery-link in the email and EVEN DISABLING ALL PLUGINS IN THE DATABASE didn’t work.
So I removed Jetpack from all my WordPress-Sites
even after purchasing the extension in order to use the restore feature – this plugin just hangs – and what’s more gives no clear indication why. i have learnt from my mistakes in the past and always ensure there are plenty of resources on the server.
this last site i tried to migrate 3 times – and every time it just hung – no reason why. i finally decided to look for other options and found one that migrated my whole site in less than 10 minutes – even after using it for the very first time – and a free version. during the whole process there were clear progression messages that made me feel confident the plugin was actually doing something. it happened so fast anyway there was little time to worry. so i urge to to look for other solutions as this one seems to have fallen behind.
]]>