WHMCS CEO Matt Posted November 22, 2013 WHMCS CEO Share Posted November 22, 2013 This has been confirmed to be an error in the latest release and has been assigned a case number of 3670 for tracking purposes. In the meantime until a fix can be made available, WHOIS Lookups can still be performed by copying the domain and pasting it manually into the WHOIS Lookup tool which can be accessed via the Utilities menu. Sorry for any inconvenience this may cause. Matt Link to comment Share on other sites More sharing options...
pierre Posted November 23, 2013 Share Posted November 23, 2013 Ok, keeping an eye on this thread, same exact error even though I did everything we were instructed. Waiting on fix. Edit: by the way, the results from whois.php are very incomplete for us, and miss crucial owner details. Link to comment Share on other sites More sharing options...
andy40 Posted November 23, 2013 Share Posted November 23, 2013 Just updated one of ours and same problem, so will leave the others for now until a fix is out. Link to comment Share on other sites More sharing options...
greghl Posted November 23, 2013 Share Posted November 23, 2013 Just updated one of ours and same problem, so will leave the others for now until a fix is out. let me see if I understand this... yes, a whois script breaks - but you get a fix to zero-day security issues - and while the whois script is a *HUGE* pain in the rear, you would rather have an insecure and potentially hackable WHMCS installation than lose your whois? fwiw - this whois is a MASSIVE pain - I use it so many times a day, that this not having the facility infuriates me enormously - but would I rather recover from a destroyed install? Heck no.... I think you're nuts for not upgrading, even with the whois issue. @mattofwhmcs - that tracking ID you posted - can we track these bugs or is it for internal use only? This is a nightmare not having that whois link. Link to comment Share on other sites More sharing options...
gbh Posted November 23, 2013 Share Posted November 23, 2013 Subscribing as I have the same issue Link to comment Share on other sites More sharing options...
rkatz0 Posted November 23, 2013 Share Posted November 23, 2013 Subscribing as I have the same issue ditto support is saying the invalid token is template_c but it is not, of course we already cleared templates and refreshed browser cache, now Matt says there is a bug and it's being fixed and that is great, and some guy wants his system hacked rather then lose whois capability, wonderful! All this to get the required length to post to track this thread! Link to comment Share on other sites More sharing options...
pegazhosting Posted November 24, 2013 Share Posted November 24, 2013 Security is important, but WHOIS is important too They destroyed Twitter feed on home page before 6 months, i got answer: The issue with Twitter is due to an update in the Twitter API, the unauthenticated v1.0 API is now discontinued. We've opened case #2776 with our developers in order to have this resolved for future releases. Unfortunately, I cannot provide an estimated time for completion for this. However, once we resolve cases and push features they are available at our change log, here: http://changelog.whmcs.com/ Link to comment Share on other sites More sharing options...
rdavis Posted November 24, 2013 Share Posted November 24, 2013 Hello, After installing patch v5212 to v5213 the ability to use the 'Whois" from the clients profile stoped working and says "Invalid Token", so we uploaded the previous version in v5212 [whois.php] size 7,828 and now the whois works once again. Link to comment Share on other sites More sharing options...
lance Posted November 24, 2013 Share Posted November 24, 2013 (edited) seems we cant get to download the files for 5.2.12 from the client area to get said file, only allows download of the latest release by the looks of it. **ignore** have it in a backup..... Edited November 24, 2013 by lance Link to comment Share on other sites More sharing options...
ivaserver Posted November 25, 2013 Share Posted November 25, 2013 trouble is the new whois.php file might be part of the security fix so by installing the old version we may open up a vulnerability. Link to comment Share on other sites More sharing options...
Infopro Posted November 25, 2013 Share Posted November 25, 2013 This has been confirmed to be an error in the latest release and has been assigned a case number of 3670 for tracking purposes. In the meantime until a fix can be made available, WHOIS Lookups can still be performed by copying the domain and pasting it manually into the WHOIS Lookup tool which can be accessed via the Utilities menu. Sorry for any inconvenience this may cause. Matt Merged several new threads into this one, also bumping Matt's post to be sure it's been seen. Link to comment Share on other sites More sharing options...
WHMCS Nate Posted November 27, 2013 Share Posted November 27, 2013 Hello, This has been corrected in 5.2.14. Please note it does include a template change, so you will need to clear templates_c after upgrade to get this corrected. Link to comment Share on other sites More sharing options...
Recommended Posts