greghl Posted July 27, 2015 Share Posted July 27, 2015 Since upgrading to v6.01 none of our whois queries for anything but the basic TLDs seems to work - I've checked that our whoisservers.php is intact - did they move it in v6? Most perplexed... Yes, I did open a helpdesk ticket - nothing back from WHMCS support as yet. 0 Quote Link to comment Share on other sites More sharing options...
greghl Posted July 27, 2015 Author Share Posted July 27, 2015 apparently my whoisservers.php was overwritten without me noticing - that'll teach me to grep -l bio instead of '^.bio|' when checking if my newTLDs were overwritten or not. When oh when are they going to have core whoisservers.php and our custom-whoisservers.php where our custom ones don't get overwritten?!?! 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted July 28, 2015 Share Posted July 28, 2015 (edited) Since upgrading to v6.01 none of our whois queries for anything but the basic TLDs seems to work - I've checked that our whoisservers.php is intact - did they move it in v6? it's still in the same old place - includes/whoisservers.php Edited July 28, 2015 by brian! 0 Quote Link to comment Share on other sites More sharing options...
greghl Posted July 28, 2015 Author Share Posted July 28, 2015 Yes, my bad - because I was using grep -l .bio whoisservers.php it was returning positive because of .bio.br - so I was erroneously concluding that my whoisservers.php file was my custom version. I still think they should recode this system - there needs to be a whoisservers-core.php - which we don't alter and a whoisservers-custom.php If the custom version has a different whois server for one of the core entries, then that custom version is used - all our custom newTLDs would go into whoisservers-custom.php and this file would NOT get overwritten on full or incremental update. Better still - in the admin whois tools, it could report whether the whois server being used is core or custom so we can know which file is in play. I believe this fairly small and easy to code enhancement would be a big improvement that would save a lot of time for a lot of users. 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted July 28, 2015 Share Posted July 28, 2015 seems a little like overkill to me - I just delete the WHMCS version and use my own whoisservers file... and then back it up before I do an upgrade. 0 Quote Link to comment Share on other sites More sharing options...
greghl Posted July 28, 2015 Author Share Posted July 28, 2015 well how are you going to do that when they implement the auto-update which features request site says is 'in progress'? 0 Quote Link to comment Share on other sites More sharing options...
Alex - Arvixe Posted July 28, 2015 Share Posted July 28, 2015 well how are you going to do that when they implement the auto-update which features request site says is 'in progress'? Don't use the auto update feature... when / if it arrives. 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted July 28, 2015 Share Posted July 28, 2015 well how are you going to do that when they implement the auto-update which features request site says is 'in progress'? well I have three responses to that... 1. the title "In Progress" is pretty meaningless - the cPanel integration was in progress for years, so I don't believe for one second this is imminent... in fact, I think I read WHMCS John say the same in one of his discus posts recently... so it might indeed be on the cards, but I doubt it will be this year. 2. I do not believe the auto-update facility will be compulsory, e.g the user can disable it if they wish - so if that's the case, your question is irrelevant; if it's not, then there will be a lot of users complaining about being forced to use it. 3. I have a number of licenses, but the one where the whoisservers file is of vital importance, is currently using a very-highly customised domainchecker and still runs on v5.3.14 - it would work on Six now, but wouldn't long-term - so I will eventually port it to v6 (probably v6.1), rewriting nearly all the code to use its own database tables and enhance it further with new features... if as part of that process, it needs to use my custom whoisservers.php rather than a default one, then i'll simply code it to do so. so in brief - it's not imminent; it's unlikely to be compulsory; and I could get around it anyway. 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.