Viewing 11 replies - 1 through 11 (of 11 total)
  • Can you please provide more information?
    What is the error that you receive?
    Have you enabled debug in WordPress?
    You can enable debugging in WordPress by going to wp-config.php and using this code:

    // Enable WP_DEBUG mode
    define('WP_DEBUG', true);
    
    // Enable Debug logging to the /wp-content/debug.log file
    define('WP_DEBUG_LOG', true);
    
    // Disable display of errors and warnings
    define('WP_DEBUG_DISPLAY', false);
    @ini_set('display_errors',0);
    
    // Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
    define('SCRIPT_DEBUG', true);

    Also don’t forget to remove any instance where WP_DEBUG is false.

    Many times the error is because of low memory assigned to WordPress. Be sure to have at least 128mb of memory dedicated to WordPress.
    You can set this via wp-config.php by this code:
    define('WP_MEMORY_LIMIT', '128M');

    I visited your site and it is working. From what I can see, you are using WPML 3.2.2. Have you tested to first upgrade WPML to its latest version?

    After upgrading to version 3.7, the site down with error 500. The error logs found this: PHP Fatal error: Call to undefined method WCML_Url_Translation::url_string_namet() in /wp-content/plugins/woocommerce-multilingual/inc/wc-strings.class.php on line 202.
    Rolling back to version 3.6.9 and the site working again. Fix a bug, please.

    @roganoff than you for reporting this issue.
    Can you please provide more information? Which versions of WPML you are using? Are you using WPML 3.2.7?

    WordPress 4.3.1, WPML 3.2.2

    Oh I see the issue now. It seems like a typo for the function.
    It should read url_string_name in /wp-content/plugins/woocommerce-multilingual/inc/wc-strings.class.php on line 202

    I have talked with our developers and a fix is on the way.

    Thanks!

    Our developers just released an updated version 3.7.1 that includes this fix.
    Thank you for reporting the issue.

    Thread Starter iammhaev

    (@iammhaev)

    For the meantime I deactivated the latest version and install again the old version 3.6.7

    I think we have the same error
    the site down with error 500.

    Thread Starter iammhaev

    (@iammhaev)

    Great it works already thank you πŸ™‚

    I am glad that it works for you as well.
    Please don’t hesitate to notify us when you have any other issues.
    I am marking this ticket as resolved.

    Thread Starter iammhaev

    (@iammhaev)

    alright thanks again!

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

The topic ‘After updating plugin website down’ is closed to new replies.