Databases
StackOverflow2013
Postsdbo
POTroubleshooting "parse error, unexpected '>'" error
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POTroubleshooting "parse error, unexpected '>'" error
    primarykey
    data
    text
    <p>I am getting this error that is reading</p> <blockquote> <p>Parse error: parse error, unexpected '>' in C:\wamp\www\about.php on line 11</p> </blockquote> <p>Here is my code:</p> <pre><code>&lt;?php session_start(); include ("include/header.php"); if (!isset($_SESSION['name'])){; header("Location:includeindex.php"); exit; } else{ TopNavigation("about Me -ECA236","About Me",$_SESSION['name']); echo "&lt;p&gt;Here is a little about me. I am a mother of twin girls who are 9 &lt;/p&gt; echo "&lt;p&gt;I been married for 5 years but been with my husband for 11 years &lt;/p&gt; echo "&lt;p&gt;I am attending college for Computer Programming and Database Mangament &lt;/p&gt; echo "&lt;p&gt;After I get done with this degree I am want to go back for Web Design &lt;/p&gt; echo "&lt;p&gt;since half my classes are web design now. I enjoy camping,bon fires and &lt;/p&gt; echo "&lt;p&gt;playing video games, hanging out with friends and family.&lt;/p&gt; Footer(); } ?&gt; </code></pre> <p>I have tried adding ; to the end and " to the end but the same thing pops up. Can someone sees what I am doing wrong.</p> <p>Here is the error i get when i add "; to the end of those:</p> <blockquote> <p>Warning: include(include/header.php) [function.include]: failed to open stream: No such file or directory in C:\wamp\www\about.php on line 3</p> <p>Warning: include() [function.include]: Failed opening 'include/header.php' for inclusion (include_path='.;C:\php5\pear') in C:\wamp\www\about.php on line 3</p> <p>Warning: Cannot modify header information - headers already sent by (output started at C:\wamp\www\about.php:3) in C:\wamp\www\about.php on line 5</p> </blockquote>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USandy
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POTroubleshooting "parse error, unexpected '>'" error
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POTroubleshooting "parse error, unexpected '>'" error
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    3. VO
      singulars
      1. POTroubleshooting "parse error, unexpected '>'" error
      1. USandy
      1. VTFavorite
    1. COuse like this `echo "<p>Here is a little about me. I am a mother of twin girls who are 9 </p>";`
      singulars
      1. POTroubleshooting "parse error, unexpected '>'" error
      1. USMuhammad Zeeshan
    2. CODid you try to put *both* at the end, in the right order?
      singulars
      1. POTroubleshooting "parse error, unexpected '>'" error
      1. USFelix Kling
    3. COYou do not need to use echo to output larger chunks of HTML. Close the PHP, output the HTML and then open PHP again. See my answer below for an example.
      singulars
      1. POTroubleshooting "parse error, unexpected '>'" error
      1. UShakre
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload