WooCommerce is conflicting with XStore and throwing up a 500 error

This topic has 13 replies, 2 voices, and was last updated 1 years, 9 months ago ago by Rose Tyler

  • Avatar: Hulkbearza
    Hulkbearza
    Participant
    July 9, 2022 at 10:19

    Greetings,

    XStore Core is running Version 4.2.3
    WooCommerce is running Version 6.6.1

    When I run Xstore Core plugin with WooCommerce I get a ” is currently unable to handle this request.
    HTTP ERROR 500″

    The WooCommerce support mentioned I should raise it here as they would not be able to do anything.

    Any assistance would be most appreciated as it was working a few days ago but now nothing.

    12 Answers
    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    July 10, 2022 at 06:54

    Hello,

    Thanks for using our theme.
    Please contact your hosting provider first. Check server error log.
    Let us know the result.

    Regards

    Avatar: Hulkbearza
    Hulkbearza
    Participant
    July 11, 2022 at 11:10

    Thanks, we are just running through wordpress.com here is the error log

    [11-Jul-2022 09:53:12 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/core/6.0/wp-includes/class-wp-query.php on line 584
    [11-Jul-2022 09:53:40 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/core/6.0/wp-includes/class-wp-tax-query.php on line 154
    [11-Jul-2022 09:54:00 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/core/6.0/wp-includes/class-wp-query.php on line 584
    [11-Jul-2022 09:54:00 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/core/6.0/wp-includes/class-wp-hook.php on line 300
    [11-Jul-2022 10:00:10 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/core/6.0/wp-includes/class-wp-query.php on line 584
    [11-Jul-2022 10:00:10 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/core/6.0/wp-includes/class-wp-hook.php on line 300
    [11-Jul-2022 10:00:17 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/core/6.0/wp-includes/class-wp-query.php on line 584
    [11-Jul-2022 10:00:17 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/core/6.0/wp-includes/class-wp-hook.php on line 300
    [11-Jul-2022 10:00:36 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 262144 bytes) in /wordpress/core/6.0/wp-includes/class-wp-term-query.php on line 259
    [11-Jul-2022 10:00:36 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 262144 bytes) in Unknown on line 0
    [11-Jul-2022 10:00:36 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 262144 bytes) in /scripts/env.php on line 105
    [11-Jul-2022 10:00:48 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/core/6.0/wp-includes/plugin.php on line 189
    [11-Jul-2022 10:00:48 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/plugins/woocommerce/6.6.1/includes/abstracts/abstract-wc-data.php on line 744
    [11-Jul-2022 10:00:49 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/core/6.0/wp-includes/class-wp-hook.php on line 300
    [11-Jul-2022 10:00:49 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 262144 bytes) in /wordpress/core/6.0/wp-includes/class-wp-query.php on line 3586
    [11-Jul-2022 10:00:49 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 262144 bytes) in /wordpress/core/6.0/wp-includes/load.php on line 1564
    [11-Jul-2022 10:00:49 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 262144 bytes) in /scripts/env.php on line 105
    [11-Jul-2022 10:01:08 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/core/6.0/wp-includes/functions.php on line 4801
    [11-Jul-2022 10:01:11 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/core/6.0/wp-includes/functions.php on line 4801
    [11-Jul-2022 10:01:30 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/plugins/woocommerce/6.6.1/includes/abstracts/abstract-wc-data.php on line 744
    [11-Jul-2022 10:01:57 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/core/6.0/wp-includes/functions.php on line 4801
    [11-Jul-2022 10:06:23 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/core/6.0/wp-includes/class-wp-query.php on line 584
    [11-Jul-2022 10:06:24 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/core/6.0/wp-includes/class-wp-hook.php on line 300
    [11-Jul-2022 10:06:24 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/core/6.0/wp-includes/functions.php on line 4801
    [11-Jul-2022 10:06:24 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 262144 bytes) in /wordpress/core/6.0/wp-includes/class-wp-query.php on line 3586
    [11-Jul-2022 10:06:24 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 262144 bytes) in /wordpress/core/6.0/wp-includes/load.php on line 1564
    [11-Jul-2022 10:06:24 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 262144 bytes) in /scripts/env.php on line 105
    [11-Jul-2022 10:06:28 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/core/6.0/wp-includes/class-wp-query.php on line 584
    [11-Jul-2022 10:06:28 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/core/6.0/wp-includes/class-wp-hook.php on line 300
    [11-Jul-2022 10:06:36 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/core/6.0/wp-includes/class-wp-tax-query.php on line 154
    [11-Jul-2022 10:06:43 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/plugins/woocommerce/6.6.1/includes/abstracts/abstract-wc-data.php on line 744
    [11-Jul-2022 10:06:56 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/core/6.0/wp-includes/class-wp-tax-query.php on line 154
    [11-Jul-2022 10:06:59 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/core/6.0/wp-includes/class-wp-tax-query.php on line 154
    [11-Jul-2022 10:07:01 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/plugins/woocommerce/6.6.1/includes/abstracts/abstract-wc-data.php on line 744
    [11-Jul-2022 10:07:30 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/core/6.0/wp-includes/functions.php on line 4801

    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    July 11, 2022 at 12:12

    Hello,

    You need to contact your hosting provider support and ask them to increase memory_limit value.

    Regards

    Avatar: Hulkbearza
    Hulkbearza
    Participant
    July 12, 2022 at 12:24

    Please see the response I received below.

    In this case there is clearly a glitch in the custom theme code, or that of one of the plugins on the website that is causing a memory overflow.

    In fact the theme’s own tool mentions that their memory requirement is 128MB. If they now say that they require 1024MB, then there is certainly something wrong in their code.

    The error 500 seems to stop whenever we deactivate the X Store Core plugin

    It will be good if the theme team there takes a look at these error messages and what code lies on the exact lines shown by the error:

    Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/core/6.0/wp-includes/functions.php on line 4801

    Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 32768 bytes) in phar:///usr/local/bin/wp-cli/vendor/wp-cli/php-cli-tools/lib/cli/Colors.php on line 1

    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    July 12, 2022 at 12:39

    Hello,

    Please provide temporary wp-admin and FTP access, so we can take a closer look.
    Create an account via Dashboard (Users > Add new) with administrator role http://prntscr.com/s3rc9m > provide us with username and password via the Private Content area http://prntscr.com/s5mao7 You can use any email for it.
    If you do not know how to create FTP contact with your hosting provider, they will help you.

    Regards

    Avatar: Hulkbearza
    Hulkbearza
    Participant
    July 14, 2022 at 11:50

    See private message.

    Please contact administrator
    for this information.
    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    July 14, 2022 at 16:56

    Hello,

    Thanks for the reply.
    About FTP access, we can’t connect, unfortunately.

    Error:        	Connection timed out after 20 seconds of inactivity
    Error:        	Could not connect to server

    Do you have any limits for connections from other countries?
    What port can we use? Please clearly provide FTP host, FTP username, FTP password, FTP port.
    Waiting for your reply.

    Regards

    Avatar: Hulkbearza
    Hulkbearza
    Participant
    July 15, 2022 at 04:21

    Please see updated details

    Please contact administrator
    for this information.
    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    July 15, 2022 at 06:38

    Hello,

    I’ve passed this question to one of our developers. I will let you know once get an answer. Please be patient and do not change access.

    Regards

    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    July 15, 2022 at 10:09

    Hello,

    Url of site in your first message is different to the latest one. Did you provide access to site where the problem exists?
    We found that you have notice of outdated theme -> https://gyazo.com/81040f9783e3b430667e5fcfc1893cc3
    Could you please, update the theme to the latest version on https://recur****to.com.br/ or give us a feedback if we can do it for you? Create backup before update, read more – https://xstore.helpscoutdocs.com/article/63-theme-update
    Also, we don’t see any error log files
    https://prnt.sc/qqkANcy4DXEh
    Where are they located or maybe you removed all of them ?

    Regards

    Avatar: Hulkbearza
    Hulkbearza
    Participant
    July 16, 2022 at 11:59

    Looks like when I try to access the site through the XStore Child theme, I get the 500 error this version has my customization. With the Xstore main theme, I believe I can get the site to work, but I have no customizations on that one.

    https://engravingsystems23594761.wpcomstaging.com

    I had also temporarily disabled the Xstore plugin. Otherwise, the site crashed, but it is back up and running with the child XStore them and getting the 500 error. I also disabled debugging in the FTP but that is up and running again also.

    Let me know how you get on from what I could tell, everything was updated?

    Regards,

    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    July 16, 2022 at 13:51

    If the problem persists with the child theme only, you need to check your custom changes there (comment code in fuctions.php, rename re-written files and check what exactly custom code caused the problem).
    Please note that we are not responsible for custom changes that you do in the child theme.

    Regards

  • Viewing 13 results - 1 through 13 (of 13 total)

You must be logged in to reply to this topic.Log in/Sign up

We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.