harrip Posted March 31, 2016 Share Posted March 31, 2016 (edited) Hi I'm less than impressed that v6.3.0 has been released with a bug that results in the following error on domain renewals: Fatal error: Class 'Carbon' not found in xxx/includes/registrarfunctions.php on line 0 This results in clients getting an error message an they do not know if a domain has or has not been renewed. The expiry date for the domain has to be manually corrected although it appears they are being renewed. The most frustrating part of this is when reported via support I am notified that it is a known bug! Case #CORE-9907 is open with your developers. Why oh why are you releasing software with a known bug of such a critical nature? In the mean time, I recommend users of the latest release manually review every domain renewal to ensure it is correctly processed. Edited March 31, 2016 by harrip 0 Quote Link to comment Share on other sites More sharing options...
splaquet Posted March 31, 2016 Share Posted March 31, 2016 i just found myself with errors on renewal as well. i upgraded to 6.3 yesterday and am now seeing an error. (see screen shots. 2nd one is what happens after 'renew' is clicked) 0 Quote Link to comment Share on other sites More sharing options...
twhiting9275 Posted April 2, 2016 Share Posted April 2, 2016 If you open up a support ticket, there's a hotfix for this which can be given to you. 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted April 2, 2016 Share Posted April 2, 2016 http://forum.whmcs.com/showthread.php?112798-Hot-Fix-CORE-9907-Prevent-fatal-error-after-renewing-domains 0 Quote Link to comment Share on other sites More sharing options...
penguin Posted April 2, 2016 Share Posted April 2, 2016 I think it would be helpful if hotfixes are announced via e-mail in the same manner as releases - at least this shows some proactivity and highlights an issue to users who may not be checking the forum each day. The quicker you notify someone, the less impact to their business from it. 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted April 2, 2016 Share Posted April 2, 2016 I think it would be helpful if hotfixes are announced via e-mail in the same manner as releases - at least this shows some proactivity and highlights an issue to users who may not be checking the forum each day. The quicker you notify someone, the less impact to their business from it. I wouldn't argue with that... we're now in the situation where they won't have updated (I assume as it was their policy not to) the main v6.3 zip release with the fix - so a new user wouldn't necessarily know there is an issue with domain renewal. what WHMCS used to do years ago, was have all the hotfixes in one place, but for some reason they stopped doing that when they launched v6... though that seem to have started doing it again with this v6.3 hotfix. http://docs.whmcs.com/HotFixes I suppose if you could create a RSS feed for that page, you could use IFTTT to notify you of an update. i've got an IFTTT recipe linked to the WHMCS security blog and I get an email from IFTTT when it's updated... i'll usually get an official security advisory email from WHMCS upto 24 hours after that. luckily, I was busy when v6.3 launched and didn't install it... plus it's usually wise to hold back on installing WHMCS major releases as they nearly always tend to have bugs that should have been discovered during testing, and v6.3.1 will inevitably be released within a fortnight of v6.3.0. 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.