Forum Replies Created

Viewing 15 replies - 166 through 180 (of 231 total)
  • Forum: Plugins
    In reply to: Moosecandy Help Needed

    You’ve done all you need to do to get it running. You didn’t post your blog address so nobody can actually go and look. Though my first suggestion would be to make sure you didn’t corrupt the file when you transferred it from your Windows box to your Unix box. 🙂

    Thread Starter error

    (@error)

    Update again: I’ve updated the plugin to version 0.3, including moderation for suspicious comments and a better internal format which SA likes a lot better.

    I can’t imagine using LJ, and I’d love suggestions for weaning a few of my friends off it. They are by no means capable of hosting their own sites, though. 🙁

    Thread Starter error

    (@error)

    I just pulled 2005-01-07 and it is indeed fixed. Thanks! (Aside: we need some way to cross-reference or eliminate these duplicate posts.)

    Thread Starter error

    (@error)

    Looks like possibly a paste gone bad in that region of xmlrpc.php. I’ve done a patch, now I just need somebody to ping me…

    Click Options » Permalinks. If the .htaccess section appears, then it is not writable. Go pull a directory listing on the .htaccess file. If it really is set to 666, it will look something like:

    -rw-rw-rw- 1 xavierroy users 5319 Jan 5 04:55 .htaccess

    If all three rws do not appear, it’s not world writable. On my host, it appears as:

    -rw-rw---- 1 error apache 9678 Jan 5 19:43 .htaccess

    In this case it is not world writable, but it is writable by the web server apache. Which means other users on the same web host can’t screw with it.

    Exactly. The spammers have already gotten around that. That’s how I got hit with so many comment spams last weekend.

    Right now I’m using a combination of the SpamAssassin plugin and realtime blackhole lists, along with some fairly strict user agent filtering. And a custom 403 page in case a legitimate user happens to accidentally get blocked.

    The blackhole lists let people view the site, but not post comments (WP closes comments/pings entirely if they’re on the blackhole list, and I’ll have this hack out shortly. Of course I said that yesterday, but now that I’m snowed in, it might actually happen.)

    Forum: Plugins
    In reply to: Moose Candy Troubles

    Since you haven’t really stated WHAT the problem is, I don’t think too many people (not even NuclearMoose!) will be able to help. Aside from that, you probably have extra spaces or blank lines after the ?> at the end of the file. Take those out.

    Or just put it directly into index.php. The catch is it will appear above the first post (and on every page). Mine looks like:

    <div class="googlesyndication"><p><script type="text/javascript"><!--
    google_ad_client = "pub-000000000000000";
    google_alternate_ad_url = "http://www.ioerror.us/wp-content/google_adsense_script.html";
    google_ad_width = 468;
    google_ad_height = 60;
    google_ad_format = "468x60_as";
    google_ad_channel ="";
    google_page_url = document.location;
    google_color_border = "FFFFFF";
    google_color_bg = "FFFFFF";
    google_color_link = "000099";
    google_color_url = "006600";
    google_color_text = "000000";
    //--></script>
    <script type="text/javascript"
    src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
    </script></p></div>

    <?php if (have_posts()) : while (have_posts()) : the_post(); ?> (this last line is the start of the loop)

    If you really want it to be between the first and second posts, it’ll have to be Moose Candy.

    Very true! Not everyone wants to approach the spam problem in the same way, mainly because some approaches can cause inconvenience to their users, or false positive results, or lots of work for the blogger. Having more choices is better so that each person can choose for themselves how to approach the problem.

    I’m in the middle of writing something to address trackback spam. What I have already would have killed one of the two that were posted in this thread, and it’s already killed one attempt at my site, so I’ll see what I can do about polishing it up and releasing it.

    Forum: Plugins
    In reply to: Moose Candy Troubles

    Try Moose Candy 1.2.0 at http://jason.goldsmith.us/wp-plugins/moosecandy.phps it actually works. 🙂

    Oh, and you should definitely not have a call to moosecandy() in the loop. Very strange things will happen which won’t be what you want.

    I don’t have a left join in there at all. You’ve either got a newer version or an older version of what I have…this is what I have now:

    function get_recent_comments($no_comments = 5, $comment_lenth = 5, $before = '<li>', $after = '</li>', $show_pass_post = false) {
    global $wpdb, $tablecomments, $tableposts;
    $request = "SELECT ID, comment_ID, comment_content, comment_author FROM
    $tableposts, $tablecomments WHERE $tableposts.ID=$tablecomments.comment_post_ID
    AND post_status = 'publish' ";
    if(!$show_pass_post) { $request .= "AND post_password ='' "; }
    $request .= "AND comment_approved = '1' ORDER BY $tablecomments.comment_date DESC LIMIT $no_comments";
    $comments = $wpdb->get_results($request);
    $output = '';
    foreach ($comments as $comment) {
    $comment_author = stripslashes($comment->comment_author);
    $comment_content = strip_tags($comment->comment_content);
    $comment_content = stripslashes($comment_content);
    $words=split(" ",$comment_content);
    $comment_excerpt = join(" ",array_slice($words,0,$comment_lenth));
    $permalink = get_permalink($comment->ID)."#comment-".$comment->comment_ID;
    $output .= $before . '<strong>' . $comment_author . ':</strong> <br /><a href="' . $permalink;
    $output .= '" title="View the entire comment by ' . $comment_author.'">' . $comment_excerpt . '...</a>' . $after;
    }
    echo $output;
    }

    When I first started using WordPress 1.2, I ran into this same problem – at new installation! I think I reinstalled it about five or six times, including completely dropping all the tables and starting with a fresh empty database. Never could log in. I finally went to the latest nightly and they’ve been working very well, aside from the occasional upgrade strangeness (what happened to my theme?). But I knew what I was getting in to when I started using nightlies, and it’s definitely not for everyone. You should have a strong grasp of PHP and being self-hosted makes things easier. 🙂 I know it doesn’t exactly solve the problem, but it’s an option.

    The ones that have been bothering me are actually scraping the forms off my site and reading them, then a couple of hours later, will POST to the same comment ID they just scraped.

    I know. I tried them all. The problem is they block comments AFTER the spammer has sent their comment and wasted your CPU and bandwidth. My hack closes comments entirely to that IP address (i.e. “Sorry, comments are closed for this item.”) so they can’t even try to post.

Viewing 15 replies - 166 through 180 (of 231 total)