drupal_routes/profiles/acquia/modules/mollom/README.txt

-- SUMMARY --

Integrates with the Mollom service: https://www.mollom.com

For a full description of the module, visit the project page:
  http://drupal.org/project/mollom

To submit bug reports and feature suggestions, or to track changes:
  http://drupal.org/project/issues/mollom

For issues pertaining to the Mollom service, contact Mollom Support:
  https://www.mollom.com/contact
  - e.g., inappropriately blocked posts, spam posts getting through, etc.
  - Ensure to include the Mollom session/content IDs of affected posts; find
    them in Drupal's Recent log messages by filtering by the "mollom" category.


-- REQUIREMENTS --

None.


-- INSTALLATION --

* Install as usual:
  http://drupal.org/documentation/install/modules-themes/modules-7

* Go to https://www.mollom.com,

  - sign up or log in with your account
  - go to your Site manager ("Manage sites" link in the upper right)
  - create a site (API keys) for this Drupal installation.

* Enter your API keys on Administration » Configuration » Content authoring
  » Mollom » Settings.

* If your site runs behind a reverse proxy or load balancer:

  - Open sites/default/settings.php in a text editor.
  - Ensure that the "reverse_proxy" settings are enabled and configured
    correctly.

  Your site MUST send the actual/proper IP address for every site visitor to
  Mollom.  You can confirm that your configuration is correct by going to
  Reports » "Recent log messages".  In the details of each log entry, you should
  see a different IP address for each site visitor in the "Hostname" field.
  If you see the same IP address for different visitors, then your reverse proxy
  configuration is not correct.

* On servers running PHP <5.4, and PHP as CGI (not Apache module), inbound HTTP
  request headers are not made available to PHP.  Add the following lines to
  your .htaccess file:

    RewriteEngine On
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

-- OPTIONAL INSTALLATION --
 * Download and enable the libraries module: http://drupal.org/project/libraries
 * Download the chosen JavaScript plugin into your libraries location
   - Download from https://github.com/harvesthq/chosen/releases
     and save in your libraries location in a new "chosen" folder.
   - See instructions from the libraries module for details:
     https://www.drupal.org/node/1440066

-- CONFIGURATION --

The Mollom protection needs to be enabled and configured separately for each
form that you want to protect with Mollom:

* Go to Administration » Configuration » Content authoring » Mollom.

* Add a form to protect and configure the options as desired.

Note the "bypass permissions" for each protected form:  If the currently
logged-in user has any of the listed permissions, then Mollom is NOT involved
in the form submission (at all).


-- TESTING --

Do NOT test Mollom without enabling the testing mode.  Doing so would negatively
affect your own author reputation across all sites in the Mollom network.

To test Mollom:

* Go to Administration » Configuration » Content authoring » Mollom » Settings.

* Enable the "Testing mode" option.
  Note: Ensure to read the difference in behavior.

* Log out or switch to a different user, and perform your tests.

* Disable the testing mode once you're done with testing.


-- FAQ --

Q: Mollom does not stop any spam on my form?

A: Do you see Mollom's privacy policy link on the protected form?  If not, you
   most likely did not protect the form (but a different one instead).

   Note: The privacy policy link can be toggled in the global module settings.


Q: Can I protect other forms that are not listed?
Q: Can I protect a custom form?
Q: The form I want to protect is not offered as an option?

A: Out of the box, the Mollom module allows to protect Drupal core forms only.
   However, the Mollom module provides an API for other modules.  Other modules
   need to integrate with the Mollom module API to expose their forms.  The API
   is extensively documented in mollom.api.php in this directory.

   To protect a custom form, you need to integrate with the Mollom module API.
   However, if you have a completely custom form (not even using Drupal's Form
   API), you may also protect that, by following Mollom's general guide and
   example for PHP client implementations:

   - https://github.com/Mollom/guide
   - https://github.com/Mollom/guide/tree/master/examples/php52

Q: What happened to the Mollom Content Moderation Platform?

A: On Thursday, 1 October 2015, Acquia is ending support for the Content
   Moderation Platform (CMP) feature of Mollom, which was originally added as a
   feature in 2013.  Users who activated their CMP accounts before June 1, 2015
   will have access until that time.

   - https://docs.acquia.com/mollom/faq/platform


-- CONTACT --

For questions pertaining to the Mollom service go to https://www.mollom.com/support

Current maintainers:
* Lisa Backer (eshta) - https://www.drupal.org/u/eshta
* Nick Veenhof (Nick_vh) - https://www.drupal.org/u/nick_vh