Problem/Motivation
The settings screen contains a checkbox labeled "Enable testing mode". This lets Akismet know you are testing by setting the is_test input (see https://akismet.com/development/api/#detailed-docs, heading "Testing your API calls"). However, this is now what the description says; "Submitting "ham", "unsure", or "spam" triggers the corresponding behaviour; image CAPTCHAs only respond to "correct" and audio CAPTCHAs only respond to "demo". Do not enable this option if this site is publicly accessible." This is a direct copy of the text from the Mollom module. The text is misleading in case of Akismet.
Proposed resolution
Change the description to "Let Akismet know you are testing and do not train the algorithm based on your inputs. Refer to the Akismet documentation for triggering guaranteed spam responses (regardless of using test mode)."
Remaining tasks
- Make change
- Augment tests, make sure there is a test that checks for the is_test input for the API
- Submit MR
- Review
- Commit
User interface changes
Changes to microcopy with the testing mode option.
API changes
None.
Data model changes
None.
Issue fork akismet-3075149
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
eelkeblokWhile working on #3198393: Automated tests are currently failing I realised the test mode checkbox does do something; it enables the is_test input passed to the Akismet API (see https://akismet.com/development/api/#detailed-docs, heading "Testing your API calls"). This is probably a good approach, combined with the documented inputs to force spam responses. The description of the checkbon in the settings is misleading, though, and does not properly explain what it does. It should explain that it lets Akismet know you are testing, and should explain what it does "Let Akismet know you are testing and do not train the algorithm based on your inputs. Refer to the Akismet documentation for triggering guaranteed spam responses (regardless of using test mode)."
Comment #3
eelkeblokUpdated IS.
Comment #5
eelkeblokComment #6
eelkeblokI'm pushing the test adjustment to #3225042: Rework testing mode test, since it will involve some refactoring of the client code.
Comment #8
eelkeblok