Parse Error on custom-header

  • Resolved finster123

    (@finster123)


    6 years, 8 months ago

    Hi,
    My site is currently down with the following error. The custom-header.php file has been updated on March 16th so I’m guessing there’s an issue there that’s causing the error. I have tried disabling all plugins but no joy. Any ideas what might be causing this?
    Thanks,
    Stephen

    Parse error: syntax error, unexpected '<', expecting end of file in /home6/parentf5/public_html/wp-content/themes/twentyseventeen/inc/custom-header.php on line 17

Viewing 3 replies - 1 through 3 (of 3 total)
  • Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    Maybe the theme didn’t update properly, but to make sure there’s nothing sinister going on can you paste the code from lines 1 to 20 here in this thread?

    You can find this file through FTP or using a file managing tool available in your hosting provider’s control panel.

    Thread Starter finster123

    (@finster123)

    Thanks Andrew,

    <?php
/**
 * Custom header implementation
 *
 * @link https://codex.www.ads-software.com/Custom_Headers
 *
 * @package WordPress
 * @subpackage Twenty_Seventeen
 * @since 1.0
 */

/**
 * Set up the WordPress core custom header feature.
 *
 * @uses twentyseventeen_header_style()
 */
<div align="center">
<span style="font-size: 22px;"><i class="fa fa-phone"> CALL US NOW <a href="tel:0000000000"></i> 000-000-0000</span>
</div>
function twentyseventeen_custom_header_setup() {
    Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    I’m sorry to say you’ve been hacked.

    Get a fresh cup of coffee, take a deep breath and carefully follow this guide. When you’re done, you may want to implement some (if not all) of the recommended security measures.

    If you’re unable to clean your site(s) successfully, there are reputable organizations that can clean your sites for you. Sucuri and Wordfence are a couple.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Parse Error on custom-header’ is closed to new replies.