Error after update - by area7567 - on WordPress WooCommerce support

Solved7 replies2 participantsUpdated by Rose Tyler

  • Avatar: area7567
    area7567
    Participant

    After updating the theme to the latest version, I cannot enter the console.

    Please, contact administrator
    for this information.

    7 Answers

    Avatar: Rose Tyler
    Rose Tyler
    Support staff

    Hello,

    Enable debug mode in WordPress – https://wordpress.org/support/article/debugging-in-wordpress/ to find out what error appears on your site, it will point you in the right direction what needs to be fixed.

    Regards

    Avatar: area7567
    area7567
    Participant

    The Enable WP_DEBUG mode has been turned on, and then the website is reorganized to display this screen. What does it mean?

    Please contact administrator
    for this information.
    Avatar: Rose Tyler
    Rose Tyler
    Support staff

    Provide FTP access also.

    Regards

    Avatar: area7567
    area7567
    Participant

    Please help me to deal with it. I have gone back to the server several times and still get errors. I also have another website that needs to be updated. I am worried that there will be the same problem.

    Please contact administrator
    for this information.
    Avatar: Rose Tyler
    Rose Tyler
    Support staff

    I can’t connect. https://prnt.sc/wuydho Is there any restriction by IP?
    What port?
    Wi**67 is username or password?

    Regards

    Avatar: area7567
    area7567
    Participant

    Please try again, thanks.

    Please contact administrator
    for this information.
    Avatar: Rose Tyler
    Rose Tyler
    Support staff

    You used very old version of the Core plugin. We uploaded the new version of the Core via FTP.
    Please check. If everything is fine, you can delete the old plugin version.
    Watch about the update via FTP here – https://www.8theme.com/documentation/xstore/theme-installation/theme-update/

    Regards

The issue related to '‘Error after update’' has been successfully resolved, and the topic is now closed for further responses