• Resolved Contegi66

    (@contegi66)


    Hi there,

    I had a website running 4.0.1 hosted on gandi.net. Two days ago I manually update to 4.2.2 following codex procedure and something goes wrong as I got white death. I contacted hosting and after several attempts they tell me that most probably pieces of old version is conflicting with 4.2.2.
    Gandi proposed to completely delete htdocs contents and replace by one of my backup done under 4.0.1. but NOTHING CHANGED!

    I got this:
    Notice: Undefined index: HTTPS in /srv/data/web/vhosts/www.siua.eu/htdocs/wp-config.php on line 93

    Warning: file_get_contents(/etc/httpd/sites-enabled-user/httpd-vhost.conf-user): failed to open stream: No such file or directory in /srv/data/web/vhosts/www.siua.eu/htdocs/wp-config.php on line 101

    Parse error: syntax error, unexpected ‘}’ in /srv/data/web/vhosts/www.siua.eu/htdocs/wp-includes/load.php on line 830

    does anyone can tell me what I can do?

    PS: not only wp-admin but site is also obviously unreacheable.

    Thank you in advance,
    G

Viewing 13 replies - 1 through 13 (of 13 total)
  • Your white screen is returning a 500 Internal server error. This is a server side error and your hosting should give you more usable information. Old files do not conflict with new files in a proper WordPress upgrade.

    Error messages are very valuable pieces of information. However, in your case it would be helpful to know what code appears in wp-config.php lines 93 and 101 plus load.php on line 830. These lines of code do not exist on the site I checked.

    Thread Starter Contegi66

    (@contegi66)

    Hi wslade,

    thank you for your concern. indeed hosting should do more and I am not at all happy w/them (Gandi.net) as I am not a tech geek therefore I do not know what to do….

    note quite sure to catch what you meant on related code in the config.php. This is what I got on server side:

    88 define( ‘WP_DEBUG’, true );
    89
    90 /* That’s all, stop editing! Happy blogging. */
    91 $pageURL = ‘http’;
    92 if ($_SERVER[“HTTPS”] == “on”) {$pageURL .= “s”;}
    93 $pageURL .= “://”;
    94 if ($_SERVER[“SERVER_PORT”] != “80”) {
    95 $pageURL .= $_SERVER[“SERVER_NAME”].”:”.$_SERVER[“SERVER_PORT”];
    96 } else {
    97 $pageURL .= $_SERVER[“SERVER_NAME”];
    98 }
    99
    100 $virtual_host_file = file_get_contents(“/etc/httpd/sites-enabled-user/httpd-vhost.conf-user”);
    101 if (preg_match(‘/ServerName ‘.$_SERVER[“SERVER_NAME”].’/’, $virtual_host_file)) {
    102 define(‘WP_SITEURL’, $pageURL);
    103 } else {
    104 define(‘WP_SITEURL’, $pageURL.’/’);
    105 }
    106
    107 if (!defined(‘SYNOWORDPRESS’))
    108 define(‘SYNOWORDPRESS’, ‘Synology Inc.’);
    109
    110 /** Absolute path to the WordPress directory. */
    111 if ( !defined(‘ABSPATH’) )
    112 define(‘ABSPATH’, dirname(__FILE__) . ‘/’);
    113
    114 /** Sets up WordPress vars and included files. */
    115 require_once(ABSPATH . ‘wp-settings.php’);
    116 require_once(ABSPATH . ‘syno-misc.php’);

    that’s it.

    Related to load.php, i got this:

    828 }
    829 ‘WP_SETUP_CONFIG’ ) && file_exists( $location . ‘/admin-‘ . $locale . ‘.mo’ ) )
    830 load_textdomain( ‘default’, $location . ‘/admin-‘ . $locale . ‘.mo’ );
    break 2;
    }
    }
    }

    Thank you in advance for any suggestion/help

    G

    OK, how interesting. You have a lot of puzzling entries in these two files. It could simply be that your version is so old that its entries are no longer mentioned in the codex. I’m not looking for something to blame but 4.0.1 is like WAY old in WordPress years. ?? Your site is 13 revisions and 2 major updates out of date.

    You might try this: https://codex.www.ads-software.com/Upgrading_WordPress_-_Extended_Instructions. I suggest you try manually upgrading to 4.1 first. If you can get the site to run on 4.1 you can try for an auto update.

    If you can’t make the site run on 4.1, then then try for 4.2.2. Make sure you follow the instructions about database backups.

    Good luck. Please post your results.

    Thread Starter Contegi66

    (@contegi66)

    Thank you very much ! I will do it tomorrow and be sure let you know.

    with my kind regards,
    G

    Thread Starter Contegi66

    (@contegi66)

    Dear wslade,

    Thank you very very much for your help. I followed everything by the book and I got back all my work.

    I owe a belgian beer if you come by Brussels ??

    Thank you again

    Cheers

    What great news! Were you able to auto update at 4.1?

    Thread Starter Contegi66

    (@contegi66)

    I installed 4.1and it gives me automatic update to 4.2.2 which runs great for 10 minutes as now I got this:

    Internal Server Error

    The server encountered an internal error or misconfiguration and was unable to complete your request.

    Please contact the server administrator at [no address given] to inform them of the time this error occurred, and the actions you performed just before this error.

    More information about this error may be available in the server error log.

    Thread Starter Contegi66

    (@contegi66)

    Back on track again. well this hosting will kill me.. ??

    If you continue to have issues, post the recent errors from your error_log.

    I see you have a error notice. Just open up your /wp-config.php file and add the following line:

    define (‘WPLANG’, ”);

    This will cause a default to English. You will want to add your chosen language.

    Thread Starter Contegi66

    (@contegi66)

    Yes yes I was on it ?? Thank you again !

    Thread Starter Contegi66

    (@contegi66)

    Anyway I was thinking that from 4.0 WPLANG was deprecated. anyway even adding in wp-config.php, i still got the msg in wp-admin which is:

    Notice: Use of undefined constant WPLANG – assumed ‘WPLANG’ in /srv/data/web/vhosts/www.siua.eu/htdocs/wp-content/plugins/LayerSlider/classes/class.km.autoupdate.v3.php on line 74

    Now if I go to that file at line 74 I see this:

    72 ‘option’ => strtolower(basename(dirname($config[‘root’]))) . ‘_update_info’,
    73 ‘locale’ => WPLANG
    74 ));
    75 }

    I do not know what’s wrong with line 74

    Thread Starter Contegi66

    (@contegi66)

    never mind I solved it by leaving WPLANG empty in config.php :))

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Critical issue and white death’ is closed to new replies.