Repeatable: Always

Steps from a fresh, standard install:
1. Enable module 'mollom', configure API keys.
2. Add a form for Mollom to protect (e.g., Node: Article form)
3. Add a user or change permissions so that you can create nodes but not bypass Mollom protection.
4. Create some nodes of various types (e.g., Articles and Basic Pages)
--> Mollom is correctly protecting the Article form but not the Page form, as expected.
5. Delete a node of the protected node type, and one of an unprotected type.

Expected Results:
Deleting an Article yields a "Report as inappropriate" form, which is fine, because I protected that form.

Actual Results:
In addition to Article, deleting a Page also yields this form, even though I did not protect this form.

For some content types the content reporting is not necessary. In addition, since the "Report as inappropriate" form defaults to "Unwanted, taunting, off-topic", I am concerned that editors who habitually click "next" will end up reporting false positives to Mollom.

I'm a novice module developer, but I will investigate and submit a patch if it's relatively straightforward.

Comments

areikiera’s picture

areikiera commented
Status: Active » Closed (duplicate)

@marleythedog,

There's another post about this here: #1352012: Feedback options appear for every entity bundle, even when not protected, and while it's technically the duplicate, I thought I'd change the status here since @Moloc started suggesting a solution, though it looks like the progress has slowed.

Were you able to solve this with a patch or otherwise? I'm experiencing the same problem, and would really appreciate it if you could share if/how you solved it.

Thanks!