We’re really excited to see all of the collaboration and enthusiasm around this Drupal project. This work has the potential to benefit many Convio clients and partners, and we hope to see more contributions and projects stem off this project in the near future.

As discussed in our meeting last week with the maintainers of this project, and to help this effort takeoff, Convio is attaching development snapshot module code and documentation of a module it has prototyped to this comment (quick note: our support team provides support for Convio Open APIs for our customers and certified partners – all contributions to Drupal.org including this one are done in the spirit of community development and are outside of the scope of what our tech support team will support – the maintainers of this project provide support for this module and Mike and I are happy to work with them).

This code uses Convio Open APIs to provide:

  • Single sign-on between Drupal 6 and Convio Constituent 360
  • Personalization and conditional content on Drupal pages
  • Convio Source Code tracking

Please see documentation in the attached tar.gz file for additional details.

Our hope is that this code, and corresponding documentation, will be of value and can be leveraged by contributors to this and related projects so that more people can build great Drupal sites on top of Convio.

Regards,

Kevin Suer

Michael Pih

Convio

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

convio’s picture

FileSize
95.73 KB

Attached is an updated development snapshot for our module code. This new tar includes improved installation instructions and an update to the name and description of the module (as it appears on your module administration page in Drupal).

Kevin Suer
Convio

convio’s picture

FileSize
95.73 KB

Attached is the latest patch for Convio's development snapshot module.

Release note:
- Fixed the getGroups() and getInterests() API calls.

Regards,

Kevin Suer
Convio

mfer’s picture

Are there any updates to the codebase?

BTMash’s picture

@mfer, I just responded to this in another issue. Aside from talks last year, there hasn't been much in the way of updates due to a lack of time (mainly from me) which I am looking to rectify this summer.

mfer’s picture

@BTMash, is work going to happen on the codebase here or elsewhere? I've started to clean up what's here and wondering if this is the most appropriate codebase to start from. I can push it to git (already started with this as a clean git codebase). To help contribute, is there a better setup?

BTMash’s picture

@mfer, by 'here' do you mean the codebase posted by convio or the codebase that is currently in git.

mfer’s picture

@BTMash I mean the codebase posted by convio. Or, is that a bad place to start?

BTMash’s picture

@mfer Ah, ok. Basically, the initial plans were that the convio api module would act as the glue piece which would do the actual communication with a convio server (based off the parameters, request type, url. Then there would be another project which worked using the api module to actually implement the actual convio api. The convio_user module that was included in the master codebase on git only served to show how to use the api as an example.

It would still be ideal to have one module that handles that aspect of it and then have others built out but I'm open to other ideas as well.

cluther’s picture

I guess this project stalled when we couldn't coordinate the merging of three separate versions a solution: a sample developed by Michael Pih at Convio, a version developed by Ashok, and a version developed by myself and Kevin Kaland (wizonesolutions) for an client engagement last year.

With the hope of kickstarting the project again I've placed a copy of my team's Convio_API module up on GITHUB at https://github.com/chluther/convio_api . This module provides SSO and personalization features.

We also developed features that allowed integration between Drupal and Convio's e-Commerce store, however we need extract parts from the client's custom module so that it can stand on it's own. Once that is done I'll post it as a new project under GITHUB.

Best Regards,

Chris Luther

laryn’s picture

Thanks, I was trying to track down where things stood on this module. I'm assuming this is all for Drupal 6 -- am I right?

cluther’s picture

Yes... Drupal 6 only. But I'd be anxious to work with someone to help develop a D7 version.

Chris Luther

cluther’s picture

I've since move the code from GITHUB to a Drupal Sandbox at http://drupal.org/sandbox/cluther/1275364

BTMash’s picture

I had not seen this issue until now. I have granted you access to commit to the codebase so you are free to commit code if you wish. Again, my apologies for not seeing this issue sooner and that you were not given access to commit to the codebase.

BTMash’s picture

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

Closing.