richsalvucci

Hi Jagdeepreel,

This sounds lke it could be a theme or plugin conflict. There are a few things you can try.

• Try reloading WordPress core files via the admin or via FTP
• Try using one of the base themes like twentyseventeen or twentysixteen. If that works the conflict is in the theme and you should reach out to the theme developer.
• Disable all plugins via the Dashboard or via FTP. You should keep a default theme activated during this process. If disabling all of the plugins works you can reenable them individually and see which one is causing your issue. Then you can reach-out to that plugin developer.

I hope these steps help.

-Rich

Hi Rob,

I am glad you were able to fix it. On the multisites that I am using domain mapping I have used the WPMU Domain mapping and it works fairly well, but that is a paid plugin.

-Rich

Based on what the error says I would start by renaming the code snippet plugin folder on the ftp and see if that allows the site to load. If that is what you meant when you said fix the problem try deleting it completely. The other error that I see is related to a Bluehost must use page caching plugin. You should be able to disable that via the dashboard once you get back in.

• This reply was modified 7 years, 4 months ago by richsalvucci.

Hi Rob,

I can’t seem to recreate the error in Chrome. All of the images I checked seemed to be working as expected. Are you using a domain mapping plugin? What does the enqueue script look like for Contact Form 7?

-Rich

Hi Rob,

Those letters after the .uks are the version numbers that at automatically added by WordPress. It is done for cache busting so the latest files are automatically being loaded and not an older version of your CSS or JS. The instructions to remove the version numbers be found on here.

https://www.codementor.io/tips/8369241717/remove-version-number-from-css-js-in-wordpress-theme

If you are changing the styles.css it would be where you see red in the code above, you would want to change that to the color you want the current page menu item to be. It is generally a good idea to have it be a different color so the user knows where they are.
Depending on what theme you are using it is very likely a setting. It looks like you are using a child theme of Flat here is the Flat documentation. https://docs.themeisle.com/article/165-flat-documentation#s2 Poke around in the customizer and you will probably find it.

You can paste this code in below line 133 in the styles.css or change those lines yourself.

.current_page_item li {
    background-color: ***Your new color goes here*** !important;
    color: ***Your new color goes here*** !important;
}

• This reply was modified 7 years, 4 months ago by richsalvucci.

That is based on the CSS on line 133 of your styles.css it is because that is the current menu item. This is the rule that needs changing

.current_page_item li {
    background-color: red !important;
    color: red !important;
}

I used Chrome dev tools to discover the issue. https://developer.chrome.com/devtools

There may be a setting in your theme for current menu item as well.

Hi Ben,

It is now loading in around 500ms. We switched to a VPS with dedicated resources and that resolved the issue.

Thanks,
Rich

@bsokic It appears to only be an intermittent issue for me. With Yoast deactivated it is working as expected.

This bug appears to be preventing the use of the Settings panel as well.

Marking as resolved.

I realized my problem. I was improperly calling the theme mod it needed to be:

function add_css_to_head() {
	$custom_css = get_theme_mod( 'custom_css' );
	?>
         <style type="text/css">
             <?php echo $custom_css; ?>
             h6 { color: lime;}
         </style>
    <?php
}
add_action( 'wp_head', 'add_css_to_head');

I am actually no longer getting the white screen at this point, but there seems to be an issue with the add_css_to_head function. I am seeing the style tag and the hard coded h6, but not the $custom_css values:

function add_css_to_head() {
	$custom_css = get_theme_mod('add_custom_css');
	?>
         <style type="text/css">
             <?php echo $custom_css; ?>
             h6 { color: lime;}
         </style>
    <?php
}
add_action( 'wp_head', 'add_css_to_head');

Hi Rajesh,

Sorry for the delay in response. I started getting a 500 error on the site that need to be resolved. When I turn on the debugging I get this error message:

Notice: wp_deregister_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /*****/*****/public_html/mrmicrosite/wp-includes/functions.php on line 3622

I just fixed that debugging error, I was not enqueuing the scripts I was only enqueuing the styles. My issue with the customizer is still persisting. I did change the code slightly to fix the 500 error :

function add_custom_css( $wp_customize ) {
	//Add CSS section
	$wp_customize->add_section( 'custom_css_section', array(
		'title' => 'Custom CSS',
		'priority' => 150,
	) );

	//Add CSS setting
	$wp_customize->add_setting( 'custom_css', array(
		'default' => '',
		'transport' => 'refresh',
	));

	//Add CSS Control
$wp_customize->add_control(
    new WP_Customize_Control(
        $wp_customize,
        'custom_css',
        array(
            'label'          => __( 'Custom CSS', 'custom_css' ),
            'section'        => 'custom_css_section',
            'settings'       => 'custom_css',
            'type'           => 'textarea',
        )
    )
);
}
add_action( 'customize_register', 'add_custom_css');

function add_css_to_head() {
	$custom_css = get_theme_mod('add_custom_css');
	?>
         <style type="text/css">
             <?php echo $custom_css; ?>
             h6 { color: lime;}
         </style>
    <?php
}

Thanks for the help.