<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Yeah that's not exactly how webforms works - you can't create content
that is then publically accessible - it would email and/or database the
submissions and then an admin would have to go in and create the actual
content type. Using cck to create a content type and allowing that
role to create and edit would be the way to go for this.<br>
<br>
.s<br>
<br>
Jason Flatt wrote:
<blockquote cite="mid:200709181407.36011.drupal@oadaeh.net" type="cite">
<pre wrap="">On Tuesday 18 September 2007 11:38:07 Fred Jones wrote:
</pre>
<blockquote type="cite">
<pre wrap="">sander-martijn wrote:
</pre>
<blockquote type="cite">
<pre wrap="">For much greater flexibility and easier maintenance consider the
webforms module. This allows you to add as many custom fields as you
need, email different addresses, add content before and after, database
the info and look at stats etc. That's what i used to create 3
different contact forms that included questionaires etc.
</pre>
</blockquote>
<pre wrap="">This raises an interesting question. I have a site where we want to
allow members who are of the type 'Volunteer' to login and submit a form
with a few fields like:
DATE
ACTIVITY (dropdown)
NOTES (textarea)
Then we need to allow both the admins and the Volunteer himself to be
able to view a table of all such records, where Date, Activity and Notes
are the columns. Each Volunteer could of course see only his own records
and the admins would need to be able to view a unique table for each
volunteer.
We started this with CCK, but I haven't gotten it just yet.
Is webforms the way to go for this?
Thanks!
</pre>
</blockquote>
<pre wrap=""><!---->
I believe the best way to go is to use CCK and Views. You create a new
content type w/CCK. You give the volunteers to ability to create content and
edit their own content for the new node type in the Access control area.
Then you create as many views as you need to display what you need to whom
you need (two might work, but might require the creative use of $args).
Though I haven't actually tried it, I don't think you can get your views (or
reports) the way you want them with the Webform module.
</pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<hr align="center" noshade="noshade" size="1" width="100%">
<p
style="text-align: center; font-family: verdana,arial,helvetica,sans-serif; color: rgb(51, 51, 51); font-size: 10px; text-transform: lowercase; font-style: normal; font-weight: normal;"><a
href="mailto:sander@sander-martijn.com"
style="text-decoration: none; color: rgb(0, 0, 255); font-family: verdana,arial,helvetica,sans-serif;">sander-martijn</a><br>
interface developer | architect<br>
<a href="mailto:sander@sander-martijn.com"
style="text-decoration: none; color: rgb(0, 0, 255); font-family: verdana,arial,helvetica,sans-serif;">sander@sander-martijn.com</a><br>
<a href="http://www.sander-martijn.com"
style="text-decoration: none; color: rgb(0, 0, 255); font-family: verdana,arial,helvetica,sans-serif;">www.sander-martijn.com</a>
</p>
<hr align="center" noshade="noshade" size="1" width="100%"></div>
</body>
</html>