Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • After playing around I’ve found out that the problem isn’t quite what I thought it was. Basically I had set the auto-generated “about” page of a new blog to be the “homepage” in Settings-Reading. It’s when you try to comment on a page that is set as the homepage that this problem occurs, because the page is being displayed without its “proper” URL. Therefore, the comment gets saved to the database but the redirect goes awry.

    I’m off to google the new problem becaus I think I saw this come up on my previous searches. Hope that helps someone.

    Hey guitarcrazy087,
    could you post the solution. I’m having the same issue.
    Thanks.

    Ditto. Please tell us the solution guitarcrazy087! I’m having the same problem with a clean WMPU 2.7.1 install with comments on pages on subdomain blogs using the default (kubrick) theme.

    Thread Starter authcode

    (@authcode)

    Excellent, thank you.

    Thread Starter authcode

    (@authcode)

    This also occurs on my WordPress 2.5.1 blog where it throws a 500 error trying to access edit-comments.php.

    My server is running MySQL 4.1.22-standard and PHP 5.2.6 on Apache 2.2.9 (Unix). If anyone cares.

    I’m not sure if this is a WordPress problem but how can I post WordPress bugs? I can’t find any information about posting bugs.

    Thread Starter authcode

    (@authcode)

    Thanks for your reply jleuze but I’ve found the culprit and it’s a doozy.

    Basically if this string:

    “ORA-nnnnn: “

    (without quotes, where n is any digit and a single space trails the colon) appears in the comment_content field of a comment either MySQL, PHP or WordPress chokes, resulting in a 404 error for the page attempting to load one or more comments containg this string. In my case edit-comment.php.

    You can test this by entering a comment on your own blog like this:

    ORA-11111: test

    and then trying to edit the comment. (You have to enter something after the “: ” else the space will be trimmed and the problem won’t be triggered). The comment will show on the post page but will choke the edit-comment.php page.

    Unfortunately my blog is about Oracle databases and “ORA-nnnnn:” is an Oracle error code. I’m sure most people will never come across this problem but it’s quite significant for me.

    Anyone care to suggest what’s happening here?

    I’ve manully edited the offending comments to be “ORA–nnnnn: ” but interestingly, even though this fixes the problem, in certain uses, such as when the comment gets output at the bottom of the post page, the double hyphen is reduced to a single hyphen. What’s all that about?

    Hope this helps someone else and possibly even gets fixed!

Viewing 5 replies - 1 through 5 (of 5 total)