Support » Fixing WordPress » Warning: Cannot modify header information erorr leading into parse/syntax errors

  • This is the error I keep receiving:

    Warning: Cannot modify header information – headers already sent by (output started at /home/alur007/public_html/wp-content/themes/Unicorn/options.php:2) in /home/alur007/public_html/wp-includes/pluggable.php on line 881

    After reading through the troubleshooting guides in the WordPress codex @ How Do I Solve The Headers Already Sent Warning Problem, it appears my error is on line 2 of the options.php.

    When I get there and do as the link above describes, I then receive this error:

    Parse error: syntax error, unexpected ‘<‘ in /home/alur007/public_html/wp-content/themes/Unicorn/options.php:2

    The beginning of the code found in this area is:

    <!--CSS Options-->
    	<script> <style type="text/css" media="screen">
    		 a:hover,.sf-menu li.current-menu-item a, .sf-menu li a:hover,
    		.widget_calendar table#wp-calendar>tbody>tr>td>a,
    		.widget_calendar tfoot>tr>td#prev a,.widget_calendar tfoot>tr>td#next a,
    		.comment-post-title, .footer-widget a:hover, .credits a:hover ,
    		.footer-widget.widget_calendar tfoot>tr>td#prev a,.widget_calendar tfoot>tr>td#next a,
    		.half-meta .half-meta-time .day,.half-meta .half-meta-time .year,.half-meta .half-meta-time .month, .caption-time .day, .flex-caption h3 a:hover, form.nd_form p a:hover.forgotten, span.reedwan-following-info:hover
    			color:<?php echo '#'.get_option('reedwan_generalcolor'); ?>;
    		.sf-menu li a:hover, .sf-menu li.current-menu-item a{
    			border-bottom-color:<?php echo '#'.get_option('reedwan_generalcolor'); ?>;
    		::-moz-selection {background:<?php echo '#'.get_option('reedwan_generalcolor'); ?>;}
    		::selection {background:<?php echo '#'.get_option('reedwan_generalcolor'); ?>;}

    Obviously, this error is an issue with my theme. I just purchased it and installed it today, and seem to be the only person who has had this issue with it. When I revert back to my old theme I have no issues, but I would like to figure this out so that the money is not wasted.

    Any help would be appreciated.

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


    Have you contacted your theme’s vendors with this issue? forums are meant for supporting the core application, themes and plugins that are distributed on

    I have indeed, but as it is the weekend I don’t expect to be hearing back before Monday. I wouldn’t be here without going that route first, and wouldn’t have bothered at all if I hadn’t seen how prevalent an issue this seems to be.

    Unfortunately, every topic on this has a different answer and a different method due to it being a different file each time for the most part, and I’ve yet to find one that I can get to work so I thought I’d see if anyone could identify the problem.

    I know it is something simple, but each fix I attempt has either done nothing, or led to other versions of the parse error/syntax error disabling the website.

    Yes, I posted that very link in my original post as one of the methods I had attempted to correct the header issue. What is described there ended up with me getting the parse/syntax error that I described, disabling the website completely.

    Oh sorry, my bad…unfortunately I don’t know how to solve that one either.

    It’s alright, I appreciate the attempt at any rate. It was a shot in the dark that I would find some help, may have to just wait until Monday and revert to the old theme.

    Are you stuck entirely — out of the old theme too now? If so, you could try accessing your site via FTP — and rename the bad theme folder — then it should automatically revert you to the default WP theme and you should be able to then activate your old theme.

    My original theme is fine when I revert back, it’s just this new one with the errors that I can’t seem to work out. Thanks though.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Warning: Cannot modify header information erorr leading into parse/syntax errors’ is closed to new replies.