Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hi--first, thanks for this module! It is a feature I could use but unfortunately I'm not php literate (yet!) and so am wondering if you know when a D7 version might be available. Thanks again!
Comment | File | Size | Author |
---|---|---|---|
#12 | webform_constant_contact_d7port2.tar_.gz | 6.19 KB | attheshow |
#11 | webform_constant_contact_d7port1.tar_.gz | 5.59 KB | attheshow |
Comments
Comment #1
justphp CreditAttribution: justphp commentedI've already started work on it but it's not a straight forward port from D6, it will need quite a big rewrite of some bits so might take a few more weeks.
Comment #2
cartagena CreditAttribution: cartagena commentedThanks so much. I am in awe of programmers...
Comment #3
primitive CreditAttribution: primitive commentedYes, a D7 version of this module would be a massive help. Glad to hear you're working on it! Thanks for your contributions, justphp.
Comment #4
ELS Landscape CreditAttribution: ELS Landscape commentedDo I need to lean on Constant Contact if they want to keep me past my 60 day trial? I would hope they support the Development.
Comment #5
justphp CreditAttribution: justphp commentedyes they should let you extend your trial for development purposes, I have a trial account about 2 years old that still works.
Comment #6
ELS Landscape CreditAttribution: ELS Landscape commentedYes but you are actually developing the code. :P
I want to push them to support you in getting it developed.
I think Constant contact has some skin in this game.
Comment #7
justphp CreditAttribution: justphp commentedConstant contact paid me to develop the Wordpress Plugin so they are receptive to people suggesting new integrations, I doubt they would sponsor a webform component integration for d7 but worth asking them I guess!
Comment #8
JuliaKoelsch CreditAttribution: JuliaKoelsch commentedHello,
I am curious about the status of this issue -- it's closed, but it doesn't look like it's been released yet. If it's not ready yet, do you have a sandbox for it? Maybe some of us could pitch in and help. Thanks!
Comment #9
jerry CreditAttribution: jerry commentedEchoing the comments above. I could use this and would be willing to lend a hand to get it released. A dev release would be an excellent start.
Comment #10
benschaaf CreditAttribution: benschaaf commentedAlso interested in seeing this happen. Could potentially sponsor in part.
Comment #11
attheshow CreditAttribution: attheshow commentedFirst pass at a D7 version. I'm also going to be trying to add in the ability for additional field values on the same form (as long as they're named according to the API naming conventions for fields) to be pulled in when users are added/updated via the webform.
Comment #12
attheshow CreditAttribution: attheshow commented2nd draft is attached. A bit more code cleanup. I also fixed the database query in the module to use the new PDO/DBTNG query style. And I added the functionality I mentioned above. If the user names other webform fields (machine name) according to the mappings that they have set up within the main Constant Contact module's configuration screen, any matching webform data should travel over to Constant Contact too along with the email address.
Comment #13
justphp CreditAttribution: justphp commentedGreat, ill put this out as a development release when I get a mo.
Comment #14
waltercat CreditAttribution: waltercat commentedJust upgraded to D7 and the port is not working for me. I am getting this:
Also I have multiple newsletter lists and even though I select only one, it shows all of my newsletter lists.
I am happy to pay to have a D7 release version finished up.
Comment #15
waltercat CreditAttribution: waltercat commentedOffer is still out there to pay for a port of this to D7.
Comment #16
justphp CreditAttribution: justphp commentedSorry I just don't have the time for this right now.
Comment #17
attheshow CreditAttribution: attheshow commentedThe code from #12 has been submitted as a D7 1.0 release now. Marking this issue as fixed.