Support » Plugin: Simple Catalog for WooCommerce » Plugin could not be activated because it triggered a fatal error

  • Resolved Jmwd.studio

    (@jmwdstudio)


    Hi, Ive tried to install the plugin but I get this message: Plugin could not be activated because it triggered a fatal error.

    Fatal error: Can’t use method return value in write context in /var/www/vhosts/dandyhire.co.uk/httpdocs/wp-content/plugins/simple-catalog-for-woocommerce/simple-catalog-for-woocommerce.php on line 296

    Any advice would be most appreciated.

    Jen

    • This topic was modified 2 years, 4 months ago by Jmwd.studio.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author ahortin

    (@ahortin)

    What version of PHP are you using? If you’re using less than v5.5 I would recommend updating to at least 5.5

    Hi, I’ve updated to 5.5 and it installed. I have turned all options to off but the cart and 0 Items is still appearing in my top navigation bar, any advice?

    Plugin Author ahortin

    (@ahortin)

    When you say that you’ve “turned all options to off” I presume that you mean that you’ve set all options to “hide for all users”. Is that correct?

    If your site is still showing a Cart button in your top Nav, this is most likely being added by the theme itself. WooCommerce, by default, does not add a cart button/icon to your nav or header area, which also means that this plugin can’t control it (or hide it). I would suggest looking at your theme options for your theme to see if there’s an option to disable that cart button/icon.

    Likewise, with your Cart page. It sounds like your theme has a custom cart template or something that isn’t the standard WooCommerce cart. Normally the Cart is just a standard WordPress page with a [woocommerce_cart] shortcode. Try unpublishing this page and see if that helps. If the Cart is still showing, then your theme is overriding it somehow and you’ll need to either look in your theme options again, or contact the theme developer.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Plugin could not be activated because it triggered a fatal error’ is closed to new replies.