Comment "corriger" un message d'erreur wp-blog-header.php?
-
-
Où avez-vous cet appel?Soyez unpeupluspréciset veuilleznousmontrer lemodèle oùil apparaît.Il semble que vousessayez d'accéder à unepartie de wp (directement) sans le charger.Where have you got that call? Be a little more specific and please show us the template where it appears. It looks like you're trying to access some part of wp (directly) without loading it.
- 0
- 2011-03-25
- kaiser
-
5 réponses
- votes
-
- 2017-07-26
Je devais simplement résoudre ceproblèmeprécis.Mon site [Riverside Bartending School]esttombéen panneet commetous ceux qui ont ceproblème ou un rapport similaire,je n'aipasnonpluspu accéder aupanneau d'administration.C'est donc ce quej'aifait.
En utilisant cPanel (vouspouvez également utiliser FTP),j'ai supprimétous lesfichiers cacheet super cache.
Ensuite,j'aitéléchargé unenouvelle copie de Wordpress remplaçanttous lesfichiers Wordpress à l'exception du dossieret du contenu wp-content.
Troisièmement,j'ai changé lefichier wp-config.phppourm'assurer que lesinformations d'identification de labase de données étaient correctes.
Laprochaine étape consistait àtenter de se connecter aupanneau d'administration,et cela a été un succès.Puis réactivez lesplugins -encore unefois un succès.Testez le siteet l'altoil était opérationnel.
I just had to fix this exact issue. My site [Riverside Bartending School] went down and like the many with this issue or one similar report I too could not access the Admin Panel. So this is what I did.
Using cPanel (you can also use FTP) I deleted all the cache and super cache files.
Then I uploaded a fresh copy of Wordpress replacing all the Wordpress files except for wp-content folder and contents.
Thirdly, I changed the wp-config.php file to make sure that the database credentials were correct.
Next step was to attempt to login to the admin panel, and it was a success. Then reactivate the plugins - again a success. Test the site and viola it was up and running.
-
- 2011-03-25
Pour charger WordPress,il suffit de charger "wp-load.php" comme vous l'avezfait.Jene reconnaispas lafonction wp ()et jene l'aipastrouvée dans la source.Comme d'autrespersonnes semblent avoir lemêmeproblème sur Internet,je suppose que cela a à voir avec unplugin ou uneinstallation WordPresspeut-être obsolète.
Désactiveztous vospluginset voyez si cela résout leproblème.
Par curiosité: à quoi sert cefichier?
To load WordPress it is enough to load "wp-load.php" like you did. I don't recognize the wp() function and haven't found it in the source. As other people seem to have the same problem on the internet I guess it has to do with a plugin or a possibly outdated WordPress installation.
Disable all your plugins and see if that resolves the problem.
Out of curiosity: What is this file for?
-
C'est un site Web d'annuaire.Jemettaisjuste àjour WP àpartir dutableau debord?Je suis allé de l'avantet j'aitout suppriméet j'aienvoyé unenouvelleinstallationpar FTP.Tout semblebien fonctionnermaintenant.Merci de votre aide.It is a directory website. I was just updating WP from the dashboard? I have gone ahead and deleted everything and FTP'd a new install. Everything seems to be working fine now. Thanks for your help.
- 0
- 2011-03-27
- Marna
-
Ah oui,je vois!Jepensais que celafaisaitpartie de votre code dethème.Mais votre droit,celafaitpartie dunoyau WordPress.Heureux qu'une "réinstallation" l'ait corrigépour vous.Ah yes, I see! Thought that this was part of your theme code. But your right, it's part of the WordPress core. Glad that a "reinstall" fixed it for you.
- 0
- 2011-03-28
- marvinhagemeister
-
- 2011-03-25
Je suis d'accord.C'estgénéralement unplugin qui cause cesproblèmes dansmonexpérience.celapeut être un casse-tête,mais désactivertous vosplugins,puispasseren revueet activer vosplugins unpar unpermettra souvent d'identifier leproblème.
I agree. Usually it's a plugin that causes these issues in my experience. it can be a headache, but disabling all of your plugins, then going through and enabling your plugins one by one will often pinpoint the problem.
-
- 2016-11-07
J'étais confronté à cetteerreur lors du déplacement desfichiers demon site de hostgator vers un autre hôte,ce quej'aifait a été de compresser lesfichierset de lesenvoyerpar FTP vers lenouvel hôte.quelque chose agâché la compression desfichiers,lorsqueje les ai compressés avectar.gz,toutfonctionnaitbien.c'est ce quim'a aidé aprèsplusieurs heures,
probablement quelque chose avec l'encodage desfichiers.
I was facing this error when moving my site files from hostgator to other host, what I did was ZIP the files and FTP them to the new host. something messed up with compressing the files, when I compressed them with tar.gz everything worked fine. that's what helped me after several hours,
probably something with the encoding of files.
-
- 2020-06-20
Il y a unproblème avec WordPress. veuillezmettre àjour votre
wp_load.php
et utiliser ce code.<!-- start --> <?php /** * Bootstrap file for setting the ABSPATH constant * and loading the wp-config.php file. The wp-config.php * file will then load the wp-settings.php file, which * will then set up the WordPress environment. * * If the wp-config.php file is not found then an error * will be displayed asking the visitor to set up the * wp-config.php file. * * Will also search for wp-config.php in WordPress' parent * directory to allow the WordPress directory to remain * untouched. * * @package WordPress */ /** Define ABSPATH as this file's directory */ if ( ! defined( 'ABSPATH' ) ) { define( 'ABSPATH', dirname( __FILE__ ) . '/' ); } error_reporting( E_CORE_ERROR | E_CORE_WARNING | E_COMPILE_ERROR | E_ERROR | E_WARNING | E_PARSE | E_USER_ERROR | E_USER_WARNING | E_RECOVERABLE_ERROR ); /* * If wp-config.php exists in the WordPress root, or if it exists in the root and wp-settings.php * doesn't, load wp-config.php. The secondary check for wp-settings.php has the added benefit * of avoiding cases where the current directory is a nested installation, e.g. / is WordPress(a) * and /blog/ is WordPress(b). * * If neither set of conditions is true, initiate loading the setup process. */ if ( file_exists( ABSPATH . 'wp-config.php' ) ) { /** The config file resides in ABSPATH */ require_once( ABSPATH . 'wp-config.php' ); } elseif ( @file_exists( dirname( ABSPATH ) . '/wp-config.php' ) && ! @file_exists( dirname( ABSPATH ) . '/wp-settings.php' ) ) { /** The config file resides one level above ABSPATH but is not part of another installation */ require_once( dirname( ABSPATH ) . '/wp-config.php' ); } else { // A config file doesn't exist define( 'WPINC', 'wp-includes' ); require_once( ABSPATH . WPINC . '/load.php' ); // Standardize $_SERVER variables across setups. wp_fix_server_vars(); require_once( ABSPATH . WPINC . '/functions.php' ); $path = wp_guess_url() . '/wp-admin/setup-config.php'; /* * We're going to redirect to setup-config.php. While this shouldn't result * in an infinite loop, that's a silly thing to assume, don't you think? If * we're traveling in circles, our last-ditch effort is "Need more help?" */ if ( false === strpos( $_SERVER['REQUEST_URI'], 'setup-config' ) ) { header( 'Location: ' . $path ); exit; } define( 'WP_CONTENT_DIR', ABSPATH . 'wp-content' ); require_once( ABSPATH . WPINC . '/version.php' ); wp_check_php_mysql_versions(); wp_load_translations_early(); // Die with an error message $die = sprintf( /* translators: %s: wp-config.php */ __( "There doesn't seem to be a %s file. I need this before we can get started." ), '<code>wp-config.php</code>' ) . '</p>'; $die .= '<p>' . sprintf( /* translators: %s: Documentation URL. */ __( "Need more help? <a href='%s'>We got it</a>." ), __( 'https://wordpress.org/support/article/editing-wp-config-php/' ) ) . '</p>'; $die .= '<p>' . sprintf( /* translators: %s: wp-config.php */ __( "You can create a %s file through a web interface, but this doesn't work for all server setups. The safest way is to manually create the file." ), '<code>wp-config.php</code>' ) . '</p>'; $die .= '<p><a href="' . $path . '" class="button button-large">' . __( 'Create a Configuration File' ) . '</a>'; wp_die( $die, __( 'WordPress › Error' ) ); } <!-- end -->
et veuillez changer l'autorisation defichier 644en 444.
There is some WordPress issue. you please update your
wp_load.php
and using this code.<!-- start --> <?php /** * Bootstrap file for setting the ABSPATH constant * and loading the wp-config.php file. The wp-config.php * file will then load the wp-settings.php file, which * will then set up the WordPress environment. * * If the wp-config.php file is not found then an error * will be displayed asking the visitor to set up the * wp-config.php file. * * Will also search for wp-config.php in WordPress' parent * directory to allow the WordPress directory to remain * untouched. * * @package WordPress */ /** Define ABSPATH as this file's directory */ if ( ! defined( 'ABSPATH' ) ) { define( 'ABSPATH', dirname( __FILE__ ) . '/' ); } error_reporting( E_CORE_ERROR | E_CORE_WARNING | E_COMPILE_ERROR | E_ERROR | E_WARNING | E_PARSE | E_USER_ERROR | E_USER_WARNING | E_RECOVERABLE_ERROR ); /* * If wp-config.php exists in the WordPress root, or if it exists in the root and wp-settings.php * doesn't, load wp-config.php. The secondary check for wp-settings.php has the added benefit * of avoiding cases where the current directory is a nested installation, e.g. / is WordPress(a) * and /blog/ is WordPress(b). * * If neither set of conditions is true, initiate loading the setup process. */ if ( file_exists( ABSPATH . 'wp-config.php' ) ) { /** The config file resides in ABSPATH */ require_once( ABSPATH . 'wp-config.php' ); } elseif ( @file_exists( dirname( ABSPATH ) . '/wp-config.php' ) && ! @file_exists( dirname( ABSPATH ) . '/wp-settings.php' ) ) { /** The config file resides one level above ABSPATH but is not part of another installation */ require_once( dirname( ABSPATH ) . '/wp-config.php' ); } else { // A config file doesn't exist define( 'WPINC', 'wp-includes' ); require_once( ABSPATH . WPINC . '/load.php' ); // Standardize $_SERVER variables across setups. wp_fix_server_vars(); require_once( ABSPATH . WPINC . '/functions.php' ); $path = wp_guess_url() . '/wp-admin/setup-config.php'; /* * We're going to redirect to setup-config.php. While this shouldn't result * in an infinite loop, that's a silly thing to assume, don't you think? If * we're traveling in circles, our last-ditch effort is "Need more help?" */ if ( false === strpos( $_SERVER['REQUEST_URI'], 'setup-config' ) ) { header( 'Location: ' . $path ); exit; } define( 'WP_CONTENT_DIR', ABSPATH . 'wp-content' ); require_once( ABSPATH . WPINC . '/version.php' ); wp_check_php_mysql_versions(); wp_load_translations_early(); // Die with an error message $die = sprintf( /* translators: %s: wp-config.php */ __( "There doesn't seem to be a %s file. I need this before we can get started." ), '<code>wp-config.php</code>' ) . '</p>'; $die .= '<p>' . sprintf( /* translators: %s: Documentation URL. */ __( "Need more help? <a href='%s'>We got it</a>." ), __( 'https://wordpress.org/support/article/editing-wp-config-php/' ) ) . '</p>'; $die .= '<p>' . sprintf( /* translators: %s: wp-config.php */ __( "You can create a %s file through a web interface, but this doesn't work for all server setups. The safest way is to manually create the file." ), '<code>wp-config.php</code>' ) . '</p>'; $die .= '<p><a href="' . $path . '" class="button button-large">' . __( 'Create a Configuration File' ) . '</a>'; wp_die( $die, __( 'WordPress › Error' ) ); } <!-- end -->
and please change file permission 644 to 444.
-
Veuillez ** [modifier] votre réponse **,et ajouter uneexplication: **pourquoi ** celapourrait-il résoudre leproblème?Cela semble être unetrèsmauvaiseidée demodifier lenoyau sans aucune raison.Please **[edit] your answer**, and add an explanation: **why** could that solve the problem? It looks just like a very bad idea to edit core without any reason.
- 1
- 2020-06-20
- fuxia
-
D'accord @fuxia. @ sumer-signh-harawat - Si vous aviez lagentillesse de dire à @marna (et au reste d'entrenous qui lisons ceci)pourquoi lesmodifications apportées à `wp-load.php` résoudraient leproblème.Deplus,lesmodifications sont susceptibles d'être écrasées lors d'unemise àniveau de _WordPress_,il convient donc denoter que cettemodification doit être vérifiéepour s'assurer qu'elle reste après chaquemise àniveau (et ré-implémentée chaquefois qu'elleestmodifiée).Agreed @fuxia. @sumer-signh-harawat -- If you would be kind enough to tell @marna (and the rest of us reading this) why the changes to `wp-load.php` would fix the problem. Additionally, the changes are likely to be overwritten during a _WordPress_ upgrade, so it should be noted that this modification must be checked to ensure it remains after every upgrade (and re-implemented every time it is changed).
- 0
- 2020-06-21
- Mort 1305
J'ai récemmentmis àjour un siteet j'ai reçu lemessage d'erreur suivant:
J'ai vérifié lefichieret ilne semblepas y avoir deproblème,doncje nepeuxpas comprendre ce quine vapas?
Toute aide seraitgrandement appréciée.