I posted a test comment to your latest post (“Commenting doesn’t work”) in Firefox 2.0.14. The post apparently went through. But, the page was broken. The last few lines are:
<li class="alt item" id="comment-2590">
<div class="commententry">
<img src="
Some PHP code in the theme of your comments.php is messed up. Could you post the part of that file around “<div class="commententry">“?
“The website cannot display the page.”
Was it a browser error message? If this was some sort of connection timeout, then there could have been a temporary disruption in your Internet connection, or the site’s server could have “hiccuped” or rebooted.
Thread Starter
moe321
(@moe321)
Thanks! Yes, I see that your comment went through.
Yes, “The website cannot display the page” was an IE error message, and it repeats each time I try to post a comment using IE. For some reason, it seems that both Safari and Firefox can now post comments, so it is right now only an IE issue.
Here is the code:
<div class="commententry">
<img src="<?php gravatar("R",80, "http://www.absentofi.org/wp-content/uploads/2007/04/transpix2.gif"); ?>" alt="" />
<?php comment_author_link() ?> says so:<span style="text-transform: lowercase;"><a href="#comment-<?php comment_ID() ?>" title="Comment Permalink"><?php comment_date('l, F j, Y') ?></a> <?php if (function_exists('quoter_comment')) { quoter_comment(); } ?> <?php edit_comment_link('| e','',''); ?></span>
The page is loading now, so, everything seems okay. Though, it looks my comment was flagged as spam and hidden from view. — I can see the comment in the source view.
All in all, this was probably some sort of server hiccup, so you should be good to go.
(@moe321)
15 years, 11 months ago
I have a browser related problem on my blog:
With Safari, it works fine to post a comment. But with Firefox and IE, after submitting a comment, this URL comes up:
http://www.absentofi.org/wp-comments-post.php
with this error message:
“The website cannot display the page.”
Any ideas? I tried switching themes, but that didn’t make a difference.
It is possible that this happened after I upgraded to WP 2.5 last week.