Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Does it really make sense to use separate mailhide keys for each input filter?
Particularly now that mailhide has its own module, it makes more sense to me to use a settings page. That way, if you want to use it on, say, the default and the full html filters, you don't have to reenter keys for each filter.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | recaptcha_mailhide.module.patch | 2.79 KB | robloach |
Comments
Comment #1
robloachYou're right! I'll work on it sometime in the next 24 hours.
Comment #2
robloachWhat if it still used the Input Filter's configuration, but get and set globally available public and private keys? So, instead of keys unique to that filter, they are site dependent. This would save us having to put another menu item on there as well as allow us to put filter unique stuff in later on if we want to. The attached patch will hopefully do it (I didn't do intensive testing).
Thoughts?
Comment #3
robloachComment #4
kthagen commentedIt works for me
Comment #5
kthagen commentedBTW, this change does require those who are upgrading to reenter the keys, so a warning in README.txt is probably appropriate.
Comment #6
robloachYay, thanks kthagen.
Comment #7
(not verified) commented