• Resolved oseven

    (@oseven)


    Got a white page for all the website after the upgrade to 4.1.3! Had to find the 4.1.2 from the previous backups to restore website.
    The site shows normal when logged on to wordpress, but shows white page when try to connect from incognito screen.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Hello, @oseven
    Can you provide more information about the error, please?
    Perhaps you need to enable debugging in order to get the error in the log.

    You can do this by setting this options in wp-config.php
    above the line that says:
    /* That’s all, stop editing! Happy blogging. */

    // Turn debugging on
    define('WP_DEBUG', true);
    
    // Tell WordPress to log everything to /wp-content/debug.log
    define('WP_DEBUG_LOG', true);
    
    // Turn off the display of error messages on your site
    define('WP_DEBUG_DISPLAY', false);
    
    // For good measure, you can also add the follow code, which will hide errors from being displayed on-screen
    @ini_set('display_errors', 0);

    Please do note to remove any other instances of this code if you have it in the file:

    define('WP_DEBUG', false);

    Thread Starter oseven

    (@oseven)

    Hello,

    I have the server error log during the downtime, does that help?

    https://gist.github.com/altuno/e4e48c6b3ce4bd582541be16c6b6bc04

    @oseven Yes, this is somewhat of a help at least to identify the error.
    Can you elaborate on the action that triggered this error?
    Do you have any special plugins that modify the products, gateways, e-mails or orders in any way?
    Are you using all current versions of all plugins/themes that you have?

    Any further info that you can share is welcome.

    Thread Starter oseven

    (@oseven)

    I am not sure, it took me quite some time to understand the issue is from the Woocommerce WPML – as I first thought the issue was Woocommerce itself.

    What I did around the time the site went down was to deactivate and delete a Woocommerce payment gateway plugin (https://woocommerce.com/products/sofort-payment-gateway/) and at the same time I updated your plugin to the latest version. Then the site went down. This must have screwed up something in the site, because I could not replicate the problem in my staging site. The only thing I did different in the staging site is that I first disabled the SOFORT gateway in woocommerce preferences before I deactivated & deleted it. So right now in the staging site, your plugin is up to date and the site runs ok.
    However in the live site, the moment I update your plugin to the latest version, the site goes down again.

    All my plugins are up to date. Here is the system report from my theme which should show all the installed plugins & settings etc:
    https://gist.github.com/altuno/ecd381d2fc16faace73e1a908292c4d6

    I can provide you a temporary admin access if it will help.

    Because we cannot share here credentials securely, it would be best if you can open a new ticket in our support forum at wpml.org.
    There after a moderator enables a private reply – you can share temporary credentials to a staging environment where the issue has been reproduced – so that we can run some test and see what causes this and to provide a fix.

    Our developers analyzed the error, and there might be a fix that you can test if it works for you.

    in the file: /wp-content/plugins/woocommerce-multilingual/inc/class-wcml-emails.php you have to replace:

    if( '_payment_method_title' === $meta_key ){){

    With this code:

    
    if( $object_id && 'shop_order' === get_post_type( $object_id ) && '_payment_method_title' === $meta_key ){
    Thread Starter oseven

    (@oseven)

    Hello,

    I cannot find

    if( $object_id && '_payment_method_title' === $meta_key ){

    neither in the 4.1.2 version of the plugin (active in the live site) nor in the 4.1.3 version of the plugin (active in the staging site) in the class-wcml-emails.php file??

    Do you plan to incorporate this fix in 4.1.4? Then I can try to upgrade directly to this version and test.

    Oh, sorry my mistake – I edited the post to the correct code that need to be replaced.
    That code is in 4.1.3:
    if( '_payment_method_title' === $meta_key ){
    and yes the fix will be merged in the next release

    Thread Starter oseven

    (@oseven)

    hi, this resolved the issue. Thank you.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘White page after 4.1.3 upgrade’ is closed to new replies.