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

doublejosh’s picture

We'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.

greg.harvey’s picture

Sounds 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.

doublejosh’s picture

Nice. 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.

doublejosh’s picture

This 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.

greg.harvey’s picture

Oh, you want a patch! I forgot. Let me see if I can get one...

doublejosh’s picture

I feel like I owe one as well :)

greg.harvey’s picture

greg.harvey’s picture

Status: Active » Fixed

Actually 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. =)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

doublejosh’s picture

Status: Closed (fixed) » Needs work

Sorry, wrapped up in simpleSAMLphp.

drupalninja99’s picture

Is 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?

drupalninja99’s picture

Status: Needs work » Postponed

I 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.

drupalninja99’s picture

We could also look at refactoring to use the Entity API module as a dependency.

drupalninja99’s picture

Issue summary: View changes
Status: Postponed » Closed (fixed)