WordPress.org

Ready to get started?Download WordPress

Forums

WooCommerce - excelling eCommerce
Add to Cart Button redirects to WordPress Login (2 posts)

  1. inplacemarketing
    Member
    Posted 1 year ago #

    My client ignored my advice and updated to WooCommerce 2.0 before I got to test.
    Now I can no longer had to cart and it instead redirects to the WordPress Login. Why is this happening? It is it a theme issue or a WooCommerce conflict?

    My site is
    https://www.duecanicellars.com

    Any help would be amazing!

    http://wordpress.org/extend/plugins/woocommerce/

  2. Coen Jacobs
    Member
    Plugin Author

    Posted 1 year ago #

    There are a couple errors that you should address first though:

    Warning: include(/webroot/d/u/dueca001/primary/www/wordpress/wp-content/advanced-cache.php): failed to open stream: No such file or directory in /webroot/d/u/dueca001/primary/www/wordpress/wp-settings.php on line 58 Warning: include(): Failed opening '/webroot/d/u/dueca001/primary/www/wordpress/wp-content/advanced-cache.php' for inclusion (include_path='.:/usr/share/pear:/usr/share/php53/pear') in /webroot/d/u/dueca001/primary/www/wordpress/wp-settings.php on line 58 Warning: Cannot modify header information - headers already sent by (output started at /webroot/d/u/dueca001/primary/www/wordpress/wp-settings.php:58) in /webroot/d/u/dueca001/primary/www/wordpress/wp-content/plugins/woocommerce/classes/class-wc-session-handler.php on line 63 Warning: session_start(): Cannot send session cookie - headers already sent by (output started at /webroot/d/u/dueca001/primary/www/wordpress/wp-settings.php:58) in /webroot/d/u/dueca001/primary/www/wordpress/wp-content/plugins/si-contact-form/si-contact-form.php on line 1997 Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /webroot/d/u/dueca001/primary/www/wordpress/wp-settings.php:58) in /webroot/d/u/dueca001/primary/www/wordpress/wp-content/plugins/si-contact-form/si-contact-form.php on line 1997 Notice: WC_Product was called incorrectly. The WC_Product class is now abstract. Use get_product() to instantiate an instance of a product instead of calling this class directly. Please see Debugging in WordPress for more information. (This message was added in version 2.0 of WooCommerce.) in /webroot/d/u/dueca001/primary/www/wordpress/wp-includes/functions.php on line 2959 Notice: WC_Product was called incorrectly. The WC_Product class is now abstract. Use get_product() to instantiate an instance of a product instead of calling this class directly. Please see Debugging in WordPress for more information. (This message was added in version 2.0 of WooCommerce.) in /webroot/d/u/dueca001/primary/www/wordpress/wp-includes/functions.php on line 2959 Notice: WC_Product was called incorrectly. The WC_Product class is now abstract. Use get_product() to instantiate an instance of a product instead of calling this class directly. Please see Debugging in WordPress for more information. (This message was added in version 2.0 of WooCommerce.) in /webroot/d/u/dueca001/primary/www/wordpress/wp-includes/functions.php on line 2959 Warning: Cannot modify header information - headers already sent by (output started at /webroot/d/u/dueca001/primary/www/wordpress/wp-settings.php:58) in /webroot/d/u/dueca001/primary/www/wordpress/wp-includes/pluggable.php on line 876

    I can't even get it to the login screen right now. From what I can see, you've enabled the debug mode now, which is a good thing and enables you to see the errors at hand. Most errors are pretty straight forward. You have a missing file from W3 Total Cache and WooCommerce now advises you to use get_product() instead of new WC_Product(). Both issues are not fatal though, when you disable debug mode it should work as far as that means 'not showing any errors'.

    All of the WooCommerce premium extensions sold via our website woothemes.com have been updated to be compatible with WooCommerce 2.0 and so have our themes. If you are using one of those, please update to the latest available versions.

    If you're using third party plugins or theme as well, please check for updates there and if not available: go ask the developers to make the code WooCommerce 2.0 compatible.

    As far as the redirect to login redirect goes: This is probably a plugin doing this, as WooCommerce core has not setting for this. If you can't find the cause, start deactivating the plugins one by one until you've found the one that changes this.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags

No tags yet.