• Resolved Ajay Ghaghretiya

    (@ajayghaghretiya1)


    Hello everyone,

    We are facing the issue with the woocommerce setting page as the woocommerce settings display in twice.

    We are using the using the woocommerce version 3.2.5 on our live server. We have done the same setup on our local server but we are not facing this issue on local server. Also, We are not able to re-generate this issue on the staging server. I have attached the setting page screenshot for your reference.

    https://ibb.co/fAiH09
    https://ibb.co/nj1gSp

    When we are updating the latest version of woocommerce then it will break the whole woocommerce setting page as it is displaying the fatal error here like : “PHP Fatal error: Cannot declare class WC_Settings_General, because the name is already in use in /nas/content/live/prairiegrit/wp-content/plugins/woocommerce/includes/admin/settings/class-wc-settings-general.php on line 380”.

    Thanks in advanced

Viewing 4 replies - 1 through 4 (of 4 total)
  • Luminus Alabi

    (@luminus)

    Automattic Happiness Engineer

    Hi @ajayghaghretiya1,

    This kind of problem is usually caused by either a conflict with your theme or with another plugin.

    The best way to determine if the issue is being caused by a theme and/or plugin is to temporarily switch your theme to Storefront and disable all plugins except for WooCommerce. If you can install plugins, install Health Check. On the troubleshooting tab, you can click the button to disable all plugins and change the theme for you while you’re logged in to that session without affecting normal visitors to your site. Note that Health Check may not count Storefront as a default theme, so you can also use Twenty Seventeen as well.

    If that resolves the issue, then one-by-one you can switch back your theme and re-enable your plugins, testing in between, until you find the one causing the conflict.

    Thread Starter Ajay Ghaghretiya

    (@ajayghaghretiya1)

    Hello Luminus,

    Thanks for your replay..!!

    We have installed the Health Check plugin on our live server and we have tried to troubleshoot the issue but we can not activate some plugins using this troubleshooting functionality it is displaying the notice that we can not enable this plugin and it causes the issue and we have reverted it. We just need to catch the error from wc setting page.

    As we have discussed with our server support team they told us that woocommerce support team will provide you to the element arguments that need to exclude from that page.

    And also break the woocommerce setting page while we are updating the plugin to the latest version of the plugin and it is displaying the PHP Fatal error: Cannot declare class WC_Settings_General But as we have reviewed the code we can to found the WC_Settings_General.

    We have configured the same setup on our local server for troubleshooting this issue but we are not facing these issues on our local server.

    Please do assist us here in fixing this issue. And How we can troubleshoot this issue?

    Thanks,
    Ajay

    Plugin Support Hannah S.L.

    (@fernashes)

    Automattic Happiness Engineer

    Hey there Ajay,

    I’m going to echo what Luminus said above – this sounds like a conflict test. Health Check is just a tool to help you with that, and if it’s not working, then you’ll need to manually disable all plugins and switch the theme.

    As we have discussed with our server support team they told us that woocommerce support team will provide you to the element arguments that need to exclude from that page.

    I’m not sure exactly what you need here, but there isn’t anything we can provide.

    As you’re not seeing the same problem on the staging site, then it’s going to be something unique to the live site. That could be a slightly different plugin setup, or it could be a server difference.

    Thread Starter Ajay Ghaghretiya

    (@ajayghaghretiya1)

    Fixed..!!

    Thanks

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Issue with the WooCommerce Settings Page’ is closed to new replies.