sbstaskiewicz1

Here’s what I have coded:

<p class="post-footer">
<?php global $user_identity;
get_currentuserinfo();

echo ('Welcome ' . $user_identity . '.');
?>
<br />
You have posted <?php the_author_posts(); ?> times.
<br />
<em><a href="wp-admin/profile.php">Edit your Profile.</a></em>
</p>

<ul><li</li></ul>

If I add anything conditional, I get parsing errors up the wazoo. What is the best way to code the conditional statement in there without wrecking the whole thing?

That did it. It looks as if it was a coding error on the developer’s behalf. Line 91 of my code read:

<?endif; ?>

Which should have at least been coded as:

<? endif: ?> (space before the endif)

I never thought to go through line by line in the code to see if the PHP notation had changed. It’s strange because every where else in the document, any PHP function is listed as:

<?php some sort of code ?>

Oh well. Thanks for the tip.

I’ve come across the same error. I followed the upgrade directions exactly. I’m not sure what is causing this conflict.

Are we the only people with this issue?

What are you using your install for? Maybe we have a common issue (besides the current one). My install is located on a university web server that has some pretty tight limitations, but ran version 1.5.x fine.