Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DOC Update docs to reflect changes in CLI interaction #127

Merged
merged 1 commit into from
Sep 26, 2024
Merged

DOC Update docs to reflect changes in CLI interaction #127

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ implements the `\SilverStripe\SpamProtection\SpamProtector` interface. More on t
## Configuring

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
spam protection hooks with that protector.

Expand Down Expand Up @@ -124,7 +124,7 @@ class CustomSpamProtector implements SpamProtector
## Using Spam Protection with User Forms

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
`Spam Protection Field`. The type of spam protection used will be based on your
currently selected SpamProtector instance.
Expand Down
Loading