I'm using the latest version of the module, have input my API keys correctly, and I still cannot initialize the client. Is there a step I am missing?

Comments

blasthaus’s picture

blasthaus commented

There is a roadmap here to get everything working with the latest v.2 of Recurly's API, but at the moment, you'll still have to use the v.1 API to get this module to function. @quicksketch has jumped on this project to help and there seems to finally be some momentum. In addition, I've rewritten the module to work with v.2 and it's in a sandbox here, but it's going to be ultimately up to Ryan and Nate how much of that code makes it in here.

threadsniper’s picture

threadsniper commented

Is there any way to implement the Sandbox into a production site without many issues? Could you familiarize me with that process? Sorry for the incessant questions. We are on a tight deadline and found out at a late hour that recurring billing in Drupal was tough stuff! Any help would be appreciated.

threadsniper’s picture

threadsniper commented

I have downloaded and installed the v.1 API from Recurly's Github repository, but I receive the same message. Any help, again, is appreciated.

blasthaus’s picture

blasthaus commented

Well the Sandbox version is very much intended to try and steer this Recurly module into v2.0 and was necessary for me in the course of developing a new module that integrates Recurly with Drupal Commerce. So while it may not be quite ready for prime time, it is working for me. In terms of integration, the only way I see that you can use this module in it's current state is to use the hosting options, so you have a simple node with a "product description" lets say, and on that node you link directly to a page on Recurly where a user can subscribe. You can also use the Recurly.js and integrate javascript to put the forms on your Drupal site. Anyway, even using this sandbox module, you still have some work to do as it provides no commerce solution. I'm close to releasing the commerce_recurly module which you may want to take a look at as soon as I finally get it up.

blasthaus’s picture

blasthaus commented

My bad, it looks like the latest dev version uses v.2 of Recurly API. So switch back to that and if you still have problems, make sure you have libraries module installed and that you have the path sites/all/libraries/recurly/lib/recurly.php and that you have the right permissions/ownership on that folder

threadsniper’s picture

threadsniper commented

Will give that a shot Blasthaus. Thanks for the continued help!

threadsniper’s picture

threadsniper commented
Status: Active » Fixed

Okay. I've gotten this working. Great! Now, to find some documentation on setting this up to create a premium content subscription!

quicksketch’s picture

quicksketch
he/him
commented

Yeah @threadsniper: Your best bet right now is to hang out for a week or so and check back in. I'm working full time right now on ramping up this module to get it production ready. Right now the functionality is ridiculously limited. It basically just keeps records in your database tables and links off to Recurly to manage accounts. There's not even ability to sign up for an account from Drupal yet.

threadsniper’s picture

threadsniper commented

Is there any way to use Rules to assign user roles if I link out to hosted pages? Such as "If user returns to X URL, assign role?" This would need to be a quick fix (this site is set to launch on Monday) and a temporary one, but I'll need to figure out some form of automation so I'm not waiting on notification from Recurly and needing to manually assign those roles.

threadsniper’s picture

threadsniper commented

And thanks for the hard work on this. I really do enjoy Recurly's service and can't wait to see it integrated fully!

Status: Fixed » Closed (fixed)

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