• Resolved aminmemar

    (@aminmemar)


    After updating to 1.7.0 it gave HTTP 500 error on the home page. The error goes after diactivation.

    The page I need help with: [log in to see the link]

Viewing 10 replies - 1 through 10 (of 10 total)
  • @aminmemar thanks for your report! Could you tell us which version of the plugin you updated from?

    Providing your Site Health information would also be great to see if there could anything conflicting. Thank you!

    Thread Starter aminmemar

    (@aminmemar)

    I am not sure which version it was but I was keeping it up to date. So it was the previous stable version.

    The health status says:

    
    ### wp-core ###
    
    version: 5.4
    site_language: fa_IR
    user_language: fa_IR
    timezone: Asia/Tehran
    permalink: /%year%/%monthnum%/%day%/%postname%/
    https_status: true
    user_registration: 1
    default_comment_status: open
    multisite: false
    user_count: 8
    dotorg_communication: true
    
    ### wp-dropins (1) ###
    
    advanced-cache.php: true
    
    ### wp-active-theme ###
    
    name: eCommerce Gem (ecommerce-gem)
    version: 2.1.4
    author: ProDesigns
    author_website: https://www.prodesigns.com/
    parent_theme: none
    theme_features: align-wide, post-thumbnails, automatic-feed-links, title-tag, custom-logo, menus, html5, custom-background, woocommerce, wc-product-gallery-lightbox, wc-product-gallery-slider, wc-product-gallery-zoom, widgets, editor-style
    theme_path: /home2/peyvandr/public_html/wp-content/themes/ecommerce-gem
    
    ### wp-plugins-active (29) ###
    
    Autoptimize: version: 2.6.2, author: Frank Goossens (futtta)
    Back In Stock Notifier for WooCommerce | WooCommerce Waitlist Pro: version: 1.9.6, author: codewoogeek
    Contact Form 7: version: 5.1.7, author: Takayuki Miyoshi
    Google XML Sitemaps: version: 4.1.0, author: Arne Brachhold
    Hide WooCommerce Categories On Shop Page: version: 1.1.0, author: Matix Web Designers
    Loco Translate: version: 2.3.3, author: Tim Whitlock
    Mailchimp for WooCommerce: version: 2.3.6, author: Mailchimp
    Max Mega Menu: version: 2.7.6, author: megamenu.com
    MC4WP: Mailchimp for WordPress: version: 4.7.6, author: ibericode
    Product Visibility by User Role for WooCommerce: version: 1.5.3, author: WP Wham
    Qty Increment Buttons for WooCommerce: version: 2.7.1, author: taisho
    Really Simple SSL: version: 3.3.1, author: Rogier Lankhorst, Mark Wolters
    ReCaptcha v2 for Contact Form 7: version: 1.2.4, author: IQComputing
    Redux Framework: version: 3.6.18, author: Team Redux
    Store Management: version: 1.0.0, author: Amin
    Variation Swatches for WooCommerce: version: 1.0.80, author: Emran Ahmed
    WooCommerce: version: 4.0.1, author: Automattic
    WooCommerce Admin: version: 1.0.3, author: WooCommerce
    WooCommerce Group Attributes: version: 1.3.3, author: DB-Dzine
    WP-Optimize - Clean, Compress, Cache: version: 3.0.19, author: David Anderson, Ruhani Rabin, Team Updraft
    WP-Parsidate: version: 3.0.3, author: WP-Parsi Team
    WP-Persian: version: 3.2.5, author: Siavash Salemi
    WP Google Maps: version: 8.0.22, author: WP Google Maps
    WPS Hide Login: version: 1.5.6, author: WPServeur, NicolasKulka, tabrisrp
    YITH WooCommerce Compare: version: 2.3.20, author: YITH
    YITH WooCommerce Wishlist: version: 3.0.9, author: YITH
    افزونه حمل و نقل ووکامرس: version: 2.1.5, author: MahdiY
    درگاه پرداخت بهپرداخت ملت افزونه ووکامرس: version: 5.0.0, author: ووکامرس فارسی
    ووکامرس فارسی: version: 3.9.1, author: ووکامرس فارسی
    
    ### wp-plugins-inactive (1) ###
    
    Site Kit by Google: version: 1.7.0, author: Google
    
    ### wp-media ###
    
    image_editor: WP_Image_Editor_GD
    imagick_module_version: Not available
    imagemagick_version: Not available
    gd_version: bundled (2.1.0 compatible)
    ghostscript_version: 9.25
    
    ### wp-server ###
    
    server_architecture: Linux 3.10.0-962.3.2.lve1.5.27.el7.x86_64 x86_64
    httpd_software: Apache
    php_version: 7.2.29 64bit
    php_sapi: cgi-fcgi
    max_input_variables: 1000
    time_limit: 30
    memory_limit: 256M
    max_input_time: 60
    upload_max_size: 2M
    php_post_max_size: 8M
    curl_version: 7.68.0 OpenSSL/1.1.1d
    suhosin: false
    imagick_availability: false
    htaccess_extra_rules: true
    
    ### wp-database ###
    
    extension: mysqli
    server_version: 5.6.47
    client_version: mysqlnd 5.0.12-dev - 20150407 - $Id: 3591daad22de08524295e1bd073aceeff11e6579 $
    
    ### wp-constants ###
    
    WP_HOME: undefined
    WP_SITEURL: undefined
    
    WP_MAX_MEMORY_LIMIT: 256M
    WP_DEBUG: false
    WP_DEBUG_DISPLAY: true
    WP_DEBUG_LOG: false
    SCRIPT_DEBUG: false
    WP_CACHE: true
    CONCATENATE_SCRIPTS: false
    COMPRESS_SCRIPTS: undefined
    COMPRESS_CSS: undefined
    WP_LOCAL_DEV: undefined
    DB_CHARSET: utf8mb4
    DB_COLLATE: undefined
    
    ### wp-filesystem ###
    
    wordpress: writable
    wp-content: writable
    uploads: writable
    plugins: writable
    themes: writable
    mu-plugins: writable
    
    
    • This reply was modified 4 years, 3 months ago by Yui. Reason: cleared userinfo from wp-paths

    @aminmemar thanks for the details. I don’t see anything that is known.

    1) Did the error just happen on the home page or internal pages too?

    2) Were you logged into WordPress while viewing the frontend of the site when you saw the error?

    I am going to try to test updating with some the plugins you have to see if there is a conflict.

    Thread Starter aminmemar

    (@aminmemar)

    Thank you, The error was just on the front pages. I did not get the error on admin panel. Yes, I was logged in already.

    @aminmemar thanks again for these details and your patience as we narrow down the source.

    We are getting other reports of an issue with viewing the front end while logged in due to another plugin conflicting however you do not have this plugin installed and the 500 error is unique in your case. I’ve tested the majority of the plugins from your Site Health info, but I haven’t reproduce the issue yet.

    There may be another way we can try find the source of the issue since this is a server error. Are you able to contact your host to see if there are any error logs available for around the time this occurred? This may give us a clue what could be happening.

    Thread Starter aminmemar

    (@aminmemar)

    Thank you for dedicating your time to my issue. Since there might be some security problems I demand you to delete my site health report since I no longer have the permission to delete it.

    There is no log from hosting services.

    • This reply was modified 4 years, 3 months ago by aminmemar.
    Moderator Yui

    (@fierevere)

    永子

    @aminmemar
    posting site health info is not considered to be security threat/private information disclosure,
    therefore we (moderators) will not delete/edit it.

    forum guidelines and below

    Plugin Support James Osborne

    (@jamesosborne)

    @aminmemar Can you confirm you have access to Google services from your current location?

    @aminmemar does the issue still persist for you after updating to the new version 1.7.1?

    @aminmemar since we have not heard from you, I am marking your support topic as resolved. Feel fee to open a new support topic if you need further help.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘500 error after updating to version 1.7.0’ is closed to new replies.