OVH registrar module broken (again)

[dimitrifrom31]

The OVH registrar module has almost never worked for the past 3 years.

It has been working for few days after v7 release but it is now broken again as it was coded based on the ovh old (reaching EOL) SOAPI.

As a consequence I have been processing domain orders manually which is a real nightmare not to mention I purchased a whmcs owned license then renewed my support & updates addon to update to v7 but also the upgrade service. All that money to end with a manual process and whmcs does not seem to make it a priority so I might wait about 2 years again to get a fix that will get released when OVH will start using a new API.

I have a ticket with whmcs and I submitted a bug report but I felt like posting here because I have been ways too much patient with this now. It should be time to stop trying to offer fancy features and focus instead on getting the core features working properly (I got quite a few bugs on v7 and I see Im not the only one when I read these forums).

 

Thank you for reading.

[WHMCS ChrisD]

Hello Dimitrifrom31,

 

Thank you for your post.

 

We do have a case open to update the OVH Module under case ID CORE-8631 which we will publish to changelog.whmcs.com I can see on the card that the team have been attempting to work with OVH to get a compativle module up and running but we do not have an ETA just yet.

[dimitrifrom31]

Hi Chris,

 

Yes I have been told so however that was also the case in August 2014 and the module was fixed only in October 2016... more than 2 years later, and broke again in November 2016.

The OVH API documentation was released long time ago, the problem is that instead of preparing future changes updating the module, whmcs is only fixing afterwards (with years of delay in that case).

I can't explain why third party modules are updated more frequently than the official ones.