記得前段時(shí)間因?yàn)樯?jí)WHMCS導(dǎo)致錯(cuò)誤，還專門(mén)寫(xiě)了一篇文章：WHMCS 7.1.1 升級(jí)經(jīng)驗(yàn)總結(jié)?，這篇文章詳細(xì)記錄了WHMCS從6.*升級(jí)到7.1.1的痛苦經(jīng)歷，簡(jiǎn)直苦不堪言，經(jīng)過(guò)了幾個(gè)小時(shí)的折騰最后總算升級(jí)上去了，但是留下了一個(gè)致命的bug，發(fā)現(xiàn)前臺(tái)eNom域名的DNS管理界面始終多一條包含數(shù)字的莫名其妙的記錄如下：
提交工單給WHMCS技術(shù)客服以后，給到的答復(fù)如下：
Hi Xiaoge,
Thanks for contacting WHMCS. I’ve been able to replicate this issue on my end as well, it appears eNom have made some kind of change to their API. As such I have opened case #CORE-10857 is open with our developers in order to have this reviewed for future releases. Whilst I cannot provide an estimated time for completion for this, once we resolve cases and push features they are available at our change log, here:
http://changelog.whmcs.com/
I apologize for the inconvenience, and appreciate your patience as we work to resolve this.
Thanks again for taking the time to report your findings. We welcome such reports at http://bugs.whmcs.com/
Best Regards,
—
John Kipling
Technical Support Supervisor
WHMCS, Ltd.
http://whmcs.com
看完發(fā)現(xiàn)全是套路，簡(jiǎn)而言之就是WHMCS官方承認(rèn)這個(gè)是一個(gè)BUG，但是就是不給你解決，只能等下一次更新，而且下一次更新是否解決也不給保證，于是最終選擇了妥協(xié)，多一條帶數(shù)字的記錄反正也不影響功能，忍了吧，滿懷希望的等下一次更新，于是幾天后終于等來(lái)了7.1.2的更新，基于對(duì)WHMCS的信任，毫不懷疑的點(diǎn)擊了升級(jí)，升級(jí)過(guò)程很流暢，升級(jí)完成，滿懷希望的打開(kāi)前臺(tái)發(fā)現(xiàn)，雖然那條數(shù)字的記錄沒(méi)了，但是這回更坑爹了，每個(gè)域名無(wú)論你原來(lái)有多少條解析記錄，通通都只剩余一條A記錄，而且無(wú)法新增，這樣以后，基本對(duì)于客戶來(lái)說(shuō)域名解析記錄的功能就廢了，壓根無(wú)法工作了。
于是又一次提交工單給WHMCS，這次給予的回復(fù)如下：
Hello Xiaoge,
Thank you for that.
I have enabled module debugging temporarily, and then replicated the issue. You can review the logged data via your Admin Area at Utilities > Logs > Module Debug Log .
Here, you can see that we’re using the gethosts function provided by eNom’s API to return the host records for the domain name. You can review eNom’s documentation for this function at https://www.enom.com/api/API%20topics/api_GetHosts.htm
Here is the API your WHMCS installation is sending to eNom:
uid=********&pw=****************&tld=org&sld=eastdesign&command=gethosts&ResponseType=XML&Engine=WHMCS7.1&
This bit is added to the end of the URL used to connect to eNom’s services. You’ll notice that this matches the format provided by eNom’s documentation. Here is the sample they provide detailing how to build the URL:
command=nameofcommand&uid=yourloginid&pw=yourpassword
¶mname=paramvalue&nextparamname=nextparamvalue
Now, here is the API response that eNom is providing:
<?xml version="1.0" encoding="utf-8"?><interface-response><host><name><![CDATA[www]]></name><type>A</type><address><![CDATA[45.33.45.201]]></address><hostid>369201857</hostid></host><host><name><![CDATA[@]]></name><type>A</type><address><![CDATA[45.33.45.201]]></address><hostid>369201858</hostid></host><DomainServices><EmailForwarding></EmailForwarding><HostRecords></HostRecords></DomainServices><DomainLimits><HostsRecordLimit>50</HostsRecordLimit><MailForwardLimit>100</MailForwardLimit></DomainLimits><HostRecordCount>2</HostRecordCount><MxRecordCount>5</MxRecordCount><Command>GETHOSTS</Command><APIType>API.NET</APIType><Language>eng</Language><ErrCount>0</ErrCount><ResponseCount>0</ResponseCount><MinPeriod>1</MinPeriod><MaxPeriod>10</MaxPeriod><Server>sjl0vwapi12</Server><Site>eNom</Site><IsLockable /><IsRealTimeTLD /><TimeDifference>+0.00</TimeDifference><ExecTime>0.073</ExecTime><Done>true</Done><TrackingKey>34810718-7f61-4c84-ac2b-e3483b61b934</TrackingKey><RequestDateTime>2/23/2017 11:12:28 AM</RequestDateTime><debug /></interface-response>
Here you can see that eNom is furnishing two A records; one for **www*, and one without a name value.
If you feel the information being returned by eNom is not correct, then you will want to contact them so that they can investigate why their API is returning this data.
If they advise of any configuration changes that need to be made to WHMCS itself, then please let us know.
Best regards,
—
Nathan Lierbo
Technical Analyst I
WHMCS, Ltd.
http://whmcs.com
通篇看下來(lái)，這次沒(méi)有用套話敷衍我，確實(shí)告知了我如何通過(guò)WHMCS自帶的module工具進(jìn)行檢測(cè)BUG，然后最終的結(jié)果就是eNom返回的記錄正確，但是前臺(tái)顯示不對(duì)我們也不知道什么原因，最好去問(wèn)問(wèn)eNom官方，我勒個(gè)去，又把皮球踢回給了eNom，至此我對(duì)WHMCS官方的技術(shù)客服非常的失望，于是回復(fù)了如下四條的投訴ticket：
I was suppose to hope this 7.1.1 to 7.1.2 will fix that eNom domain DNS management bug, but after I spent so many hours I got nothing but disappointment.
I have no choice but downgrade to WHMCS 7.1.1, although there will be one more strange number record in DNS management as I had already reported to you in my last ticket, but it was working, I am a little bit Disappointed to your tech support, it didn’t help us a lot,hope you can improve support service.
You mean that eNom has returned the right records, but my whmcs front end can’t show them correctly?
Your reply was still not helping, according to your experience, could you give me some suggestion about this issue, I mean what will cause this issue? I had try to use the new theme and still not working.
正是以上四條不滿的投訴ticket換來(lái)了WHMCS官方足夠的重視，直接提供了一個(gè)緊急修復(fù)補(bǔ)丁過(guò)來(lái)如下：
Hello Xiaoge,
I’m pleased to advise that we have an immediate fix available and I am attaching it to my reply. Please unzip this attachment and place the files in your WHMCS directory. If asked to overwrite any files please do. For reference we’ve assigned this particular issue within WHMCS a case number, CORE-10925.
When the hotfix is deployed, please check if eNom now displays all the values in client area – I would appreciate it if you could confirm this solved the issue on your install. If you have any other issues or questions please don’t hesitate to let me know.
Best regards,
—
Marcus Allen
Technical Analyst I
WHMCS, Ltd.
http://whmcs.com
這個(gè)壓縮包分享給大家：
[download id=”11752″]
至此此次升級(jí)總算圓滿結(jié)束，得出一個(gè)結(jié)論就是，發(fā)現(xiàn)問(wèn)題一定有有理有據(jù)的去投訴反饋，否則坐等官方來(lái)發(fā)現(xiàn)和修復(fù)，不知道要延遲多久的時(shí)間。