Posted by Benjamin Schrauwen on November 29, 2011 at 9:17am
2 followers
Jump to:
| Project: | Mollom |
| Version: | 7.x-1.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Basic implementation of an admin setting that allows to define an optional site policy to be displayed above each protected form. Could be used to e.g. point out that all links will be blocked on a given site.
| Attachment | Size | Status | Test result | Operations |
|---|---|---|---|---|
| site_policy.diff | 2.47 KB | Ignored: Check issue status. | None | None |
Comments
#1
Hm. Not sure about this.
Who or what is or would actually be blocking all links?
#2
Several blogs use this technique to make it clear what is allowed and what not. Here is an example from http://www.fourhourworkweek.com/
This patch is meant to be used on sampler.drupalgardens.com
#3
I'd have to research whether there isn't a module for that already. However, showing a site policy doesn't seem to be the primary goal here...?
The question remains - who or what actually performs the blocking? Is the idea to add a new API parameter, so the client can signify to the backend that it wants to block posts containing URLs (or rather, that no URLs are expected to be contained in a certain protected form)?
Or is this supposed to happen on the client-side only? In that case, I'm also almost certain that there's a module for that. Sure, we can try to incorporate and re-implement that in the Mollom module...
Just trying to understand the larger plan you're after here.
#4
Site specific policy can be enforced using the site specific blacklist. E.g. basic blocking of all links can be done by adding "http://" to the blacklist.