503 caused by spectra

  • Resolved eragonsoftware

    (@eragonsoftware)


    8 months, 1 week ago

    It’s absolutely disheartening that a forum moderator just removed my previous post from another topic, WITH THE SAME ISSUE.

    Why is wordpress org doing this ?
    Anyway.. .the same issue here as in this topic>
    https://wordpress.org/support/topic/503-error-leads-to-spectra-issue/
    Spectra started causing issues today, only in admin.
    If we remove spectra, all works fine, but we loose the frontend content styles of course, which we built using spectra among others.

    If we add spectra back, admin breaks and 503 errors appear. I activated debug logging, and strangely enough, in the debug log there are no spectra related issues, but woocommerce src related issues, which disappear magically if we again remove spectra.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter eragonsoftware

    (@eragonsoftware)

    8 months, 1 week ago

    For now, the issue is solved, I completely removed all meta keys, and all other reference to spectra from the site’s database and then reinstalled spectra, and now it works.

    RPittam

    (@rpittam)

    8 months, 1 week ago

    Not sure what you mean here – all values like %spectra% in wp_posts and wp_postmeta?

    Thread Starter eragonsoftware

    (@eragonsoftware)

    8 months, 1 week ago

    Only from postmeta and transients, in my case there were some transients related to spectra, so I removed all transients directly from phpmyadmin, since I didn’t have access to admin in either case
    DELETE FROM wp_options WHERE option_name LIKE ‘transient%’ OR option_name LIKE ‘site_transient%’;

    Then
    DELETE FROM wp_options WHERE option_name LIKE ‘%updater%’; in the hope there were hung updates
    And then
    DELETE FROM wp_options WHERE option_name LIKE ‘%spectra%’ OR option_name LIKE ‘%uag%’;
    I’m not saying it’s going to work in your case, too.. this is what helped me.
    Then afterwards I just reinstalled spectra and activated it, it’s all good.


    RPittam

    (@rpittam)

    8 months, 1 week ago

    I just used wp-optimise to remove ALL transients and it seems to have worked. I changed the folder name of /ultimate-addons-for-gutenberg to /ultimate-addons-for-gutenberg-1-broken to enable my access to the dashboard. This made SPectra inactive. THen i removed the transients options and then renamed the folder back to ultimate-addons-for-gutenberg – then activated Spectra and it all seems to work. However, I have absolutely NO nada zilch idea as to what happened so i would still be grateful for the Spectra support to enlighten me.

    spletster

    (@tomsi)

    8 months, 1 week ago

    I had the same problem and solved it by renaming the ultimate-addons-for-gutenberg folder, deleting Transients and re-enabling the Spectra plugin. It works now, but the problem appeared this morning on some pages and different servers.
    I hope it doesn’t happen again.

    • This reply was modified 8 months, 1 week ago by spletster.
Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘503 caused by spectra’ is closed to new replies.