Forum Replies Created

Viewing 10 replies - 1 through 10 (of 10 total)
  • Amelie

    (@amelie)

    Have you tried upgrading to the latest version of WP? I’m not sure if it would help, but your post states that you are using 2.0.3 which is relatively old (the current stable version is 2.2).

    Amelie

    (@amelie)

    Do you have Akismet enabled? I’ve had problems all day with my comments timing out with Akismet (not just with WordPress) – I believe the service is down right now, so comments are just getting lost. I also think that if someone is logged in, their comments are not submitted to Akismet, hence why you are able to leave comments when logged in.

    When Akismet is back up and running, try seeing if you/your friends are able to leave comments without being logged in.

    Thread Starter Amelie

    (@amelie)

    Never mind, managed to fix it (not sure how, but there you go)

    Thread Starter Amelie

    (@amelie)

    I’ve tried commenting out the lines affected, and also creating a new instance of $wpdb, only the former just caused more problems and the latter just moved the error down to where the next call to $wpdb was. I ended up having to add new $wpdb objects to each and every function for some reason (it wasn’t taking any notice of the global statement), but then it would not work for GET (i.e. normal) requests. Argh!

    Anyone have any ideas at all?

    I have replied to your topic about this at CodeGrrl. 🙂

    Thread Starter Amelie

    (@amelie)

    @podz: Akismet 1.14, Bad Behaviour 1.2.4, WordPress Database Backup 1.7, Autoclose Comments 0.1, Comment Plugger 1.1, Exec-PHP 2.0, Gravatar 1.1, Quote Comment 2.0.2, Subscribe to Comments 2.0, Search and Replace 1.1 and runPHP 2.1b.

    I’m having the same problem. Using 1.5.1 with 3 themes installed. Haven’t touched any core files. Tried the permissions etc but they were already set correctly.
    Not a massive problem since I never really use the theme editor but a problem nonetheless. 🙂

    Ok, from looking at your source code, this is what seems to be the problem: You have a <div> tag open (class=post), you then have an h3, an a, and an image. This is all fine, however you need to close all those tags before you go on to use your div class=meta tag, that is what is causing it to display those errors.

    This could be because of 1 of 2 things, either you’ve got a </a> in there when you didn’t open a link, or you haven’t nested your tags properly (nesting = closing tags in the order you opened them, ex. <a><i><b>text</b></i></a>)

    EDIT: no wait, I see what you’ve done – you’ve already closed your h3’s etc so basically you’re closing them twice if you see what I mean. You need to take out the duplicates 🙂

    You need to make sure your images all have an ‘alt’ element, and that they ‘self-close’. Example: <img src="someimage.jpg" alt="Add something here" /> See the slash before the close of the tag? That’s called self-closing, you need to go through your entries and make sure any images you’ve used are coded in this way. I hope that helps you out.

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