I created a very simple module for integrating the Mollom module with the Domain module (Domain Conf).
By default Mollom stores the Public and the Private key inside the system variable table. And since its generally not such a good idea to prefix the variable's table with the Domain Prefix module for additional domains, its unfortunately not possible to have different "Public" and "Private" keys for your Mollom install.
With this small module you can without hacking Mollom or the Domain_Conf module, edit these keys in the Domain Batch pages per domain (admin/build/domain/batch). The Public and Private key for the default domain is edited at the standard admin location (admin/settings/mollom).
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | domain_mollom.tar_.gz | 8.38 KB | Terence Westphal |
| #2 | domain_mollom.tar_.gz | 1.66 KB | Terence Westphal |
| domain_mollom.tar_.gz | 746 bytes | Terence Westphal |
Comments
Comment #1
agentrickardThis approach should also expose the variable to Domain Conf. Nice. This should get a separate release. Perhaps as part of the Bonus Pack?
http://drupal.org/project/domain_bonus
For those of you new to the module, this is the proper way to expose a per-domain variable setting to the Domain module.
Comment #2
Terence Westphal commentedI am glad you approve the way I made this small module. It would be best to give this module its own release.
And sure it could be added to the Bonus Pack if you think thats the best place to put. I think it servers it purpose best if its link to by the Domain Access module instead of the Mollom module. I guess here is where people are going to look for it. Since its only useful when using Domain Access.
I added some comment to the code and made a readme for it.
Feel free to adjust anything if you think things could be better.
I would like to see this end up inside the bonus pack. Or If the Bonus pack maintainer thinks otherwise you may create a release for it if you like.
Comment #3
agentrickardI'm maintaining too much code as it is, and reject all additions to the DA core project.
Comment #4
dries commentedFrom reading this issue, it doesn't sounds like this need any modifications to the Mollom module. Is that accurate? If not, please comment on #545960: Integrate with Domain Access module.
Comment #5
Terence Westphal commentedI have decided to apply for an CVS account to give this module its own project page.
The attachment is the version I will commit to the cvs when my application is accepted. I made a small code cleanup for readability.
Comment #6
agentrickard@Dries-
If the Mollom module wanted to implement the hook directly, then we wouldn't need a stand alone module. But either approach is fine.
Comment #7
Terence Westphal commentedMy first guess is that the "Mollom" module will de used on all/most/alot sites (Or its equivalent Anti-SPAM module of course).
Where this module "Domain Mollom" is only used at sites that use the "Domain Access" module in combo with "Mollom".
Derived from this, to me it looks that the "Domain Mollom" is best not implemented into the (main) "Mollom" module. That way it keeps it light weight.
Comment #8
agentrickardWell, considering that it adds < 50 lines of code, I don't think it's a big deal. Whatever you folks decide. I have already decided that DA core only supports Drupal core, and this is a similar debate.
Comment #10
rogeriodec commentedI do not know why, but I configured this module Domain Mollom using the same key for all my 50 subdomains (bulk), however Mollom's report shows no activity for more than two months and some of my subdomains has received messages of robots (which usually are blocked by other sites that I have, which do not use the module Domain Access).
Someone could give some a hint how I can easily operate Mollom in all subdomains?
Comment #11
agentrickardComment #12
rogeriodec commentedI solved #10.
I had created individual contact forms for each subdomain.
Thus, the form name passed from
contact_mail_pagetodomain_contact_mail_page.I manually changed the field
form_idof tablemollom_formfordomain_contact_mail_page(after I cleared the cache) and now everything works.