tonyair/silverstripe-spamprotection
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-spamprotection.git synced 2024-10-22 14:05:59 +02:00
Code Issues Projects Releases Wiki Activity

DOC Update docs to reflect changes in CLI interaction (#127)

Browse Source
This commit is contained in:
Guy Sartorelli 2024-09-26 17:31:25 +12:00 committed by GitHub
parent eccaad42b3
commit 16a447ee03
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -36,7 +36,7 @@ implements the `\SilverStripe\SpamProtection\SpamProtector` interface. More on t
## Configuring ## Configuring
After installing this module and a protector of your choice (i.e mollom) you'll After installing this module and a protector of your choice (i.e mollom) you'll
need to rebuild your database through `dev/build` and set the default protector need to rebuild your database by running `sake db:build --flush` and set the default protector
via SilverStripe's config system. This will update any Form instances that have via SilverStripe's config system. This will update any Form instances that have
spam protection hooks with that protector. spam protection hooks with that protector.
@ -124,7 +124,7 @@ class CustomSpamProtector implements SpamProtector
## Using Spam Protection with User Forms ## Using Spam Protection with User Forms
This module provides an `EditableSpamProtectionField` wrapper which you can add This module provides an `EditableSpamProtectionField` wrapper which you can add
to your UserForm instances. After installing this module and running `/dev/build` to your UserForm instances. After installing this module and running `sake db:build --flush`
to rebuild the database, your Form Builder interface will have an option for to rebuild the database, your Form Builder interface will have an option for
`Spam Protection Field`. The type of spam protection used will be based on your `Spam Protection Field`. The type of spam protection used will be based on your
currently selected SpamProtector instance. currently selected SpamProtector instance.