EditableSpamProtectionField doesn't work by default

[chillu]

It requires a spam protector to be available and set up correctly. If any spam protector module is installed, the field will show - but doesn't check for a valid API key. In the case of recaptcha or akisment spam protectors, that means it won't apply any spam protection.

This affects the default CWP functionality with the recently added blog module, since it bundles the silverstripe/akismet module but doesn't configure an API key. cc @tractorcow @assertchris

[tractorcow]

The problem is that there is no "core standard" fallback for when a spam protector isn't enabled. We probably should have some kind of agreed on fallback behaviour for the core module.

[maxime-rainville]

Need to validate if this still affect SS4.

[GuySartorelli]

This does still affect SS4. I wouldn't say it's a bug though so much as a UX concern - we should just more clearly communicate that the field doesn't do anything without an additional module installed to provide the actual spam protection functionality.