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.

CommentFileSizeAuthor
site_policy.diff2.47 KBBenjamin Schrauwen

Comments

sun’s picture

Hm. Not sure about this.

Could be used to e.g. point out that all links will be blocked on a given site.

Who or what is or would actually be blocking all links?

Benjamin Schrauwen’s picture

Several blogs use this technique to make it clear what is allowed and what not. Here is an example from http://www.fourhourworkweek.com/

Comment Rules: Remember what Fonzie was like? Cool. That's how we're gonna be -- cool. Critical is fine, but if you're rude, we'll delete your stuff. Please use your PERSONAL name or initials and not your business name and do not put your website in the comment text, as both come off like spam. Have fun and thanks for adding to the conversation! (Thanks to Brian Oberkirch for the inspiration)

This patch is meant to be used on sampler.drupalgardens.com

sun’s picture

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.

Benjamin Schrauwen’s picture

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.

sun’s picture

Version: 7.x-1.x-dev » 7.x-2.x-dev
Status: Active » Closed (won't fix)

I do not believe that this feature pertains to the functionality of Mollom module.

Feel free to re-open this issue and discuss/clarify if you disagree.