Lawrence Posted January 10, 2011 Share Posted January 10, 2011 Ever since upgrading to 4.4.1, the Registrar Lock setting is unchecked on all domains. This has been confirmed with eNom. Not sure about other registrars as we do not deal with others that support Registrar Locking. The locking appears to work, just the check box that's broken. 0 Quote Link to comment Share on other sites More sharing options...
WHMCS CEO Matt Posted January 10, 2011 WHMCS CEO Share Posted January 10, 2011 This is an Enom issue - not V4.4. The API response seemed to change on Friday for the locking status from "RegLock" to "reg-lock". Currently waiting on news from them as to why and if it will be changed back (their devs don't do weekends). Matt 0 Quote Link to comment Share on other sites More sharing options...
hiddenko Posted January 10, 2011 Share Posted January 10, 2011 Hello i use namecheap and got same issue 0 Quote Link to comment Share on other sites More sharing options...
Lawrence Posted January 11, 2011 Author Share Posted January 11, 2011 Thanks Matt, Wonder who made that mistake LOL. I am looking at version 6.4 of their API documentation (dated 11/30/2010) and it mentions nothing of a change. In fact, the GetRegLock command returns a parameter called RegLock which is either set to 1 or 0. I guess someone f*cked up. Hiddenko, that is because NameCheap is an eNom reseller, despite any claims to the contrary. 0 Quote Link to comment Share on other sites More sharing options...
othellotech Posted January 11, 2011 Share Posted January 11, 2011 It goes a little deeper than just their API response change - even using their interface over the weekend, unlocking domains for transfer ddnt get sent to Verisign, but *did* change the status in their web interface, so it said unlocked even though it was locked ! matt - are you releasing a temp-patch for all the 4.x branch of WHMCS ? 0 Quote Link to comment Share on other sites More sharing options...
webauthor Posted January 11, 2011 Share Posted January 11, 2011 Bump - Any word as to when this will be fixed? Should we call Enom or is this a WHMCS bug since it's happening with other registrars? Thanks 0 Quote Link to comment Share on other sites More sharing options...
Lawrence Posted January 11, 2011 Author Share Posted January 11, 2011 Bump - Any word as to when this will be fixed? Should we call Enom or is this a WHMCS bug since it's happening with other registrars? Thanks It's purely an eNom bug. They changed the API result without any notice (we have access to their API documents and can confirm this). The only other "registrar" mentioned is NameCheap, who are merely just an eNom reseller. 0 Quote Link to comment Share on other sites More sharing options...
Lawrence Posted January 11, 2011 Author Share Posted January 11, 2011 It goes a little deeper than just their API response change - even using their interface over the weekend, unlocking domains for transfer ddnt get sent to Verisign, but *did* change the status in their web interface, so it said unlocked even though it was locked ! matt - are you releasing a temp-patch for all the 4.x branch of WHMCS ? I would doubt it. It would only serve to cause confusion for something that should be easily fixed by eNom themselves. 0 Quote Link to comment Share on other sites More sharing options...
othellotech Posted January 12, 2011 Share Posted January 12, 2011 I would doubt it. It would only serve to cause confusion for something that should be easily fixed by eNom themselves. Having waited 5+ months for them to fix earlier issues in their API, I think having a patched WHMCS module will be quicker 0 Quote Link to comment Share on other sites More sharing options...
WHMCS CEO Matt Posted January 12, 2011 WHMCS CEO Share Posted January 12, 2011 We had considered releasing a patch but like larwilliams said, thought it would cause confusion and it would only be a workaround rather than a fix. We did however expect Enom given the severity of this issue and the amount of people it must be affecting to react a bit quicker as we first reported it to Enom last Saturday and it's now almost Thursday the next week without anything more than a "we'll escalate it to our developers team to investigate" despite daily requests for an update. So, I guess if it's not fixed by the end of the day tomorrow then we'll look at issueing a workaround to be used in the interim. Matt [uPDATE: Enom have advised this should now be fixed as of 11pm GMT Friday] 0 Quote Link to comment Share on other sites More sharing options...
joelie Posted September 21, 2011 Share Posted September 21, 2011 I am using v 4.4.2 and this is still happening. Can it be easily patched instead of waiting for enom? 0 Quote Link to comment Share on other sites More sharing options...
WHMCS CEO Matt Posted September 21, 2011 WHMCS CEO Share Posted September 21, 2011 Not even Enom are this slow! It's a new issue in their API that is meaning registrar lock returns as unavailable for all domains currently. Doesn't matter what version you're using it will be a problem. They are currently "investigating" so as soon as we know more we'll pass it on. Matt 0 Quote Link to comment Share on other sites More sharing options...
billchalmers Posted September 22, 2011 Share Posted September 22, 2011 I'm using 4.4.2 and my registrar lock button is missing on the admin side as well as the client side, is this the same issue? 0 Quote Link to comment Share on other sites More sharing options...
pjs32 Posted September 22, 2011 Share Posted September 22, 2011 I'm using 4.4.2 and my registrar lock button is missing on the admin side as well as the client side, is this the same issue? Mine is the same,so it must be. 0 Quote Link to comment Share on other sites More sharing options...
9DollarDomains Posted September 26, 2011 Share Posted September 26, 2011 Bump - we just noticed the same, so way for Domain owners from their client side, or for us from the Admin side to be able to lock/unlock domains. 0 Quote Link to comment Share on other sites More sharing options...
WHMCS CEO Matt Posted September 27, 2011 WHMCS CEO Share Posted September 27, 2011 We've just had a response from Enom that they will be pushing an update through to their live servers on Wednesday of this week that should resolve the API problem. Believe me we have let them know how unacceptable the time it's taken them to come up with a solution for this is, but fingers crossed that update on Wednesday will resolve it for everyone. Matt 0 Quote Link to comment Share on other sites More sharing options...
joelie Posted September 27, 2011 Share Posted September 27, 2011 Thanks for the update Matt! Here's hoping it's resolved on Wednesday 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Mark Posted October 12, 2011 Share Posted October 12, 2011 This issue has been resolved, sorry for the late reply:lol: 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.