Thank you, hadsie, for undertaking the creation of a Registrar API.
I'd like to help with OpenSRS support. While I am only a novice programmer, if all the registrar-specific code is encapsulated in namecheap.inc, I should be able to muddle through it.
OpenSRS provides lot of documentation along with an API Specification for XML.
By any chance, have you published an API reference, along the lines found at drupalcontrib.org?
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | opensrs.tar_.gz | 8.98 KB | ergonlogic |
Comments
Comment #1
ergonlogicJust an update...
Thanks to the generosity of Kieran Lal (Amazon) and Henrique Recidive (Recidive), who shared a D5 module that implemented OpenSRS support (mentioned here), I've been able to create domains and register them with OpenSRS.
That is to say that opensrs_admin_form, opensrs_check_domains and opensrs_create_domain work as expected for all required fields, as well as all the XML encoding/decoding, socket negotiation, etc.
Next steps will include writing renew/sync/update functions, and extending support to optional fields.
Cheers, C
Comment #2
ergonlogicAlso, I notice that, among other TODOs, you have: "Each registrar API should probably be implemented as a module, instead of just a .inc"
Down the road, I'd be happy to reimplement this as a module, and for that matter, I'd be interested in helping to refactor the Registrar API to support this.
Cheers, C
Comment #3
hadsie commentedThat's great @ergonlogic! As I'm sure you can see I've not spent much time on this module since I initially launched it. I do have plans in the very short future that will require me to spend a lot more time on it, so if you have module code for this already I'll be happy to integrate it. Or if you're interested in co-maintaining I can give you commit access.
Cheers,
Scott
Comment #4
ergonlogicI've attached opensrs.inc, and the required ops.dtd. I can't really vouch for the quality of my code, as I'm still pretty new at this. All the sophisticated stuff, I inherited from Recidive (via Amazon). I need to go through and document it and clean up the code and such, but here you go.
I would, in fact, be honoured to co-maintain Registrar API with you. Thank you. I'm sure I'll be good for grunt-work at least. I guess the first step would be applying to a Drupal CVS account, and rereading the maintainer guide. Any other suggestions?
Best regards, Chris
Comment #5
ergonlogicUpon committing a couple minor patches, this code now throws some errors on the 'sync' operation, as I had developed it against the pre-patch code. I'll have to fix this before committing this .inc.
However, OpenSRS recently released a very complete PHP API Toolkit, that I think warrants further investigation. After seeing a demo, I believe inclusion of this code will greatly simplify maintaining OpenSRS compatibility. There remain some questions regarding licensing, but I believe that a "download from here, then upload to your modules/registrar_api/opensrs/ directory" is a viable strategy.
@hadsie: Let me know once you've started actively developing this module again, as I'd like to help, especially with the UC integration, if that's on the docket.
Comment #6
hadsie commentedYeah, I'll let you know. I plan on integrating this with aegir as well as ubercart. Probably still about 2 months away from that though :/
Comment #7
sadist commentedYeah! and working with Ubercart is mandatory for this great module ;)
Comment #8
javdich commentedI was just on openSRS then did a search on drupal.org which brought me here... Is this module presently working with openSRS or is there still more work to be done? I would like to be able to sell and manage domains but do so through my drupal website rather than a openSRS storefront. or perhaps a way to embed the storefront entirely...
Comment #9
hadsie commentedComment #10
migmig commentedHello! I was wondering if hadsie will integrate the ergonlogic's script for opensrs finally :)
Thanks for your work guys!