How do I test Mollom?
Mollom provides a testing mode to allow you to test the integration and determine how CAPTCHA challenges display on your website.
This testing mode works against a separate Testing API that is detached from the production system, but works identically otherwise.
The Mollom plugin used on your website needs to support the testing mode option. If it does, then you can toggle the testing mode in its global settings.
When testing mode is enabled, Mollom reacts to special string literals:
- For text analysis, you can trigger the corresponding responses when using one of the literal
unsurestrings in a post. If none of the literal strings is contained, Mollom returns
- All image CAPTCHAs can only be solved with the literal string
- All audio CAPTCHAs always spell the word
Ensure that you only enable testing mode in controlled environments, and disable it as soon as testing is finished. If you leave it enabled, regular visitors to your website may not be able to post anything.
Mollom's production API does not provide a magic testing string, nor any other means to test its behavior.
By attempting to test Mollom on any website that does not have testing mode enabled, you will negatively affect your own author reputation across all websites that are protected by Mollom.
I found a bug in a plugin — will you fix it?
The Mollom engineering team helps to maintain the plugins for Drupal and WordPress. However, these open-source projects rely on contributions from the community. The more users get involved and help to test, the faster issues can be resolved.
Mollom customers pay for using the Mollom web service, not for maintenance of the plugins. However, it is in our own interest to make sure that the Mollom plugins work well, and we will assist you in bringing bugs to the plugin maintainers' attention.
Do I have to use the plugins available on your website?
No, the Mollom API is fully documented and open.
You can use any of the Mollom API calls for whatever purpose may suit you. For example, if you only want CAPTCHAs, just ask for CAPTCHAs.
Why are most clients open source and the back-end closed source?
Mollom is built around an open API, making it possible to implement it in a large number of applications, CMSes, and web services.
We strongly believe in open source and actively support several open source plugins.
Our back-end technology, however, will remain closed source. Giving away the intelligence we need to detect spam, generate rock-solid CAPTCHAs, and figure out the quality of your content could be turned against us and used to create malicious, unblockable content.
Does my plugin have to be open source?
No, you can implement the open API and use it in proprietary software. We do encourage openness, but you are free to use the API anywhere you choose.
Can you add my client plugin on your download page?
Contact us and we will put your client on our download page.
Please note that we will review and evaluate your code for correctness. In general, we prefer client plugins that use a liberal license (such as MIT, GPL, or BSD).
Can you customize Mollom or integrate it for me?
We do not currently provide professional services around Mollom. If there is no Mollom plugin for your CMS on our download page, we probably cannot help you directly. However, Mollom provides an open API, which can be implemented in most web services, content management systems, and other web applications.
We usually don't take a lead role in implementing plugins, but we do encourage CMS vendors, consultants, and web developers to do so, and will assist with code reviews and troubleshooting via e-mail as time permits.
For approved companies, our software and reseller partner program is also available.
We recommend that you work with a service provider for your CMS of choice and that you connect them with us using our contact page.
Can I retain spam posts instead of blocking them?
Not all users are comfortable with the idea of Mollom discarding spam posts without the possibility of manual review. The Drupal Mollom module provides a configuration option that allows comments to be retained as unpublished posts in your website's moderation queue. Moderators and website administrators can then periodically review the moderation queue if necessary.
Only forms that support a publishing status (like comments or nodes/content) may be retained.
This feature is not available for some third-party Drupal modules, which do not have a publishing status. A popular example of such a module is Webform.
My website shows a "Mollom test form." How can I disable it?
The "Mollom test form" is used in Mollom unit testing, and is not necessary on a website that uses Mollom to protect content or comments.
For this entry to appear in your menu, you must have mollom_test.module enabled in your modules list. There's no reason to have that module enabled, unless you're doing unit testing of some kind. Go to admin/modules, and then clear the mollom_test.module check box, which will uninstall that module and prevent that menu entry from appearing for all users.