I was using 6.x-1.10, then upgraded to 6.x-1.x-dev to enable the 'any form' feature (to protect my webforms). The upgrade went flawlessly (no errors, etc.), but when visiting the Mollom settings page, none of my forms are protected; I have to go through one-by-one and enable them manually (I previously had ~20 forms protected by Mollom).

Feel free to change this if you don't consider it a bug, but I'd have thought upgrading would at least keep any previously protected forms protected...

CommentFileSizeAuthor
#1 mollom-DRUPAL-6--1.update.patch777 bytessun

Comments

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Active » Reviewed & tested by the community
StatusFileSize
new mollom-DRUPAL-6--1.update.patch777 bytes

Indeed. Attached patch fixes this issue (tested).

Anonymous’s picture

Anonymous (not verified) commented

Thanks! It's too late for me, but it'll stop others having to go through what I did ;)

dries’s picture

dries commented

Do you mean "do _not_ get stale information"?

dries’s picture

dries commented
Status: Reviewed & tested by the community » Fixed

Committed to CVS HEAD and DRUPAL-6--1. Thanks!

prodosh’s picture

prodosh commented

Does Mollom 6.x-1.x-dev protect Webforms now?

sun’s picture

sun
Primary language German
Location Karlsruhe
commented

@pban02: Not yet. Integration with Webform is tackled in #686136: Implement hook_mollom_form_info for submission protection by Mollom

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

  • Commit 7ae263b on master, fai6, 8.x-2.x, fbajs, actions by Dries: 
    - Patch #687626 by sun: no forms protected by default when upgrading.

  • Commit 7ae263b on master, fai6, 8.x-2.x, fbajs, actions by Dries: 
    - Patch #687626 by sun: no forms protected by default when upgrading.