I was just curious if this module is going to be for Drupal version 6 or Drupal 7 ?

I'm hoping for Drupal 7 since I have a project under development ( In D7 ) that this might be perfect for. If you are starting out with D6, consider this a vote for a future upgrade to D7 :-)

Comments

MacRonin’s picture

MacRonin commented

Probably answering my own question.

While the info isn't available on the project related pages (Yet). I did find some thing by going to the commits off the developer's user page. And from that, at least the first commit appears to be D6 :-( Oh well ... still hoping for a D7 version at some point

Webform Profile: June 28, 2011 17:40

Commit 7009f13 on 6.x-1.x
by travist
travist’s picture

travist commented

There will eventually be a Drupal 7 version come out, but for our current needs, it will start out as Drupal 6. As the demand persists, we will upgrade.

Thanks!

Travis.

MacRonin’s picture

MacRonin commented
Status: Active » Closed (fixed)

Thanks for the quick response.

woop_light’s picture

woop_light commented
Version: » 6.x-1.x-dev

Would love to see this in Drupal 7!

In the meantime I found a decent workaround:

1. Install and enable the Profile2 module.
2. Update your files with this wonderful patch: http://drupal.org/files/issues/1001798-webform-tokens-latest.patch.

Then you can prefill/prepopulate your webform components with the registration values stored by Profile2 the same way that you would normally do it. As the patch describes:

1. Just edit or add a new component of a webform to display the mentioned "component edit form".
2. Inside the form, navigate to the default value field.
3. Right below this field you can see the collapsed fieldset "TOKEN VALUES". Open it and set the default value for the field by just clicking on the desired token.

Perhaps there are other ways to do it, but this did the trick for me. Hope it saves someone time and headache.

woop

Also I'm using v 7.x-3.11

shadowdknight’s picture

shadowdknight commented

Does your patch work for 7.x-3.15

travist’s picture

travist commented

Right now, our current need for this module is for Drupal 6. We eventually will be migrating to Drupal 7 and when that happens, this module will be upgraded, but I don't see that happening for a while. So, unless someone out there decides to take on the challenge, this module probably won't get upgraded to D7 for at least the next couple of months. If anyone wants to try and upgrade it, I will make them a co-maintainer of this module.

As for the patch, that is definitely a good workaround, but only does a portion of what this module does. This module basically provides profile-linked webform components that can easily be added to the webform ( without having to manually add the components ) that form a direct link to the user profile. This not only auto-populates the values based on their profile ( like token does ), but it also will also give them the option to update their profile if they provide different data in the webform. On the flip side of that, it also gives them the option to update all their webform submissions if they update their profile with different data.

jeremymcminn’s picture

jeremymcminn commented

Hi Travis

Just watched your webforms in d7 screencast. Thanks for the good info - You mentioned this module and I see that D7 is not supported right now, do you have any plans to do this in the future?

Thanks

paskainos’s picture

paskainos commented

@jonnyfiasco: if we're talking about the same screencast uploaded on Feb 20, 2012, then it may indeed be time for a [D7] status update. :)

@travist: I was also curious how much, if any, overlap there is with Webform Entity.

jeremymcminn’s picture

jeremymcminn commented

Paskainos - thats the one!

travist’s picture

travist commented

Yeah, to be honest, I see Webform Entity being the way to go within Drupal 7, so this module is probably going to deprecate in favor of that one. I may end up adding to it though to bring in some of the features that this module has but just build on top of that module.