Hi
I have been have the 7.x-2.3 version for a while & this seems to work without incident.
I however wanted to change some settings & when I tried to go to the configuration page (/admin/config/content/mollom), it is BLANK. I have not had any blank errors for many months & in fact have memory set at 200MB, which I think is more than sufficient for this VERY low traffic site.
On the reports & some other pages, I have AT TIMES got this error message: Warning: array_merge(): Argument #2 is not an array in mollom_form_info() (line 919 of /home8/woof/public_html/abc/default/modules/mollom/mollom.module). I have not been having such messages before.
I tried to upgrade to the latest dev version, but this has not helped.
All my modules are up-to-date. To help fight spam, I also have captcha & honey pot, which have helped considerably reduce spam submissions.
Mollom is available on a couple of forms, though.
How do I get of these ugly errors? It surely must be possible to access the configuration page ...
Thank you in advance
Comment | File | Size | Author |
---|---|---|---|
#4 | 0001-1833262-by-sun-Fixed-mollom_form_info-does-not-log-s.patch | 1.26 KB | sun |
#1 | mollom.form-info-error.1.patch | 986 bytes | sun |
Comments
Comment #1
sunCan you try attached patch?
Comment #2
lionheart8 CreditAttribution: lionheart8 commentedHi
Thank you for the response.
I tried to do the patching but got stuck, although this is not the first time to use a patch.
I got a bit mixed up by this bit:
Exactly what did I have to do with the current mollom module script I had (7.x-2.3)?
I otherwise understood the last bit, below "// Any information in hook_mollom_form_info() overrides the list info."
Where I replaced that piece of code
- $form_info = array_merge($form_info, module_invoke($module, 'mollom_form_info', $form_id));
with the lines beginning with "+".
I also tried "7.x-2.3+2-dev of 2012-Nov-14", (which I now have) but still have the blank page at /admin/config/content/mollom
Thank you & kind regards
Comment #3
sunSorry for the delay. I've committed the patch in #1, so there should be a new development snapshot in ~24 hours (tomorrow).
Could you try once again after updating to that tomorrow?
Note that the committed patch will only fix the blank page; it does not fix the underlying problem, which seems to be that a form that was previously protected does no longer exist in your system. It should, however, allow you to remove the bogus/stale form protection.
Comment #4
sunComment #5
sunOh. Apparently, we did not backport #1352012: Feedback options appear for every entity bundle, even when not protected, so this patch makes no sense for D6 right now.
Comment #6
sunI've reverted the commit from #1.
This generally sounds like a duplicate of #804466: Orphan forms of other modules cause errors on administration page