How do I «fix» a wp-blog-header.php error message?
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.
5 Answers 5
No need to go here and there. I was facing the same issue and here is the only solution Fix wp-blog-header.php error
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?
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.
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.
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.
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.
There is some WordPress issue. you please update your wp_load.php and using this code.
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." ), 'wp-config.php' ) . ''; $die .= '' . sprintf( /* translators: %s: Documentation URL. */ __( "Need more help? We got it." ), __( 'https://wordpress.org/support/article/editing-wp-config-php/' ) ) . '
'; $die .= '' . 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." ), 'wp-config.php' ) . '
'; $die .= '' . __( 'Create a Configuration File' ) . ''; wp_die( $die, __( 'WordPress › Error' ) ); >
and please change file permission 644 to 444.
magento setup:upgrade error "deployment configuration is absent"
[Magento\Setup\Exception]
Can't run this operation: deployment configuration is absent. Run 'magento setup:config:set --help' for options. setup:upgrade [--keep-generated] [--magento-init-params=". "]
How to fix it? Updating using the web updater gives the following errors: I asked my hosting provider to fix them and they did install the right php version 5.6 and all extensions recommended by magento and created a cron job but I still see the error. UPDATE: (from comments)
env.php wasn't there, when I run magento setup:config:set I get this error:
$ bin/magento setup:config:set
SQLSTATE[HY000] [2002] No such file or directory [InvalidArgumentException]
Parameter validation failed
Check to see if
@SteveJohnson env.php wasn't there, when I run magento setup:config:set i get this error pastebin.com/BDzxYGGU
The error indicates your Magento database user name and password don't match. I'm not sure it's a good idea to run your Magento database as root ; have you seen our MySQL setup instructions? Maybe try that and see if the command succeeds.