Webform module allows to attach a webform to any content type selecting "Enable webform functionality" during the content type configuration.
By default, Webform workflow module only works with Webform content type, no with others. I've developed a patch to fix it.
With my patch, the Webform workflow module checks all content types with webform functionalities and allows the workflow for them, but when you enable the webform functionality in a new content type, you must uninstall/install Webform workflow module to allow workflow in it, maybe somebody would fix it... ;)
Comments
Comment #2
joel_osc commentedI think this is a legitimate defect. Changing status, testing patch.
Comment #3
natew commentedThank you for the module and the patch. I ran into this issue and the patch solved the problem.
I am using the webform_template module and created my own content type with webform enabled. I ended up adding the webform_workflow_states field manually and used the features module to make sure the field is added/deployed. This way I didn't need to uninstall and re-install to get the field instances. Which wasn't really an option for our setup.
Comment #4
laboratory.mikeI have tested the patch and it works as written.
Comment #5
pjcdawkins commentedThe problem isn't that the module doesn't support all webform content types. The problem is that the field instances are only created (automatically) on install, not at any other time.
The intended logic in the patch (finding webform content types and creating instances for each one) is already implemented in the
webform_workflow_install()hook:After installing WW, it's still easy to add a field instance to a new Webform content type - you would use the normal Field UI. I'm not sure if (or when) that should be done automatically - users do not necessarily want WW on all their webforms.
Comment #6
fgjohnson@lojoh.ca commentedThought this should be better named.
Easier to find.