Title: Remove asb callback from specific forms
Last modified: July 10, 2021

---

# Remove asb callback from specific forms

 *  Resolved [AF](https://wordpress.org/support/users/armin-fuhrmann/)
 * (@armin-fuhrmann)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/remove-asb-callback-from-specific-forms/)
 * Hi there,
    how can I remove “new-password” textarea replacements for specific
   comment forms? Thx.

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

 *  Plugin Contributor [Torsten Landsiedel](https://wordpress.org/support/users/zodiac1978/)
 * (@zodiac1978)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/remove-asb-callback-from-specific-forms/#post-14647800)
 * Hi [@armin-fuhrmann](https://wordpress.org/support/users/armin-fuhrmann/)
 * there is no way to do that. It is part of our honeypot and you can’t disable 
   it. The only way would be to change the antispam plugin.
 * The reason behind using this attribute is described here (and in following links
   in the issue):
    [https://github.com/pluginkollektiv/antispam-bee/issues/280](https://github.com/pluginkollektiv/antispam-bee/issues/280)
 * I think there is a reason why you are asking this. Can you please explain why
   do you want to do that?
 * Maybe we can solve your issue in another way?
 * All the best
    Torsten
 *  Thread Starter [AF](https://wordpress.org/support/users/armin-fuhrmann/)
 * (@armin-fuhrmann)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/remove-asb-callback-from-specific-forms/#post-14653706)
 * Hi [@zodiac1978](https://wordpress.org/support/users/zodiac1978/),
    some of my
   custoomers use comment fields in logged-in area where spam protection is not 
   strictly necessary. I solved this by adding “is_user_logged_in()” as a condition
   in prepare_comment_field(). Maybe you can add this as an option in your next 
   version 🙂
 *  Plugin Contributor [Torsten Landsiedel](https://wordpress.org/support/users/zodiac1978/)
 * (@zodiac1978)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/remove-asb-callback-from-specific-forms/#post-14654802)
 * Hi [@armin-fuhrmann](https://wordpress.org/support/users/armin-fuhrmann/)
 * you could enable to trust approved commenters:
    [https://antispambee.pluginkollektiv.org/documentation/#trust-approved-commenters](https://antispambee.pluginkollektiv.org/documentation/#trust-approved-commenters)
 * But the first comment of each commenter could be marked as spam in this case.
 * Editing plugin files should be avoided, so I think we could try another way to
   solve this.
 * You can use the `pre_comment_approved` filter to approve every comment from logged
   in users:
    [https://wordpress.stackexchange.com/questions/8512/hold-comments-for-moderation-only-if-user-is-not-logged-in](https://wordpress.stackexchange.com/questions/8512/hold-comments-for-moderation-only-if-user-is-not-logged-in)
 * Then you have the same output (no spam marking for logged in users), but without
   editing plugin files or disabling the honeypot.
 * Hope this helps!
 * All the best,
    Torsten
 *  Thread Starter [AF](https://wordpress.org/support/users/armin-fuhrmann/)
 * (@armin-fuhrmann)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/remove-asb-callback-from-specific-forms/#post-14655364)
 * Hi [@zodiac1978](https://wordpress.org/support/users/zodiac1978/),
    thank you
   for your suggestions, both will unfortunately not work, I had them in mind too.
   But I still need the holding comment for moderation for other purposes and manually
   unlock hundreds of customer accounts, where the first comment always ends up 
   in spam is also no solution. Brgds, AF
 *  Plugin Contributor [Torsten Landsiedel](https://wordpress.org/support/users/zodiac1978/)
 * (@zodiac1978)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/remove-asb-callback-from-specific-forms/#post-14655521)
 * Hi [@armin-fuhrmann](https://wordpress.org/support/users/armin-fuhrmann/)
 * > But I still need the holding comment for moderation for other purposes
 * I can’t follow you here. Which purpose is that? Are you moderating “bad words”
   via blocklist?
 * > manually unlock hundreds of customer accounts, where the first comment always
   > ends up in spam is also no solution.
 * ASB should not mark every first comment from each user as spam. Why do you think
   this would happen?
 * If you have a Github account then please open an issue for this request. Otherwise
   I can do that for you. This would open the discussion a bit more to our team.
   
   [https://github.com/pluginkollektiv/antispam-bee/issues/new](https://github.com/pluginkollektiv/antispam-bee/issues/new)
 * All the best
    Torsten
 *  Plugin Contributor [Torsten Landsiedel](https://wordpress.org/support/users/zodiac1978/)
 * (@zodiac1978)
 * [4 years, 10 months ago](https://wordpress.org/support/topic/remove-asb-callback-from-specific-forms/#post-14737599)
 * Hi [@armin-fuhrmann](https://wordpress.org/support/users/armin-fuhrmann/)
 * I close this because there was no reply since 3 weeks. If you need more help,
   please reply again or move to Github and open up an issue/PR there.
 * Thanks in advance!
 * All the best
    Torsten

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

The topic ‘Remove asb callback from specific forms’ is closed to new replies.

 * ![](https://ps.w.org/antispam-bee/assets/icon-256x256.png?rev=2898402)
 * [Antispam Bee](https://wordpress.org/plugins/antispam-bee/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/antispam-bee/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/antispam-bee/)
 * [Active Topics](https://wordpress.org/support/plugin/antispam-bee/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/antispam-bee/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/antispam-bee/reviews/)

 * 6 replies
 * 2 participants
 * Last reply from: [Torsten Landsiedel](https://wordpress.org/support/users/zodiac1978/)
 * Last activity: [4 years, 10 months ago](https://wordpress.org/support/topic/remove-asb-callback-from-specific-forms/#post-14737599)
 * Status: resolved