CVS edit link for Silicon.Valet

I've got a CCk Webform module among others that I'd like to add to the pool of resources. It would allow you to use CCK content types as web forms and get full access to all CCK fields and ancillary modules.

I'm active in answering questions for Drupal on stack overflow and within my local users grou (Houston). I also write a blog (on our recently relaunched site) emunications.com, check out the post on dynamic sortables in views.

I'd be thrilled to be able to add to the list of existing modules, thank you for your consideration.

CommentFileSizeAuthor
#2 cck_webform.zip10.22 KBSilicon.Valet

Comments

dman’s picture

Issue tags: +Module review

Cool.
Start with the requirements for applying for an account, post a tidy draft of the module you've got, and seriously have a look at the way things are done to get an idea of all the review issues that may slow down the process.
If you can see what happened with previous applications, you may be better set to make a quick, successful application.

Silicon.Valet’s picture

Status: Postponed (maintainer needs more info) » Needs review
StatusFileSize
new10.22 KB

Here's a zipped copy of the source for the module

Motivation:
A large number of sites have a need for webforms as part of their workflow and site requirements. While a very capable module exists (webform), it does not use CCK fields and does not expose webform results as nodes for use in views. There are a host of supporting modules for webform that attempt to fill this gap. This is a more direct solution, turning the node creation form for a content type directly into a webform. This will provide you access with the full array of tools and field types available to CCK and will allow you to use the submitted data within your site with less work.

Goal:
The cck_webform module is intended to provide an easy to configure, drop in module to add webform functionality to your site while leveraging your experience with one of the most used modules in all of drupaldom (CCK). This module will also give you the ability to manipulate and provide reports on your submissions using another widely used tool, views.

Functionality:
Displays an additional fieldset on content type edit form for content types with at least one field. This fieldset contains configurational data for the webform, allowing you to set notification address, optional cc field and customize the email subject and body using tokens. When a node of that type is created, the email is sent.

Configurable Options:

  • Use this content type as a webform
  • Notification email address
  • Optional cc email field (select box of fields available on this content type)

Files:
LICENSE.txt
cck_webform.info
cck_webform.install
cck_webform.module

Status:

What's missing is the view for reporting the submissions. I'll be adding that in the next few days along with Simplenews integration. Needs sanitization of user input. Will be added next.

Usage:

To use the module, create or use an existing content type with at least one field (text field would be most appropriate - module does not check this atm). When the content type exists, a new section will appear on the content type edit form. This will allow you to configure the webform. After doing so, and specifying that the webform should be used via the exposed checkbox any nodes of that type created will create a notification email to the specified address.

Special Notes:

This module is being developed for a code sprint we are doing to create a website in a day for a local charity (http://www.fortbendwomenscenter.org). We'll be out there Saturday, (Jul 17,2010) and folks will be using #FBWC on twitter to post progress if you'd like to follow along.

avpaderno’s picture

Hello, and thanks for applying for a CVS account. Some volunteers will review the code, pointing out what it needs to be changed.

summit’s picture

Subscribing, interested in the progress of this. cck_webform would be great!
greetings, Martijn

quicksketch’s picture

This would make me feel a bit better if it were called "Node mailer" or something like that, to avoid confusion with the webform module (which is completely unrelated). This module essentially e-mails the contents of a node based on tokens.

Silicon.Valet’s picture

This module was born out of a need to extend the webform module in a direction that it couldn't comfortably go without sacrificing ease of use. The intention of this module is for use creating web forms which in turn generate nodes. There's a certain amount of complexity that is going to go along with it, and I think that the complexity is really what separates the modules. Webform is a fantastic drop in module for providing webforms. This one, at least for now, is not. This one requires some small amount of configuration, but frees you from having to generate custom rules/actions for each form.

There are definitely differences between this approach and that of webform that would make them useful to different groups. Notably, this module requires a better understanding of permissions and careful thought of what is exposed on node create forms. There is also (currently) a requirement to generate your own views for reviewing the submissions. That's something I've almost got worked out (dynamic views!), but am not ready to share until it's a bit more mature.

That said, I definitely will defer to your judgement with respect to naming. You've been here longer than I have, and I respect your opinion. Is there perhaps a third alternative that you would be comfortable with that would allow me to use the webform term? Perhaps with the space (web form vs webform)?

zkrebs’s picture

Would this integrate as an Ubercart checkout pane? Would be most definitely awesome.

arski’s picture

Sounds interesting.

@slavojzizek: I suppose no uc-independent module will directly have that functionality, but I would be interested in extending uc_webform_checkout_pane with this once it comes out and looks workable :)

PS. as for the name, how about you remove the "web" from it? something like "CCK Forms"?

Silicon.Valet’s picture

slavojzizek: describe the use case to me, I'm not sure I understand what you're trying to accomplish.

arski: Good idea, I'll update the module

avpaderno’s picture

Assigned: Unassigned » avpaderno
Status: Needs review » Needs work
  • The points reported in this review are not in order or importance / relevance.
  • Most of the times I report the code that present an issue. In such cases, the same error can be present in other parts of the code; the fact I don't report the same issue more than once doesn't mean the same issue is not present in different places.
  • Not all the reported points are application blockers; some of the points I report are simple suggestions to who applies for a CVS account. For a list of what is considered a blocker for the application approval, see CVS applications review, what to expect. Keep in mind the list is still under construction, and can be changed to adapt it to what has been found out during code review, or to make the list clearer to who applies for a CVS account.
  1. Menu descriptions and titles are not passed to t().
  2. License files must not committed in CVS.
  3. See http://drupal.org/coding-standards to understand how a module should be written. In particular, see how the code should be formatted, and how functions should be named.
  4.     $options = array();
        $options_txt = "\n";
        $options['<NONE>'] = 'None, do not CC';
    
    

    Strings used in the user interface need to be translated.

  5. Remove any debug code.
avpaderno’s picture

Status: Needs work » Closed (won't fix)

I am closing this application due to lack of replies.

alfthecat’s picture

subscribing

sabrawy’s picture

subscribing

avpaderno’s picture

Component: Miscellaneous » new project application
Assigned: avpaderno » Unassigned
Issue summary: View changes

Please read the following links as this is very important information about CVS applications.