Server error when saving variation

  • Resolved Triggahippie

    (@triggahippie)


    3 years, 1 month ago

    Hi, I’m having a problem saving a variation on a product. When i hit ‘update’ i just get a spinning wheel. The error i’m getting in the console is:-

    jquery.min.js?ver=3.5.1:2 POST https://arguseurope.co.uk/wp-admin/admin-ajax.php 500
    send @ jquery.min.js?ver=3.5.1:2
    ajax @ jquery.min.js?ver=3.5.1:2
    s.ajax.s.ajax @ jquery-migrate.min.js?ver=3.3.2:2
    save_changes @ meta-boxes-product-v….min.js?ver=5.1.0:1
    save_on_submit @ meta-boxes-product-v….min.js?ver=5.1.0:1
    dispatch @ jquery.min.js?ver=3.5.1:2
    v.handle @ jquery.min.js?ver=3.5.1:2

    When i go into the error_log i see: –

    #4 /home/hgoozilg1xp4/public_html/wp-content/plugins/woocommerce/src/Proxies/LegacyP in /home/hgoozilg1xp4/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php on line 75

    Line 73-77 reads: –

    } catch ( \Exception $e ) {
    /* translators: %s: error message */
    throw new \RuntimeException( sprintf( __( ‘Error saving action: %s’, ‘woocommerce’ ), $e->getMessage() ), 0 );
    }
    }

    So it seems to be stating the obvious, that it’s having a problem saving. I’m at my wits end with it now. The only clue I have to the reason is that the website was moved to a new platform a couple of weeks ago. Same domain name, just a newer faster server with cpanel. The website and database were exported from the old platform and imported to the new one without incident.

    • This topic was modified 3 years, 1 month ago by Triggahippie.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Gabriel – a11n

    (@gabrielfuentes)

    3 years, 1 month ago

    Hi there 👋

    Have you tried to run a conflict plugin/theme check, just to be sure there isn’t a conflict? If not, then the best way to determine this is to:

    • Temporarily switch your theme to Storefront
    • Disable all plugins except for WooCommerce
    • Repeat the action that is causing the problem

    If you’re not seeing the same problem after completing the conflict test, then you know the problem was with the plugins and/or theme you deactivated. To figure out which plugin is causing the problem, reactivate your other plugins one by one, testing after each until you find the one causing conflict. You can find a more detailed explanation on how to do a conflict test here.

    Before you start

    1. First, please make sure you have a good backup in place of your full site and database. Most hosting companies have this included in the subscription, but you could also consider using a service like Jetpack. If something goes wrong, it’s nice to know that you can restore your site.
    2. Second, I would suggest installing a plugin called Health Check & Troubleshooting. This is a plugin developed by the WordPress community and it allows you to disable plugins without affecting your current site visitors.
    Thread Starter Triggahippie

    (@triggahippie)

    3 years ago

    Thanks for your reply Gabriel. Yes i did try all the usual things, removing plugins etc. In the end, i had to migrate the database again, looks like a WC table wp_e_submission became corrupted going from the mariaDB platform to MySql. Despite them being supposedly compatible, there was an issue and by the look of it the work around caused a Total Inability To Sustain Usual Performance or ‘TITSUP’ as we say in the uk.
    It’s one to remember in future, When importing the database, I received the error: #1071 – Specified key was too long; max key length is 767 bytes.
    It seems to all be working now after a second migration and a different dirty fix

    Once again, thanks for getting back to me

    Plugin Support Senff – a11n

    (@senff)

    3 years ago

    Glad to hear that’s all sorted now! I’ll close this thread on our end, but if you run into any other issues, please don’t hesitate to open a new one. 🙂

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Server error when saving variation’ is closed to new replies.