First of all, thank you for a terrific module! There's just one annoyance I'd like to report, in both the 5.x and 6.x versions of the module.

I just wasted over an hour trying to figure out why my Webforms were not visible to the general public, only to discover that they were not published! Because I had previously changed the content type's workflow settings to make all new nodes published by default, I hadn't thought to check the publication settings of each individual form. When I rechecked the content type settings, they were still set to published. However, Webform appears to override the setting and make all new forms unpublished by default.

I realize this is probably a well-intentioned feature for my own protection, but as far as I can tell it is not mentioned in the documentation, so I was not aware of it and wasted a lot of time and got very frustrated. I can imagine two approaches that would be preferable to allowing me to change the setting and then ignoring my change:

1) set the content type default to unpublished, but allow me to change it and respect my change
2) set the content type default to unpublished and don't allow me to change it, and tell me that it's for my own protection

I hope you will consider implementing one of these changes in the future. Thank you again!
Ben Stallings
Interdependent Web

Comments

quicksketch’s picture

quicksketch
he/him
commented
Status: Active » Closed (fixed)

I agree that generally this was not the best idea on my part. The forcing of webforms to be unpublished was indeed intentional, because I figured you'd never want to show a form before you'd actually added any fields to it. However the end result really is quite confusing and it's tripped up quite a few users. However that's the way I had designed it, so we'll keep it that way within the 2.x branch. This is no longer the case in the 3.x version, which I'm hoping to put out betas in the next few weeks.