On /admin/config/content/mollom/settings I can Save Configuration normally, but when I want to Enable Testing Mode the API Key fields are cleared and there is a message "The configuration options have been saved." along with an error message "The Mollom API keys are not configured yet."


sun’s picture

Version: 7.x-2.3 » 7.x-2.x-dev
Status: Active » Postponed (maintainer needs more info)

Hm. I'm not able to reproduce this.

Did you do anything special while submitting the settings form?

kenwest’s picture

It now works OK for me! It was repeatable at the time. I notice that when I set test mode the public and private keys get changed, and it's a different value each time. Perhaps the module was failing to retrieve those test keys when I was having the problem. Would a failure to retrieve test keys explain the issue?

sun’s picture

Glad to hear! :)

Hm. Technically, that might be a possible explanation. The REST Testing API is a total "mock" service that's really simple and small though, and I don't think that service ever was down.

Just to clear a detail up: When you disabled testing mode, did you see your original/real API keys again? Or were they lost, too?

kenwest’s picture

Sorry, @sun, I can't remember that detail, and I can't reproduce the issue.

I think the original/real keys were lost, as I have a vague recollection I had to look them up. I'm sorry I can't be more helpful, and I'd hate to send you on a wild-goose-chase.


John Pitcairn’s picture

I am encountering this problem, while testing mollom for a client, using a free subscription. The mollom module is newly installed and configured on two webforms.

Enabling test mode clears the keys, disabling test mode restores the keys.

Test mode does not work, ie a submission of "spam" is accepted.

sun’s picture

@John, some days ago, I noticed that the Testing API was not fully functional myself, too, but it resurrected shortly afterwards. Do you still experience the testing mode issue today?

John Pitcairn’s picture

Sorry, we gave up on it for now and uninstalled.

sun’s picture

Status: Postponed (maintainer needs more info) » Closed (works as designed)

OK, that's sad to hear, of course.

As I'm relatively certain that these glitches were caused by temporary downtimes of the Testing API (not the production API), which simply means that the module is not able to retrieve Testing API keys (hence, empty), and because the original/production API keys were retained and not lost (in my own testing during a downtime), I'm going to close this issue, since the client-side module does in fact work as designed.

Elijah Lynn’s picture

This is happening to me to right now and yes it does retain the original keys if you uncheck testing and resubmit the form.

Was the Testing API down last night and today still? If so I could see #8 being a valid explanation (possibly being handled more gracefully though), if not I think it may still be a bug.

jday’s picture

I am experiencing the same behavior, I've installed mollom, entered the public and private keys and checked the testing mode box, clicking the save configuration results: the keys are not saved. If I uncheck testing mode and save, the keys are saved. And going back after a successful save and checking testing mode box, the public & private keys are erased and the "The Mollom API keys are not configured yet." message comes back.