See this issue: https://drupal.org/node/2180233

I am running Mollom 6.x-2.7. Immediately after upgrading Webform from 6.x-3.19 to 6.x-3.20, the Mollom module began reporting errors such as "Webform module's webform_client_form_xxxx form no longer exists." In addition, the mollom module no longer offered me a list of webforms to protect.

Per the fourth comment on the above issue on Mollom, I changed line 3656 of webform.module as described in the above referenced issue. That fixed the problem.

Since the problem was fixed by modifying the webform module, it seems to me that the issue belongs here.

Comments

DanChadwick’s picture

DanChadwick CreditAttribution: DanChadwick commented
Status: Active » Fixed

Definitely a bug. Committed to 6.x-3.x-dev.

Bug does not exist in 7.x-3.x-dev or -4.x-dev due to use of Drupal 7 database API.

2ndmile’s picture

2ndmile CreditAttribution: 2ndmile commented

Same problem here. Updating to dev fixed it.

Status: Fixed » Closed (fixed)

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

Chroid’s picture

Chroid CreditAttribution: Chroid commented

Sorry to re-open a closed issue, but there's mention of this being committed to -dev, yet, unless I'm mistaken, the project page has no releases available beyond 6.x-3.20?

Is there an official Webform stance on this bug?

Cheers

Chroid’s picture

Chroid CreditAttribution: Chroid commented
Status: Closed (fixed) » Needs review
quicksketch’s picture

quicksketch
he/him
CreditAttribution: quicksketch commented
Status: Needs review » Fixed

I'm mistaken, the project page has no releases available beyond 6.x-3.20?

You can download the 3.x-dev version with drush or from this page: https://drupal.org/node/730862

This will be in the 3.21 release of the module. But since we released 3.20 so recently, I'm not sure if we have a timeline for 3.21.

Commit http://drupalcode.org/project/webform.git/commitdiff/0ce220ff666b2e24669...

Status: Fixed » Closed (fixed)

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

Chroid’s picture

Chroid CreditAttribution: Chroid commented
Status: Closed (fixed) » Active

quicksketch, thanks for your reply but your suggestion for the dev version appears to only exist in a D7 branch? Will a 3.21 release come for D6 and is there currently a D6 dev branch ? Am I missing something obvious?

quicksketch’s picture

quicksketch
he/him
CreditAttribution: quicksketch commented

You can find the dev release for 6.x-3.x by clicking "View all releases" on the project page. The direct link for the 6.x-3.x release is https://drupal.org/node/730872.

Chroid’s picture

Chroid CreditAttribution: Chroid commented
Status: Active » Fixed

My apologies! Missed the paging at the bottom of the filtered results :L

Thanks again.

gastewart’s picture

gastewart CreditAttribution: gastewart commented

We have multiple production sites protecting webform nodes with mollom, and we are receiving tons of spam since the breakage. It is terribly disappointing to hear that there is no timeline for a stable 6.x release with this bug fixed. A dev release is not something we will use on a production site, and I don't really want to fork a 'custom' module from the previous release.

Any chance there is going to be a stable release soon ?

quicksketch’s picture

quicksketch
he/him
CreditAttribution: quicksketch commented

Any chance there is going to be a stable release soon ?

I usually make stable releases after reviewing the current queues of all new bugs filed since the previous release and reviewing any submitted patches in the "needs review" or "reviewed and tested by the community" status. I usually do this every few weeks, so I'd estimate some time in May or early June at the latest. Patching your modules until the next stable release is actually quite common as described in http://www.jenlampton.com/blog/sustainable-development-workflow-patching.

Status: Fixed » Closed (fixed)

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

nickorr’s picture

nickorr CreditAttribution: nickorr commented

quicksketch,

it's now early July, any chance of a new release soon?

Thanks,
Nick

rosell.dk’s picture

rosell.dk CreditAttribution: rosell.dk commented

I would also like to see this bugfix in a new release, thanks