• Resolved designactionria

    (@designactionria)


    Hey Cornershop folks!

    I’ve got a question regarding the Supporter Fields. I’d like to be able to feed data into custom fields within Salsa Engage.

    I checked out how the plugin is currently handling getting supporter fields, and it looks like it’s hard-coded within the supporter_field_map() function on line 667 of class-gfengage.php. I’m thinking one way I could pass in a custom field to this would be if there was a filter on the $supporter_fields array—this could allow for adding a custom field ID/label at the end of the array.

    Thoughts on whether this would be feasible? Or if there would be another way to include custom fields within the supporter field list? I checked out the Salsa API, and it looks like custom fields follow a similar structure to other default fields:
    https://help.salsalabs.com/hc/en-us/articles/224470107-Engage-API-Supporter-Data#example-request

    Thanks so much for providing this plugin to the community!

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author cornershop

    (@cornershop)

    Thanks for this heads up! We’ve updated a new version of the plugin — and communicated that to you offline 😉 — just posting this update here in case any other users have the same concern.

    Thread Starter designactionria

    (@designactionria)

    Thanks so much!

    I’m not seeing the update as available—did you end up releasing it?

    Plugin Author cornershop

    (@cornershop)

    Ack, sorry! I’m dealing with some plugin confusion. I’ve got this queued up for our devs to look into. Due to client workload, we’re looking at mid-October right now.

    Thread Starter designactionria

    (@designactionria)

    No worries—thanks so much!

    Plugin Author cornershop

    (@cornershop)

    Hi there! We’ve had a chance to look into this finally.

    We believe you’re correct that modifying or extending the supporter field map would be the way to introduce support for custom fields. As no filter currently exists, we’d have to add one … so this is basically a feature request.

    It’s a good one and we plan to do it. There are two routes — one that’s rather crude and simple and would only take like 30 minutes, and one that’s far more robust and intelligent and would likely take 4-6 hours to code and test. We’d like to go the latter route, and that’s queued up in our features list, but (as indicated by response times on this thread) it’s unclear how long that could take.

    If you’d rather not wait, our developers recommend hacking the plugin to make it do what you want while you wait for us to implement something.

    Thread Starter designactionria

    (@designactionria)

    Thanks much for taking a look at this, and adding it to the features list queue!

    If you’d rather not wait, our developers recommend hacking the plugin to make it do what you want while you wait for us to implement something.

    Yes, I may end up trying this as a temporary solution—there’s only a small handful of custom fields in Salsa Engage I’m attempting to populate.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Possible to filter supporter fields?’ is closed to new replies.