Parse Error Mystery!
-
All of the sudden, I am seeing a “Parse Error” on my portfolio. I can’t seem to get rid of it. Anyone have an idea on how to get rid of this? I would really appreciate it.
The message reads “Parse error: syntax error, unexpected T_STRING in /home/merbal/meredithbaldwin.com/wp-content/themes/pilcrow/footer.php on line 36”
I am currently using the Pilcrow theme by Automattic – and I would really like to keep this if possible. Thanks in advance for any help you are willing to give me!
The blog I need help with is: (visible only to logged in users)
-
The blog you specified at http://www.meredithbaldwin.com does not appear to be hosted at WordPress.com.
This support forum is for blogs hosted at WordPress.com. If your question is about a self-hosted WordPress blog then you’ll find help at the WordPress.org forums.
If you don’t understand the difference between WordPress.com and WordPress.org, you may find this information helpful.
If you forgot to include a link to your blog, you can reply and include it below. It’ll help people to answer your question.
This is an automated message.
-
-
http://www.meredithbaldwin.com/ is not hosted at WordPress.com and you need to be over at wordpress.ORG for assistance.
http://meredithbaldwin.wordpress.com/ is hosted at WordPress.com but that’s not the blog you’re using.
-
Not according to this…
http://ismyblogworking.com/meredithbaldwin.comOr are you talking about a different blog?
-
I use wordpress.com for both of these. However, after purchasing my domain – I am only using http://www.meredithbaldwin.com.
Regardless – can anyone help me remove this message? I don’t know what has happened and why I can’t get it to disappear off of my webpage. Everything was working fine this morning.
-
I can assure you that is NOT a WordPress.com blog. Otherwise, I’d see a grey admin bar when navigating through it right now. (Among other things).
That message is probably caused by some error with your PHP code, but since we cannot handle PHP code ourselves at WordPress.com, we are not in a position to help. So please understand that you REALLY need to go to the correct forums at http://wordpress.org/support/ for assistance.
P.S. If you haven’t already done so, please familiarize yourself with the major differences between WordPress.com (where you are posting) and WordPress.org (the makers of the software you are using). http://en.support.wordpress.com/com-vs-org/
-
-
I’ve tried to login to wordpress.org and it tells me I don’t exist as a member. So I am pretty sure that I am working with wordpress.com. It’s the only site of the two that will let me log in and access my portfolio.
-
WordPress.org only supplies software. It’s not a web host.
You need to contact your web host for your blog. We cannot help you here, as that is not a WordPress.com site.
-
To use the WordPress.org forum, you need to create a username first. Whatever username you have at WordPress.com or with your hosting provider will not work. Thank you and good luck.
-
But I use wordpress.com! I promise. That’s how I’ve been running my site. Everything is through wordpress.com.
-
But it is not hosted here, I assure you. You are using WordPress 3.2.1, which is not available here.
We cannot answer you here. At the WordPress.org forums you may be able to find a way to fix that error; we can’t help you because it doesn’t occur here.
-
This site, http://www.meredithbaldwin.com/ , in the source code has the following:
<meta name="generator" content="WordPress 3.2.1" />If the site was hosted here at wordpress.com, it would say this in the source code:
<meta name="generator" content="WordPress.com" />A “whois” lookup reveals that http://www.meredithbaldwin.com/ is hosted at dreamhost, which makes it a self-hosted wordpress installation.
You need to create a username and get a password over at http://wordpress.ORG/support/ as that is where the self-hosted version of wordpress is supported. They can help you there because they are familiar with the software you are using. We here at wordpress.COM, are not.
- The topic ‘Parse Error Mystery!’ is closed to new replies.