API Re-introduced ability to insert spam field before another existing field #13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks @tractorcow. My sort of api, tested and documented :) |
wilr
added a commit
that referenced
this pull request
Mar 7, 2014
API Re-introduced ability to insert spam field before another existing field
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was updating an old site to use the new spam protector module, when I realised that the ability to specify the "insert before" field when adding the captcha field has been removed.
I've reintroduced this option with tests and documentation. :) To be careful, I've added a check to ensure the field you specify exists. The module will fallback to adding to the end if it doesn't.