http://www.kriesi.at/support/topic/fatal-errors-using-propulsion-after-woocommerce-143-update Support Forum - Topic: Fatal Errors Using Propulsion After WooCommerce 1.4.3 Update en-US Thu, 23 May 2013 23:24:24 +0000 http://bbpress.org/?v=1.0.2 q http://www.kriesi.at/support/search.php http://www.kriesi.at/support/topic/fatal-errors-using-propulsion-after-woocommerce-143-update#post-42200 Fri, 17 Feb 2012 12:44:55 +0000 TDR_ent16 42200@http://www.kriesi.at/support/ <p>Dude:</p> <p>Sorry, after I refreshed my screen after sending the 2nd comment, your message popped up. I saved the Permalinks again and the fatal error went away as you suggested it would. Part of the problem I see with WooCommerce is getting use to its peculiarities. I have used other eStore plugins and things like a Permalinks refresh are unnecessary after updating the plugin. So, thanks for the follow-up. The problem is not a problem anymore. TDR :) </p> http://www.kriesi.at/support/topic/fatal-errors-using-propulsion-after-woocommerce-143-update#post-42198 Fri, 17 Feb 2012 12:33:05 +0000 TDR_ent16 42198@http://www.kriesi.at/support/ <p>Kriesi Support:</p> <p>In anticipation of having problems with WooCommerce updates would you keep an eye on even the minor version level updates (i.e. v1.4.2 to v1.4.3 and so on) ? Perhaps Propulsion users should give you a heads-up on new updates and not install them until we hear back from the Kriesi team for a "thumbs-up" or "await a Propulsion update" comment. This is the second time just in the recent WooCommerce v1.4.X series where fatal errors are found.</p> <p>The only way to have a bug-free Propulsion site using WooCommerce after a fatal error like this is to rollback WooCommerce and your MySQL database to the state before the attempted WooCommerce update.</p> <p>Regards, TDR </p> http://www.kriesi.at/support/topic/fatal-errors-using-propulsion-after-woocommerce-143-update#post-42197 Fri, 17 Feb 2012 12:26:02 +0000 Dude 42197@http://www.kriesi.at/support/ <p>You need to save the permalink settings again. Go to Settings &gt; Permalinks and click on "Save". </p> http://www.kriesi.at/support/topic/fatal-errors-using-propulsion-after-woocommerce-143-update#post-42192 Fri, 17 Feb 2012 12:14:40 +0000 TDR_ent16 42192@http://www.kriesi.at/support/ <p>Looks like being cautious is in order even with minor updates to WooCommerce. Although an update to Woo v1.4.2 caused no problems the update from v1.4.2 to v1.4.3 produced a fatal error on the Propulsion "All Products" page. And, as we learned earlier, a rollback is not an option. Would appreciate Kriesi team support to bring about an update to Propulsion to fix this matter as the "All Products" page is unusable. The fatal error is:</p> <p>"Fatal Error: call to a member function is_visible() on a non-object in C:\\Wamp/www\wp1_yfstore2\wp-content\plugins\woocommerce\loop-shop.php on line 24"</p> <p>Regards, TDR </p>