Webform versus CCK

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
megamatt's picture

I'm looking to create a form that a user can submit DNS information with. I've attached a screenshot of a generic layout of a DNS form from another application to use as a guideline. The problem is the horizontal layout of multiple fields in a row. Just wondering if anyone else has tackled this before and if it's possible in either Webforms or using CCK to customize the layout. See screenshot for an example.

AttachmentSize
dns_form.png38.17 KB

Comments

You can theme a CCK form:

univate's picture

You can theme a CCK form: http://drupal.org/node/101092

Wondering the same thing.

charlie-s's picture

90% of the time it's an obvious decision; like when I need to setup some kind of support-ticket it's much more appropriate to use CCK, but when I need to setup a form where a user might need to request information it would most likely be webform. CCK is easier to theme but it's easier to setup a new webform. CCK works better with triggers, actions and views, but a webform is just quicker.

I guess it would always be more powerful to use CCK but a lot of the time it's simply overkill. sigh Answering my own question, I think...

Other stuff

Cablestein's picture

I like CCK, but in using it for form submission, am I right in saying that every submission becomes a node?

And thus all the submissions will be displayed in "Admin/Content Management/Content" ???

I want CCK and the potential to use Views, but I want all form submission to be entirely seperate from all other nodes. I don't want submissions to be seen as nodes. Can Views be setup to build generic SQL queries, from X table?

Anyways I'm using Webforms and it is indeed seperate from the entire node system. I haven't gotten into the theming/customizing of it yet, but the sepertion of form submissions from nodes is very important to me.

You are correct

charlie-s's picture

You are correct, CCK is a content-type extension in that it creates nodes. Whether or a user goes to node/add/page or node/add/my-cck-type they're just creating a node in your system.

Webform submissions are indeed just "webform submissions" and don't behave like nodes. Recently, some users have made a webform-views plugin (http://drupal.org/project/webform_views) that will let you mess with webform submissions inside Views, which is a very useful feature. The module says it's no longer maintained as Webform 3 support views natively.

Either way, what is it specifically about keeping submissions "separate from the entire node system" that you need? The way I see it...

  • Nodes can be indexed in search results, webform submissions can't (or don't)
  • Nodes can be used more readily within views, panels, etc., and allows for future sorting and examining needs that may arise
  • Nodes get clean URL aliases

If it's a privacy issue, there are only a couple steps you would need to take if you wanted to use CCK:

You can even get more

davidw's picture

You can even get more specific with making nodes restricted based on taxonomy. I use TAC Lite (http://drupal.org/project/tac_lite), but there is also TAC (http://drupal.org/project/taxonomy_access). Both of these allow fine grained access to nodes. I like TAC_Lite because I can allow or deny access based on a taxonomy term and a user role.

Thanks for the links, I'll

charlie-s's picture

Thanks for the links, I'll check these out and compare.

For original poster of this comment chain -- I'd really only ever use Webform when the content doesn't need to be stored on the website:

  • Contact forms
  • Survey (since Webform already shows you good metrics based upon submissions)
  • Appointment forms
  • Information requests
    etc.

If the goal is simply to send an email or questionnaire to an email address, use Webform. I suggest CCK for all other scenarios where futureproofing may be necessary.

Hey thanks for the info and

Cablestein's picture

Hey thanks for the info and links, will come in handy.

I'm aware of the possibilities with security/privacy but I see it as lots of stuff I have to wade through to make sure everything is protected. What I mean is a lot of stuff is setup to be public by default.

I'd rather start on the other side of the coin where by default everything is inaccessible, when it comes to sensitive data.

For now the current project is for a small, flexible client, not that big budget, so for time sake I will continue with Webforms.