White screen of death when I'm trying to make a new post

I have it but I don’t know if it was used for this installation. I got help when I migrated my website from the previous server to this one. But there is on the cpanel.

This is the output from the Pale Moons console. With cleared cache and a new session.

The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol.

To see if it was used softaculos just see if it records the install under the “all installations” tab.

But the post I made had no character encoding. It was in plain text and I didnt’t load any images neither I formatted the text.

If I am not mistaken character encoding depends on core? How can that be messed up?

Edited to add: character encoding is not the same as “page formatting”. It’s the standard whole site uses to map characters and render things like “&”.

In your theme’s header.php, can you add the following line:

<meta http-equiv="content-type" content="text/html; charset=utf-8" />

Replace any other <meta charset=... with the above if necessary.

Where is the all installations tab?

What do you mean when you say that the character encoding depends on the core? I haven’t touched anything on the configuration of the server and I haven’t changed anything on my browser.

The problem appeared last night when I tried to change a permalink.

Ok… I’m in the cpanel and I"m viewing the header.php file. Is this the file that you want me to edit?
If so where exactly do I have to add the line?

I can post the whole file here in text if it is needed.

Character encoding is a line of code in core and sometimes themes that establishes the character map for the whole site (can be relevant to how db entry are stored and takes care of rendering characters among different browsers since every browser render characters differently. A very common standard is utf-8. It can be messed up by minification…

For softaculos go to CPanel, click softaculos icon, then in the top right angle of the screen there are icons. Click the one resembling a cardboard box that brings you to the page where all installs under it are listed.

There should be an opening <head> and a closing </head> tag somewhere at the top. Place that line immediately below the opening <head> tag.

Edit

If there’s already a line as shown below:

<meta charset="<?php bloginfo( 'charset' ); ?>">

place the new line below this.

I found it. I don’t have any installations from Softaculos.

So it was installed manually and this means that the install has custom parameters.

As I am not sure about the tag here are the first lines of the header.php of my theme.

<?php
/**
 * The header for this theme.
 *
 * Displays all of the <head> section and everything up till <div id="content">
 * @package Pure_and_Simple
 * @since 1.0.0
 */
?>


<!DOCTYPE html>
<html <?php language_attributes(); ?>>
<head>
	<meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta charset="<?php bloginfo( 'charset' ); ?>">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    
    <link rel="profile" href="https://gmpg.org/xfn/11">
    <link rel="pingback" href="<?php bloginfo( 'pingback_url' ); ?>">   
    <?php wp_head(); ?>
</head>
    
<body <?php body_class(); ?>>
<!-- add move to top feture -->
<?php do_action( 'lr_move_to_top', 'marialena'); ?>

<?php $pagewidth = get_theme_mod( 'page_width', 'boxwide' ); ?>
<div id="page" class="<?php echo $pagewidth; ?> hfeed site">
	<a class="skip-link screen-reader-text" href="#content"><?php _e( 'Skip to content', 'marialena' ); ?></a>

Doesn’t look complete. But never mind, can you add the new line just above <?php wp_head(); ?>

Of course it was installed manually because I hosted the websites in a friends server who did all manually and then I got the backup and host it to another server.

But what all these have to do with the problem.
The website was all right up until last night when I tried first to edit the permalink of an already existing post.

It didn’t save the edit and then it appeared the white screen on each and every attempt I made to publish a new post.
The only post that I managed to publish after I uploaded the database backup was one that already existed.

I’ll post it without quotes.

Here is the whole thing.

application/x-httpd-php header.php ( HTML document, ASCII text, with CRLF line terminators )

<?php
/**
 * The header for this theme.
 *
 * Displays all of the <head> section and everything up till <div id="content">
 * @package Pure_and_Simple
 * @since 1.0.0
 */
?>


<!DOCTYPE html>
<html <?php language_attributes(); ?>>
<head>
	<meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta charset="<?php bloginfo( 'charset' ); ?>">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    
    <link rel="profile" href="https://gmpg.org/xfn/11">
    <link rel="pingback" href="<?php bloginfo( 'pingback_url' ); ?>">   
    <?php wp_head(); ?>
</head>
    
<body <?php body_class(); ?>>
<!-- add move to top feture -->
<?php do_action( 'lr_move_to_top', 'marialena'); ?>

<?php $pagewidth = get_theme_mod( 'page_width', 'boxwide' ); ?>
<div id="page" class="<?php echo $pagewidth; ?> hfeed site">
	<a class="skip-link screen-reader-text" href="#content"><?php _e( 'Skip to content', 'marialena' ); ?></a>

    <?php get_template_part( 'partials/logo-group' ); ?>	
    
<div class="navigation clearfix" style="background-color: <?php echo get_theme_mod( 'menu_bg', '#789993' ); ?>;">
  	<div class="container">
      	<div class="row">
          <div class="col-md-12">
             <div id="navbar" class="navbar">
				<nav id="primary-navigation" class="site-navigation primary-navigation" role="navigation">
				<div class="toggle-container visible-xs visible-sm hidden-md hidden-lg" style="background-color: <?php echo get_theme_mod( 'menu_bg', '#789993' ); ?>;">
                <button class="menu-toggle"><?php _e( 'Menu', 'marialena' ); ?></button></div>
               
				<a class="screen-reader-text skip-link" href="#content"><?php _e( 'Skip to content', 'marialena' ); ?></a>
             	<?php wp_nav_menu( array( 'theme_location' => 'primary', 'container' => false, 'menu_class' => 'nav-menu', 'fallback_cb' => 'wp_page_menu' ) ); ?>
         
			</nav>
			</div>
            
			</div>
		</div>      
	</div>
</div><!-- .navigation -->
    
<?php get_sidebar( 'banner' ); ?>

<?php 
	$breadcrumbstyle = get_theme_mod( 'breadcrumb_bg', '#e6e6e6' );
	$breadcrumbcolour = get_theme_mod( 'breadcrumb_text', '#9e9e9e' );
	if(! is_front_page() && !is_attachment() ) : 
		if(function_exists('bcn_display')) {
			echo '<div id="breadcrumb-wrapper" style="background-color:' . $breadcrumbstyle . '; color: ' . $breadcrumbcolour . ';" role="nav"><div class="container"><div class="row"><div class="col-md-12"><i class="fa fa-home"></i> ';
				bcn_display();
			echo '</div></div></div></div>';
		}
	 endif; 
?>

<?php get_sidebar( 'cta' ); ?>

    <?php get_sidebar( 'featured-top' ); ?>


	<div id="primary" class="content-area">
		<div id="content" class="site-content" style="background-color: <?php echo get_theme_mod( 'content_bg', '#ffffff' ); ?>; color:<?php echo get_theme_mod( 'contenttext', '#767676' ); ?>;" role="main">

I’ve sent you a DM.

Not sure if this is relevant, I had a similar problem recently, website displayed, admin area worked except for saving pages.
Apparently I had triggered a mod security rule and once the id was whitelisted, no further problem

1 Like

I’ve had this error coming up again with the new release, though it doesn’t WSOD me. I removed the reference to the skin map in the style sheet at the very end of the line in this file:

/wp-includes/js/tinymce/skins/lightgray/skin.min.css

This is the offending part.

/*# sourceMappingURL=skin.min.css.map */

Removing that reference to the source map will clear that error from your console; this is related to auto-minification of the file, if I understand correctly…

This was patched last year, but, appears to be back.

I checked the skin.min.css and there is no such entry ( at least the text editor wasn’t able to find it) in the skin.min.css.

I have though the css in backup unminified.

If I replace the css in its unminified version and delete completely the plugin will it remove the problem in the file that is in the cpanel?