WordPress.org

Ready to get started?Download WordPress

Forums

[Plugin: WP-SpamFree] Cannot send or recieve ping and trackback after upgrade to 1.9.6.6 (27 posts)

  1. Nadiamode
    Member
    Posted 6 years ago #

    Before I use WordPress 2.6.0 and WP-SpamFree 1.9.6.5 everthing OK I can use ping and trackback but after I upgrade WP-SpamFree to version 1.9.6.6 (and WordPress 2.6.1) I cannot send ping or recieve trackback anymore

    - In Spam Option everything same, no change

    No conflict plugins here , I also try Troubleshooting Guide but still have problem so when I deactivated all plugins I can use Trackback and Ping

    I try deactivated plugin one by one to see which plugin has conflict untill I deactivated all plugin except WP-SpamFree and still cannot use trackback but when I deactivated only WP-SpamFree trackback and ping working now.

    I think the only problem happen when I activate WP-SpamFree, Something mistake? before I use WordPress 2.6.0 and WP-SpamFree 1.9.6.5 everthing work fine but I just upgrade to WP-SpamFree 1.9.6.6 yesturday

    This plugin very nice I love it, It help me to reduce spam and block all spam so no spam can cpme in my database and use my resources same Akismet or others spam plugins

    Thank you

  2. WebGeek
    Member
    Posted 6 years ago #

    Hi Nadia,

    Most likely this has nothing to do with WP-SpamFree as it doesn't have any code that affects outgoing pingback functionality. It's most likely just a WordPress glitch and your pingbacks will probably start working again before too long without you doing anything. I've seen this on many WP blogs even before I built WP-SpamFree and on blogs that never had it installed.

    Glad you like the plugin. Hope that answers your question.

  3. Nadiamode
    Member
    Posted 6 years ago #

    OK Thanks

    I'll see.

  4. Nadiamode
    Member
    Posted 6 years ago #

    I have another blog use WP-SpamFree 1.9.6.5 (old version) with WordPress 2.6.1 also cannot send ping or recieve trackback

    Maybe because WordPress 2.6.1 that make problem before I use WP 2.6, it no problem

  5. WebGeek
    Member
    Posted 6 years ago #

    I've seen it happen on just about every version of WordPress I've used from 2.1 on so I really believe it is just a random WordPress glitch.

  6. jonamerica
    Member
    Posted 5 years ago #

    I'm having the same problem on my site. I've never had any issue with pingbacks until after I started using wp-spamfree. If I deactivate wp-spamfree pingbacks work just fine.

    I'm using wp-spamfree version 1.9.6.6 and WordPress version 2.6.2

  7. WebGeek
    Member
    Posted 5 years ago #

    There's no code in WP-SpamFree that would affect outgoing pingbacks.

    It may be unfortunate timing, but based on a lot of testing, I'm confident it's not related to the WP-SpamFree.

  8. Nadiamode
    Member
    Posted 5 years ago #

    Just to let everybody know

    Today WordPress has new version ... 2.6.2, I upgrade to latest but problem still here
    I cannot send pingback or recieve trackback after worpdress version 2.6.0

    And I believe you that wp-spanfree plugin doesn't have any code that affects outgoing pingback functionality

    I just wonder why when I disable this plugin I can use trackback but when I enable it I can't use..

    Very Confused

  9. jonamerica
    Member
    Posted 5 years ago #

    My guess is that wordpress is working properly, as is WP-SpamFree. Isn't the point of SpamFree to stop spam in comments by using "a dynamic combo of JavaScript and cookies to weed out the humans from spambots." When you ping your own site you're basically creating a comment, right? Can WordPress use either JavaScript or cookies?

    My guess is that WordPress is sending out the pingback to our own sites, but WP-SpamFree is blocking it as spam. WP-SF says how many spams it has blocked, is there a log somewhere that gives specifics? This would give us a definitive answer.

  10. Nadiamode
    Member
    Posted 5 years ago #

    maybe you're right

    I have two website on same server (same ip)
    1. I can't send ping or recieve trackback in my own blog (same blog)
    2. I can't send ping or recieve trackback to another my blog (same server)

    but sometime I test ping from another website that let people go to test trackback, I also cannot recieve, and I test ping to other people's blog also can't do that

    the only thing that can tell this story is log file but I only see NUMBER OF SPAM in wordpress admin, no link to log file and I 'm not sure there's log file or not? or only have number counting (because in folder wp-content/plugins/wp-spamfree no log file and in database also no log file create from this plugin )

  11. WebGeek
    Member
    Posted 5 years ago #

    hey jon and nadia.

    Just a couple quick notes:

    1) There isn't a log feature yet in the production (distributed) version but we are working on one for version 2.0. There was detailed info up on the plugin page but we had some issues with the site and are working on restoring it. That will be back up soon.

    2) WP-SpamFree isn't filtering pings from same sites. If they aren't happening, it means they aren't being sent, which means an issue with WordPress itself. While the production version of the plugin doesn't currently have a long, but the development/debug versions of the plugin that we use for testing on all our test sites, does ha have a logging feature that lets us see every single comment submission. This is how we are so confident about accuracy and that WP-SpamFree isn't interfering with ping process.

    Hang tight for the log feature in v2.0. That will show what I'm talking about.

    While you may feel that the timing coincides, I'm quite confident that the source of the ping issue is not WP-SpamFree.

  12. WebGeek
    Member
    Posted 5 years ago #

    @nadiamode:

    Also, nothing regarding pings was changed between versions 1.9.6.5 and 1.9.6.6 so it may have something to do with the upgraded version of WordPress.

    However when I get some time I will investigate the new code in the 2.6 versions of WordPress more in depth to see if they changed functionality.

  13. Jason Kemp
    Member
    Posted 5 years ago #

    WPSpamfree has a setting which can disable both trackbacks and pingbacks

    very easy to find - assume it has already been checked

    Its under
    Spam Options
    # Disable trackbacks.
    (Use if trackback spam is excessive.)

    # Disable pingbacks.
    (Use if pingback spam is excessive. Disadvantage is reduction of communication between blogs.)

  14. db0
    Member
    Posted 5 years ago #

    There is definitely something going on here. I have the same problem with nadia and I noticed it when my recent blogposts did not ping to the people I was linking to. I just now did some field testing on a test site and with spamfree off pingbacks are working correctly.

    WebGeek, it might very well be that you don't have anything blocking these from going out built in but this is still happening, thus I would classify it as a bug.

    Unfortunately this is the kind of thing that is difficult for most people to realise as you can't know if you were supposed to receive a pingback unless you were expecting it. And you can't tell if your pingback was received unless you know to doublecheck.

    I also had a similar problem with another spam plugin, bcspambloc which did not allow me to receive trackbacks (getting them out worked fine) and thus I had to disable it.

    Perhaps this is a combo problem with the host as well? I am using Dreamhost, what are you using yourself nadia?

    Personally, as I need something like spamfree for the moment, I will simply have to workaround it by disabling it before posting and then re-enabling it, but I would appreciate if you could take a look. I will gladly give you admin access to my test blog if you want it in order to check yourself.

  15. WebGeek
    Member
    Posted 5 years ago #

    db0:

    As I've stated above there is no code in the plugin that can affect the functionality of outgoing pings. You will have that problem with WordPress occasionally with or without the plugin. It's a glitch I've seen for a long time, even with no plugins activated. It's erratic, and I don't know what the source of it is, but it isn't WP-SpamFree.

  16. db0
    Member
    Posted 5 years ago #

    If that was the case then why do pingbacks stop working as soon as spamfree is activated and start again when I deactivate it? If it was a random glitch one would assume that it would remain regardless of what I do with spamfree. Unless the glitch happened to appear perfectly synchronized with my spamfree testing which I find a bit impossible.

    The good thing is that I received a pingback so it seems they still come through.

  17. WebGeek
    Member
    Posted 5 years ago #

    It doesn't stop working for everyone. Also, the error you're talking about happens randomly even when no plugins are installed. There's a glitch in WordPress.

  18. Samuel Wood (Otto)
    Tech Ninja
    Posted 5 years ago #

    No, WordPress has no known "glitches" along these lines. If you're not receiving pingtracks or trackbacks, then something else is blocking them from reaching your site.

    The WP-SpamFree plugin does have an option to block pings/tracks entirely, so you might check to see if that option is not turned on by mistake.

    Alternatively, if you can't get it to work, then you could try one of many other anti-spam plugins. Personally, I find that the combination of Cookies for Comments and Akismet are an almost 100% solution on all the blogs I administer. They are also both extremely well written code which run very fast and which have a very low overhead.

  19. WebGeek
    Member
    Posted 5 years ago #

    Otto42:

    Just because it isn't acknowledged doesn't mean it isn't there. I've seen the glitch quite a few times and I know many others who have as well.

    People in this thread are talking about it blocking outgoing pings, and it has no code that would affect that. You are right, it's good to check that the option to block incoming trackbacks and pingbacks isn't checked, even though that's addressing a different issue. It's off by default though.

    As always, thanks for your helpful input.

  20. Samuel Wood (Otto)
    Tech Ninja
    Posted 5 years ago #

    Just because it isn't acknowledged doesn't mean it isn't there. I've seen the glitch quite a few times and I know many others who have as well.

    That's as may be, however you are speculating as to the cause of your problem without sufficient evidence. Nobody has ever pointed it out or reproduced this problem in any way that I am aware of. The code for pingback and trackback sending is very, very straightforward and easy to follow. If it was there, then it would be rather easy to track down and find.

    So if there is some specific case or problem you can point out, then by all means do so. However until you feel like doing that, calling it a "glitch" is unfounded, because it's not really an issue with WordPress until it has actually been shown to be an issue. Understand?

    Placing blame on anything for problems, when you have no evidence to back up those claims, is unacceptable here. Unless you know specifically what the problem is, do not speculate on it. And yes, I will have something to say about it regardless of what particular piece of software you happen to be placing the blame on.

    We do not traffic in the blame game in these forums, so do not let it happen again.

    Edit: Note that I do agree that your plugin is probably not the cause. I just take exception to your calling something a "glitch" without pointing out what exactly the problem is. It's rather bad form, IMO, and I don't appreciate that sort of thing around here.

  21. Samuel Wood (Otto)
    Tech Ninja
    Posted 5 years ago #

    I just downloaded and took a look at the latest version of WP-SpamFree (I had not examined the code in a while) and the only thing I see that might possibly cause this sort of thing is that there is a rather large amount of code happening at the init action hook. There's a lot of random key generation, loading, processing, etc.

    It's possible (although really unlikely) that this could delay the cron process enough to break the timing of pingback sending on slow or overloaded servers just enough to be a problem.

    If this was happening, then one could prevent the problem by adding this line of code to the top of the plugin:
    if (DOING_CRON) return;

    That would make the entire plugin not load when the wp-cron process was running, which would eliminate it entirely from the possible list of things that could be interfering with the do_all_pings bits.

  22. WebGeek
    Member
    Posted 5 years ago #

    Hey Otto. Thanks for looking into that. I'll take a look at your suggestions and see about integrating that.

    Please don't in take offense if speak of a potential glitch in WP - I'm not attempting to throw blame. I was just expressing thoughts, which I think we're still free to do here. :) For the record I think WordPress is the best blog platform out there, and one of my favorite pieces of software. Even the most sophisticated and developed software is bound to have minor glitches...that doesn't stop it from being great. It's just the life of programming.

  23. ljmac
    Member
    Posted 5 years ago #

    With all due respect WebGeek, you seem very quick to place the blame elsewhere when something might be wrong with WP-Spamfree. People here have stated repeatedly that switching on WP-Spamfree blocks pingbacks, and switching it off allows them to work again. What if the latest version of the plug-in is inadvertantly switching on "block pingbacks" all the time, regardless of how the user sets it? This is an obvious possibility, but you haven't even investigated it.

    Also, I opened a thread three weeks ago - and sent you a support email as well - about WP-Spamfree blocking legitimate comments at the blog I run. I came up with a couple of feature requests that could possibly solve this problem, but you haven't responded at all.

    Anyway, I've made the switch to Cookies for Comments and WP Hashcash, which combines cookies and Javascript as your plug-in does, but with far greater compatibility and (unlike WP-Spamfree) no false positives. And also unlike Spamfree, you can set them to moderate, so even if there are false positives, you can catch them anyway. With WP-Spamfree, you can never know if it's blocking legitimate comments unless your readers complain (as mine have) or you happen to catch it out (as I have a well).

  24. db0
    Member
    Posted 5 years ago #

    WebGeek, I did not say it happens for everyone, I just said that it happens for me perfectly synchronized with the plugin activation/deactivation so that makes it unlikely to be a WP glitch.

    Indeed I do not necessarily blame your plugin and it might very well be a combo with the way my host has setup his server. It might even be the cron delay that Otto42 mentioned (which I'm going to check later)

    But the fact that this happens and is easy to replicate makes it worth investigating.

    As before, this seems to affect only outgoing pingbacks for me, as I managed to receive one (although I won't know if I missed any unless I see it through google blog search backlinks).

  25. bradstinyworld
    Member
    Posted 5 years ago #

    As said before this happens to a lot of people who probably don't even know it. It is happening on everyone of my blogs that uses wp-spamfree. The ones that don't use i.e. the ones on wordpress.com and a couple of other places it doesn't happen. When I uninstall the plugin on Host Gator, Zyon, and Blue Host based blogs trackbacks and pings start going out again. This is happening not just on single installs but on Mu installs as well in version 2.5, 2.6.2, 2.6.3 and 2.6.5 and 2.6.3mu and 2.6.5mu Removing the plugin always fixes the problem. Take that for what it is worth.

    I am currently removing wp-spamfree from 48 blogs I manage for this very reason all of which have this problem. The plugin works great and will be happy to return using it when this issue is resolved.

  26. ljmac
    Member
    Posted 5 years ago #

    The other big problem with WP-Spamfree is that it occasionally blocks legitimate comments, and unfortunately the author seems unwilling to recognise the problem, let alone do anything about it. I would like the option of switching off the algorithmic layer, as I believe this is what causes the problems - I really think that moderation is the only way to deal with human spam without false positives, and the JavaScript/Cookie layers already completely block bots.

    Anyway, I started another thread on this issue, which has lots of good discussion about the pros and cons of the various alternatives to WP-Spamfree - you should be able to find an anti-spam solution that works well for you by going through the comments there:

    http://wordpress.org/support/topic/214198

  27. WebGeek
    Member
    Posted 5 years ago #

    I've continued to look into this. What we've found is that we cannot recreate the error. Many many, blogs still have no problem with sending and receiving pingbacks. If you are still having problems, I suggest you upgrade your blog to the latest version of WordPress. (From what we've seen, WP 2.7+ does not seem to have any problems with this, and we've tested this on a LOT of blogs, and many different servers.)

    If that does not take care of the issue for you, please contact me directly through the WP-SpamFree Support page, and I'll look into each case individually.

Topic Closed

This topic has been closed to new replies.

About this Topic