Jump to:

Tried to find corresponding issue - but could only find closed 6.x issues.

My question is: What should "admin/content/webform" show?

Right now it shows all nodes, that potentially could have a webform. I instinctively feel that it should show alle nodes with a specific webform, with at least one component. I guess the record_exist value should be TRUE.

Comments

Right now it shows all nodes, that potentially could have a webform. I instinctively feel that it should show alle nodes with a specific webform, with at least one component. I guess the record_exist value should be TRUE.

This page shows:
- ALL "webform" nodes.
- Any other webform-enabled nodes that have ANY CHANGES to the webform default configuration (components, e-mails, settings, etc.)

The second condition is enforced indirectly. Since Webform will not allow rows in the "webform" database table unless the webform settings differ from the defaults. Note that other modules that extend Webform may break this rule if they don't properly implement hook_webform_node_defaults_alter().

» Webform "admin/content/webform" page should only show nodes with webform configuration, not all webform-enabled types

Category:

support

» bug

Priority:

Normal

» Minor

Hm, you're right. That's quite dumb. We go through all this work to make sure that the "webform" database table is nice and clean, but then the SELECT statement is just directly against the "node" table! We should be able to fix this easily enough by adding an INNER JOIN to the webform table.

just wanted to chime in to say I too have been struggling with this one. I just updated to 7.x-3.19 and this patch apparently is not included there. So I switched to the dev branch and that works great. But I thought you should know it's not in 7.x-3.19, and I think it ought to be.