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.Note, at time of writing this patch *must* be applied to the D6 version of the module - #1088074: call to undefined function _eloqua_cron on line 54 eloqua.module.
Title does what it says on the tin. Patch to follow shortly. =)
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | 1361630-1-user_profile_support.patch | 19.93 KB | greg.harvey |
Comments
Comment #1
greg.harveyPatch attached, actually created by bellesmanieres for proper Git attribution purposes.
Comment #2
drupalninja99 CreditAttribution: drupalninja99 commentedThis looks pretty good, I worry about the amount of effort it's going to take to port this to D7. I am thinking it would be better to have like an entity forms module. Eric Peterson from the entity api project said as much. For D7 wouldn't you want to be able to map any entity form to an eloqua form?
At this stage I am not sure this is worth committing to the eloqua project. It might need to live as a sandbox module. I don't want to have to support new D6 functionality that isn't also ported to D7 and this one would not be ported easily.
Comment #3
drupalninja99 CreditAttribution: drupalninja99 commentedI am thinking we should postpone this one. It would be useful to some D6 users as a sandbox that I could reference from the project description.
Comment #4
drupalninja99 CreditAttribution: drupalninja99 commented@greg.harvey do you have a D7 port for this?
Comment #5
jasonawantclosed as outdated.