Title: parse error: syntax error
Last modified: August 21, 2016

---

# parse error: syntax error

 *  [Alineke](https://wordpress.org/support/users/alineke/)
 * (@alineke)
 * [12 years, 9 months ago](https://wordpress.org/support/topic/parse-error-syntax-error-68/)
 * Hello,
 * I wanted to do the Google verification with the metatag, so I copy the code and
   put it between <head> and <Body>, but the verification didn’t work. So I tried,
   and tried….Then I went to my site and got this:
    Parse error: syntax error, unexpected‘/’
   in /home4/aline/public_html/wp-content/themes/twentyeleven/header.php on line
   60 I’m new to all this and don’t know what to do, can someone help me? I know
   I did something wrong on line 60, but how can I see where line 60 is? my site
   is [http://www.gratiskinderspullen.com](http://www.gratiskinderspullen.com) This
   is what I have:
 *     ```
       /**
        * The Header for our theme.
   
       * Displays all of the <head> section and everything up till <div id="main">
        *
        * @package WordPress
        * @subpackage Twenty_Eleven
        * @since Twenty Eleven 1.0
        */
        ?><!DOCTYPE html>
        <!--[if IE 6]>
        <html id="ie6" <?php language_attributes(); ?>>
        <![endif]-->
        <!--[if IE 7]>
        <html id="ie7" <?php language_attributes(); ?>>
        <![endif]-->
        <!--[if IE 8]>
        <html id="ie8" <?php language_attributes(); ?>>
        <![endif]-->
        <!--[if !(IE 6) | !(IE 7) | !(IE 8) ]><!-->
        <html <?php language_attributes(); ?>>
        <!--<![endif]-->
        <head
   
       <meta charset="<?php bloginfo( 'charset' ); ?>" />
        <meta name="viewport" content="width=device-width" />
        <title><?php
        /*
        * Print the <title> tag based on what is being viewed.
        */
        global $page, $paged;
   
       wp_title( '|', true, 'right' );
   
       // Add the blog name.
        bloginfo( 'name' );
   
       // Add the blog description for the home/front page.
        $site_description = get_bloginfo( 'description', 'display' );
        if ( $site_description && ( is_home() || is_front_page() ) )
        echo " | $site_description";
   
       // Add a page number if necessary:
        if ( $paged >= 2 || $page >= 2 )
        echo ' | ' . sprintf( __( 'Page %s', 'twentyeleven' ), max( $paged, $page ) );
   
       ?></title>
        <link rel="profile" href="http://gmpg.org/xfn/11" />
        <link rel="stylesheet" type="text/css" media="all" href="<?php bloginfo( 'stylesheet_url' ); ?>" />
        <link rel="pingback" href="<?php bloginfo( 'pingback_url' ); ?>" />
        <!--[if lt IE 9]>
        <script src="<?php echo get_template_directory_uri(); ?>/js/html5.js" type="text/javascript"></script>
        <![endif]-->
        <?php
        /* We add some JavaScript to pages with the comment form
        * to support sites with threaded comments (when in use).
        */
        if ( is_singular() && get_option( 'thread_comments' ) )
        wp_enqueue_script( 'comment-reply' );
        /><?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 <?php body_class(); ?>>
        <div id="page" class="hfeed">
        <header id="branding" role="banner">
        <hgroup>
        <h1 id="site-title"><span>" title="<?php echo esc_attr( get_bloginfo( 'name', 'display' ) ); ?>" rel="home"><?php bloginfo( 'name' ); ?></span></h1>
        <h2 id="site-description"><?php bloginfo( 'description' ); ?></h2>
        </hgroup>
   
       <?php
        // Check to see if the header image has been removed
        $header_image = get_header_image();
        if ( $header_image ) :
        // Compatibility with versions of WordPress prior to 3.4.
        if ( function_exists( 'get_custom_header' ) ) {
        // We need to figure out what the minimum width should be for our featured image.
        // This result would be the suggested width if the theme were to implement flexible widths.
        $header_image_width = get_theme_support( 'custom-header', 'width' );
        } else {
        $header_image_width = HEADER_IMAGE_WIDTH;
        }
        ?>
        ">
        <?php
        // The header image
        // Check if this is a post or page, if it has a thumbnail, and if it's a big one
        if ( is_singular() && has_post_thumbnail( $post->ID ) &&
        ( /* $src, $width, $height */ $image = wp_get_attachment_image_src( get_post_thumbnail_id( $post->ID ), array( $header_image_width, $header_image_width ) ) ) &&
        $image[1] >= $header_image_width ) :
        // Houston, we have a new header image!
        echo get_the_post_thumbnail( $post->ID, 'post-thumbnail' );
        else :
        // Compatibility with versions of WordPress prior to 3.4.
        if ( function_exists( 'get_custom_header' ) ) {
        $header_image_width = get_custom_header()->width;
        $header_image_height = get_custom_header()->height;
        } else {
        $header_image_width = HEADER_IMAGE_WIDTH;
        $header_image_height = HEADER_IMAGE_HEIGHT;
        }
        ?>
        <img src="<?php header_image(); ?>" width="<?php echo $header_image_width; ?>" height="<?php echo $header_image_height; ?>" alt="" />
        <?php endif; // end check for featured image or standard header ?>
   
       <?php endif; // end check for removed header image ?>
   
       <?php
        // Has the text been hidden?
        if ( 'blank' == get_header_textcolor() ) :
        ?>
        <div class="only-search<?php if ( $header_image ) : ?> with-image<?php endif; ?>">
        <?php get_search_form(); ?>
        </div>
        <?php
        else :
        ?>
        <?php get_search_form(); ?>
        <?php endif; ?>
   
       <nav id="access" role="navigation">
        <h3 class="assistive-text"><?php _e( 'Main menu', 'twentyeleven' ); ?></h3>
        <?php /* Allow screen readers / text browsers to skip the navigation menu and get right to the good stuff. */ ?>
        <div class="skip-link">"><?php _e( 'Skip to primary content', 'twentyeleven' ); ?></div>
        <div class="skip-link">"><?php _e( 'Skip to secondary content', 'twentyeleven' ); ?></div>
        <?php /* Our navigation menu. If one isn't filled out, wp_nav_menu falls back to wp_page_menu. The menu assigned to the primary location is the one used. If one isn't assigned, the menu with the lowest ID is used. */ ?>
        <?php wp_nav_menu( array( 'theme_location' => 'primary' ) ); ?>
        </nav><!-- #access -->
        </header><!-- #branding -->
   
       <div id="main">
       ```
   
 * _[Please post code or markup between backticks or use the code button. Or better
   still – use a [pastebin](http://pastebin.com/). Your posted code may now have
   been permanently damaged/corrupted by the forum’s parser.]_

Viewing 4 replies - 1 through 4 (of 4 total)

 *  [wpismypuppet](https://wordpress.org/support/users/wordpressismypuppet/)
 * (@wordpressismypuppet)
 * [12 years, 9 months ago](https://wordpress.org/support/topic/parse-error-syntax-error-68/#post-3957577)
 * You should consider using a program that understands PHP code as you type and
   can let you know of errors before they are published. One such program is DreamWeaver…
   and though I don’t like DreamWeaver for very much, the code view is rather useful…
   plus it has a built in FTP client. Those are the ONLY two good features about
   it.
 * At any rate… look in your code for these lines:
 *     ```
       if ( is_singular() && get_option( 'thread_comments' ) )
       wp_enqueue_script( 'comment-reply' );
       /><?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.
       */
       ```
   
 * and remove this line completely:
 * `/><?php`
 * You should be good after that.
 *  [esmi](https://wordpress.org/support/users/esmi/)
 * (@esmi)
 * [12 years, 9 months ago](https://wordpress.org/support/topic/parse-error-syntax-error-68/#post-3957579)
 * Do not edit the Twenty Eleven theme. First [create a child theme for your changes](http://codex.wordpress.org/Child_Themes).
   Or install a [custom CSS plugin](http://wordpress.org/extend/plugins/search.php?q=custom+css).
   Re-upload a fresh, unpacked, copy of the Twenty Eleven folder to wp-content/themes
   using [FTP](http://codex.wordpress.org/FTP_Clients) or whatever file management
   application your host provides.
    [http://wordpress.org/themes/twentyeleven](http://wordpress.org/themes/twentyeleven)
 *  Thread Starter [Alineke](https://wordpress.org/support/users/alineke/)
 * (@alineke)
 * [12 years, 9 months ago](https://wordpress.org/support/topic/parse-error-syntax-error-68/#post-3957600)
 * Thank you for your help, I’ve got my website back but still have this:* * [@package](https://wordpress.org/support/users/package/)
   WordPress * @subpackage Twenty_Eleven * [@since](https://wordpress.org/support/users/since/)
   Twenty Eleven 1.0 */ ?>
    I removed the other codes, but I can’t find this code.
   my site also changed, other layout,…
 *  [wpismypuppet](https://wordpress.org/support/users/wordpressismypuppet/)
 * (@wordpressismypuppet)
 * [12 years, 9 months ago](https://wordpress.org/support/topic/parse-error-syntax-error-68/#post-3957603)
 * You probably just need to add <?php to the very top of the page, before anything
   else. However, I would take esmi’s advice to heart.
 * I didn’t notice at first, but you are directly editing the Twenty Eleven theme
   and that’s a no no. You need to make a child theme instead. The reason being 
   is that one day Twenty Eleven is going to have an update, and either you or the
   person you are making this site for is going to click the update button, and 
   then you’ll lose ALL of your work.
 * Since you are just starting, do as esmi says and start from scratch, then create
   a child theme, then re-do your changes there.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘parse error: syntax error’ is closed to new replies.

 * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
 * 4 replies
 * 3 participants
 * Last reply from: [wpismypuppet](https://wordpress.org/support/users/wordpressismypuppet/)
 * Last activity: [12 years, 9 months ago](https://wordpress.org/support/topic/parse-error-syntax-error-68/#post-3957603)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics
