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,
We're starting to use this module and our client is very interested in expanding on it. Would you be willing to make me and my colleague co-maintainers so we can commit our work here? One of the things we would like to do is extend it to support the core Drupal user profile module. We're doing this work next week, so we will either add it to this module or create a new eloqua_profile module, depending on your response. =)
Comments
Comment #1
doublejosh CreditAttribution: doublejosh commentedWe've been using a custom built Eloqua module for the past few years and would like to roll this in as we switch to D7.
We've tied it to user registration, submit the request async and have a tracking block.
Down to work on this.
Comment #2
greg.harveySounds cool - we've created the eloqua_profile module, which works in D6 for registration form and core profile fields - just testing it now. There's probably cross-over, from what you say. Happy to share code. I'll work up a patch at some point soon.
Comment #3
doublejosh CreditAttribution: doublejosh commentedNice. We're super tired of maintaining it alone and having it live in custom land.
At our conference this week, so will try to get a patch out so we can perhaps both look at approaches and unify somehow.
Would be nice to have:
eloqua/eloqua.module
eloqua/eloqua.info
eloqua/eloqua.api
eloqua/admin.inc
eloqua/eloqua_webform/eloqua_webform.module
eloqua/eloqua_webform/eloqua_webform.info
eloqua/eloqua_user/eloqua_user.module
eloqua/eloqua_user/eloqua_user.info
The async and API stuff could live in the .inc file.
Comment #4
doublejosh CreditAttribution: doublejosh commentedThis came up again today though still tied up with a few 4th quarter projects before we get into this one.
Wanted to note: Additionally, our module integrates with Form Block in that it will add any CCK fields from a node (like field_eloqua_campaign_id) to the registration form so you can pass the node's campaign through during the registration.
This is kinda the whole point in our use of Eloqua. We use the same form to register the user, but add-in the node info to track the campaign and do an async post.
Comment #5
greg.harveyOh, you want a patch! I forgot. Let me see if I can get one...
Comment #6
doublejosh CreditAttribution: doublejosh commentedI feel like I owe one as well :)
Comment #7
greg.harveyOK, done my bit... ;-)
#1361630: Create support for mapping user profile fields to Eloqua
Comment #8
greg.harveyActually caught up with csevb10 on Twitter - haven't tried it yet, but he's more than happy to have a co-maintainer and has added me to the git committers for this module. \o/
@doublejosh, patch away! I can review and commit. =)
Comment #10
doublejosh CreditAttribution: doublejosh commentedSorry, wrapped up in simpleSAMLphp.
Comment #11
drupalninja99 CreditAttribution: drupalninja99 commentedIs there anything else in this ticket? If there is it would help if you updated the issue description. My take was that the scope of this was merging a couple different modules?
Comment #12
drupalninja99 CreditAttribution: drupalninja99 commentedI agree w/@doublejosh that we should try to move towards separating out the API from the various functions. Webform, entity forms, etc.. We will look at plans how to do that after we can shore up some bugs. Will postpone this for now.
Comment #13
drupalninja99 CreditAttribution: drupalninja99 commentedWe could also look at refactoring to use the Entity API module as a dependency.
Comment #14
drupalninja99 CreditAttribution: drupalninja99 commented