Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #1481192

    Hi
    I started seeing this error on the page below:

    Warning: Undefined array key “file” in /customers/e/d/0/joshuatree.dk/httpd.www/wp-includes/media.php on line 1444 Warning: Undefined array key “width” in /customers/e/d/0/joshuatree.dk/httpd.www/wp-includes/media.php on line 1458 Warning: Undefined array key “width” in /customers/e/d/0/joshuatree.dk/httpd.www/wp-includes/media.php on line 1463 Warning: Undefined array key “height” in /customers/e/d/0/joshuatree.dk/httpd.www/wp-includes/media.php on line 1463 Warning: Undefined array key “width” in /customers/e/d/0/joshuatree.dk/httpd.www/wp-includes/media.php on line 1458 Warning: Undefined array key “width” in /customers/e/d/0/joshuatree.dk/httpd.www/wp-includes/media.php on line 1463 Warning: Undefined array key “height” in /customers/e/d/0/joshuatree.dk/httpd.www/wp-includes/media.php on line 1463

    I deleted the header.php file from my child theme as I saw to do on another thread. That code looked like this and I don’t know what script I originally added to that file – can you see what that might be and if I need it?

    <?php
    	if ( ! defined('ABSPATH') ){ die(); }
    	
    	global $avia_config;
    	
    	$lightbox_option = avia_get_option( 'lightbox_active' );
    	$avia_config['use_standard_lightbox'] = empty( $lightbox_option ) || ( 'lightbox_active' == $lightbox_option ) ? 'lightbox_active' : 'disabled';
    	/**
    	 * Allow to overwrite the option setting for using the standard lightbox
    	 * Make sure to return 'disabled' to deactivate the standard lightbox - all checks are done against this string
    	 * 
    	 * @added_by Günter
    	 * @since 4.2.6
    	 * @param string $use_standard_lightbox				'lightbox_active' | 'disabled'
    	 * @return string									'lightbox_active' | 'disabled'
    	 */
    	$avia_config['use_standard_lightbox'] = apply_filters( 'avf_use_standard_lightbox', $avia_config['use_standard_lightbox'] );
    
    	$style 					= $avia_config['box_class'];
    	$responsive				= avia_get_option('responsive_active') != "disabled" ? "responsive" : "fixed_layout";
    	$blank 					= isset($avia_config['template']) ? $avia_config['template'] : "";	
    	$av_lightbox			= $avia_config['use_standard_lightbox'] != "disabled" ? 'av-default-lightbox' : 'av-custom-lightbox';
    	$preloader				= avia_get_option('preloader') == "preloader" ? 'av-preloader-active av-preloader-enabled' : 'av-preloader-disabled';
    	$sidebar_styling 		= avia_get_option('sidebar_styling');
    	$filterable_classes 	= avia_header_class_filter( avia_header_class_string() );
    	$av_classes_manually	= "av-no-preview"; /*required for live previews*/
    	$av_classes_manually   .= avia_is_burger_menu() ? " html_burger_menu_active" : " html_text_menu_active";
    	
    	/**
    	 * @since 4.2.3 we support columns in rtl order (before they were ltr only). To be backward comp. with old sites use this filter.
    	 */
    	$rtl_support			= 'yes' == apply_filters( 'avf_rtl_column_support', 'yes' ) ? ' rtl_columns ' : '';
    	
    ?><!DOCTYPE html>
    <html <?php language_attributes(); ?> class="<?php echo "html_{$style} ".$responsive." ".$preloader." ".$av_lightbox." ".$filterable_classes." ".$av_classes_manually ?> ">
    <head>
    <meta charset="<?php bloginfo( 'charset' ); ?>" />
    <?php
    /*
     * outputs a rel=follow or nofollow tag to circumvent google duplicate content for archives
     * located in framework/php/function-set-avia-frontend.php
     */
     if (function_exists('avia_set_follow')) { echo avia_set_follow(); }
    
    ?>
    
    <!-- mobile setting -->
    <?php
    
    if( strpos($responsive, 'responsive') !== false ) echo '<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1">';
    ?>
    
    <!-- Scripts/CSS and wp_head hook -->
    <?php
    /* Always have wp_head() just before the closing </head>
     * tag of your theme, or you will break many plugins, which
     * generally use this hook to add elements to <head> such
     * as styles, scripts, and meta tags.
     */
    
    wp_head();
    
    ?>
    		
    </head>
    
    <body id="top" <?php body_class( $rtl_support . $style." ".$avia_config['font_stack']." ".$blank." ".$sidebar_styling); avia_markup_helper(array('context' => 'body')); ?>>
    
    	<?php 
    	
    	do_action( 'ava_after_body_opening_tag' );
    		
    	if("av-preloader-active av-preloader-enabled" === $preloader)
    	{
    		echo avia_preload_screen(); 
    	}
    		
    	?>
    
    	<div id='wrap_all'>
    
    	<?php 
    	if(!$blank) //blank templates dont display header nor footer
    	{ 
    		 //fetch the template file that holds the main menu, located in includes/helper-menu-main.php
             get_template_part( 'includes/helper', 'main-menu' );
    
    	} ?>
    		
    	<div id='main' class='all_colors' data-scroll-offset='<?php echo avia_header_setting('header_scroll_offset'); ?>'>
    
    	<?php 
    		
    		if(isset($avia_config['temp_logo_container'])) echo $avia_config['temp_logo_container'];
    		do_action('ava_after_main_container'); 
    		
    	?>
    

    That did not clear up the warning though. I have hidden it by using this code in my wp-config as I found in another thread:

    ini_set('display_errors','Off');
    ini_set('error_reporting', E_ALL );
    define('WP_DEBUG', false);
    define('WP_DEBUG_DISPLAY', false);

    which works to hide it but not sure what the initial problem is?
    Can you help with this?
    thanks
    Nancy

    • This topic was modified 1 week ago by Munford.
    #1481242

    Hey Munford,
    Using a header.php in your child theme will often cause errors when you update as the new updated header.php will not be used.
    Please don’t add a header.php or footer.php to your child theme as this is the top reason for errors after updating, if you have a specific piece of code that you need to add to your header it is better to add it in your child theme functions.php, but I don’t see this in the code above.

    Best regards,
    Mike

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.