Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter juanbarham

    (@juanbarham)

    Thanks Marc,

    I will take this in mind…thanks for your reply.

    Cheers,
    Juan

    Hi @pushevs @roxymathew, I had the same problem due to the use of the WPO Optimization plugin, I deleted the tables in one of my stores…fortunately I noticed the error inmediately and didn´t commit the same mistake in the rest of my shops.

    I updated another store to the latest version, and through phpMyAdmin I exported the following tables (structure and data) to a SQL file:

    wp_actionscheduler_actions
    wp_actionscheduler_claims
    wp_actionscheduler_groups
    wp_actionscheduler_logs
    wp_wc_admin_notes
    wp_wc_admin_note_actions
    wp_wc_category_lookup
    wp_wc_customer_lookup
    wp_wc_order_coupon_lookup
    wp_wc_order_product_lookup
    wp_wc_order_stats
    wp_wc_order_tax_lookup

    Then I imported the SQL file into the damaged database, and the problem seems to have disappeared, at least in the front end.

    Just in case, make a backup before and after implementing this idea, in my case it worked, and I put it here just in case it is helpful, while Woocommerce fixes this problem definitively.

    By the way, it would not be bad if we are not forced to install the administration panel, which continues to generate errors in the backend.

    However, in the frontend it seems to be fixed.

Viewing 2 replies - 1 through 2 (of 2 total)