FV Antispam Changelog

1.9

  • Spam pings and trackbacks go to trash if they are detected by Akismet
  • Bugfix in "Filled In" plugin checking SQL

1.8.4

  • Added protection for WP registration form
  • Added removing of trash comments older than 1 month
  • Added option to hide trackbacks in Comments in admin section

1.8.3.1

  • Admin interface display issues fix
  • The Events Calendar bugfix (comment forms were not working on events)
  • Bugfix in Filled in collision detection

1.8.3

  • New function - protect Filled In forms against spam
  • New function - display comments by default when you enter Comments section in wp-admin Dashboard
  • New function - show counts of comments and pingbacks separately in Comments section in wp-admin Dashboard

1.8.2

  • New function - redirect pingbacks and trackbacks notifications to different email address
  • Or disable pingbacks and trackbacks notifications at all.

1.8.1

  • Bugfix for some templates.

1.8

  • First public release

 

24 comments on “FV Antispam Changelog”

  1. 01

    Your fv-antispam plugin is amazing. But, there’s a conflict with the Ajax Comment Preview plugin I use (http://blogwaffe.com/ajax-comment-preview/). Deactivating fv-antispam allows the comment preview to work properly. Activating fv-antispam renders Ajax comment preview non-functional.

    Will at January 24th, 2011 around 3:24 pm
    Jump to the top of this page

  2. 02

    Hello Will,

    I checked the Ajax Comment Preview plugin and there’s nothing we can do about it, as the comment input textarea code is hardcoded in the plugin.

    However, there are some other comment preview plugins that work with FV Antispam:

    Live Comment Preview works, but you have to change the textarea ID in the live-comment-preview.php file on line 124. You can find out that the ID is by looking into the source code of the page with comment form on it. It will be an unique string of seemingly random numbers and letters like “a7391152e”, so use that.

    jQuery Comment Preview is not so lightweight as the Live Comment Preview, but you can set the ID in options, so you don’t have to edit files.

    Thanks,
    Martin

    Martin at January 26th, 2011 around 2:31 am
    Jump to the top of this page

  3. 03

    Hi Will,

    If the Ajax Comment Preview author Michael Adams (aka mdawaffe aka MDA) would like to work with us on making the two plugins compatible we would be happy to collaborate to make FV Antispam work with Ajax Comment Preview.

    alec at January 27th, 2011 around 11:28 am
    Jump to the top of this page

  4. 04

    Hi there!

    I’m looking at FV Antispam for replacing WP-SpamFree on a project I’m working on. This is a multisite install with 42 site on the network currently and that will grow with time. I was wondering if FV Antispam has been tested and works well in a multisite install. Thank!

    Stéphane Bergeron at February 3rd, 2011 around 10:04 am
    Jump to the top of this page

  5. 05

    Hi Stéphane,

    There’s no reason that FV Antispam won’t work for you. FV Antispam is a much better solution for your server than WP Spam Free (which we used but actually got a couple of clients booted off shared hosting for server load).

    You’ll want an active Akismet key for FV Antispam to be most effective. FV Antispam takes care of all the machine spam but to handle human spam we rely on Akismet (horses for courses).

    Let us know how you get on.

    Paid hands on support is available for all our plugins if you find you’d like a hand with your install or tweaking performance.

    alec at February 3rd, 2011 around 2:52 pm
    Jump to the top of this page

  6. 06

    Thanks Alec!

    So I just perform a network activation and let it do its magic?

    I installed it on another site earlier and it does seem to work great and I thought I noticed a speed increase compared to same site with WP-SpamFree. With W3 Total Cache enabled on top of everything, page load is almost instantaneous.

    Thanks for the great plugin!

    Stéphane Bergeron at February 3rd, 2011 around 3:03 pm
    Jump to the top of this page

  7. 07

    Hi,

    I have installed your FV Antispam plug-in on my WordPress blog. The comment form shows up on pages but not on my home page. Can you help me out with this?

    Thanks

    Vicky

    Vicky at February 7th, 2011 around 9:35 am
    Jump to the top of this page

  8. 08

    Hello Vicky,

    do the comment forms appear before you activate our plugin? Is your home page showing a single page (wp-admin -> Settings -> Reading -> Front page displays -> A static page) or is it listing blog posts with comment forms?

    Thanks,
    Martin

    Martin at February 8th, 2011 around 9:37 am
    Jump to the top of this page

  9. 09

    This seems like a very useful plug-in – I do not see any information on testing it though. Is it even possible to test this? Do I just install it and expect it to work?

    Jeff Smith at February 22nd, 2011 around 3:10 pm
    Jump to the top of this page

  10. 10

    Hi Jeff,

    FV Anti Spam is a great plugin. We won’t run a website without it. Zero server load and complete protection.

    And like all FV plugins, FV Antispam is set to intelligent defaults out of the box. No need to configure anything. It just works.

    alec at February 22nd, 2011 around 3:17 pm
    Jump to the top of this page

  11. 11

    Hello Jeff,

    check out the updated FV Antispam Installation page for some suggestions on how to test this plugin.

    Thanks,
    Martin

    Martin at February 24th, 2011 around 7:22 am
    Jump to the top of this page

  12. 12

    I’m really impressed how Fv-Antispam works. Unlike wp-spam free, which can take a very long time to load simple page. I have tested it myself.

    debrian at March 12th, 2011 around 10:48 am
    Jump to the top of this page

  13. 13

    Hi looking at putting FV Antispam on some client sites. But with Automattic changing the license for Akismet I have been using TypePad AntiSpam on most and testing AntiSpam Bee on others. Will your plugin work with these or does it have to be Akismet?

    Paul at June 8th, 2011 around 4:51 pm
    Jump to the top of this page

  14. 14

    We should be compatible with Typepad Antispam. Antispam Bee and FV Antispam are mainly duplicate functionality.

    We prefer FV Antispam of course but there’s lots to like about Antispam Bee.

    I’d love to hear about your success with Typepad Antispam together with FV Antispam. Please let us know how it goes.

    I agree that the license fees for Akismet are pretty stiff for those who decide to pay. We paid $800 this year and that’s too much for a single year.

    alec at June 8th, 2011 around 4:59 pm
    Jump to the top of this page

  15. 15

    The plugin sounds really good although for some reason is not replacing the textarea. So, the form now has two. Any ideas what may be causing this? I’m using the latest WP.

    Thanks

    Poli at July 10th, 2011 around 11:54 am
    Jump to the top of this page

  16. 16

    Hello Poli,

    my guess be that your template is using some different HTML for the comment form (it should do it with a WordPress function) and that’s why the special CSS is not working and two textareas appear instead of one.

    If you are using any publicly available WordPress template, we can check it out and see what could be wrong.

    Also, try clearing any WP cache you are using and browser cache.

    Thanks,
    Martin

    Martin at July 11th, 2011 around 12:54 am
    Jump to the top of this page

  17. 17

    Thank you, Martin, for you reply. I appreciate it. I was guessing that it was to do with something like that but couldn’t find any offensive HTML. If you have the time a similar form is being used here:

    http://www.infozeen.co.uk/cloud-computing/

    Thanks

    Poli

    Poli at July 11th, 2011 around 2:40 am
    Jump to the top of this page

  18. 18

    It could also be due to CSS. Maybe one of the lines in your template CSS is forcing display for the textareas.

    I added your question into FAQ section.

    Thanks,
    Martin

    Martin at July 11th, 2011 around 6:39 am
    Jump to the top of this page

  19. 19

    Got it! The textarea has to have id=comment not just name=comment. Sorry, for wasting your time.

    Thanks

    Poli

    Poli at July 11th, 2011 around 7:44 am
    Jump to the top of this page

  20. 20

    Thank you for that, it’s a nice addition into our FAQ!

    Martin

    Martin at July 11th, 2011 around 7:50 am
    Jump to the top of this page

  21. 21

    Glad to have contributed: it’s a great plugin!

    Thank you for it

    Poli

    Poli at July 11th, 2011 around 7:56 am
    Jump to the top of this page

  22. 22

    Hi,

    I installed it on a fairly busy blog recently – I just noticed that all comments from *actual* humans are flagged as spam & moved to trash…

    Have you heard of this issue before? Is there something obvious I might be doing wrong or do you think it might be a plug-in conflict?

    Cheers

    Paul at July 13th, 2011 around 1:53 am
    Jump to the top of this page

  23. 23

    Hello Paul,

    there might be a conflict with your template CSS or HTML. It works well on all the sites we build, we work with a lot of different templates.

    Try following the “Testing” guidelines in our FV Antispam Installation and Testing guide.

    Thanks,
    Martin

    Martin at July 13th, 2011 around 3:52 am
    Jump to the top of this page

  24. 24

    Hello everybody,

    submission of comments has been closed here, please post your questions into our SUPPORT FORUM.

    Thanks,
    Matej

    matej at September 13th, 2011 around 10:03 am
    Jump to the top of this page