KevinR

The issue ended up being that langupdate.php was not deleted during update. However, when I checked, that file was not there, and the issue persisted. I finally got a response to my ticket about this, and once I gave them credentials they were able to quickly fix it. Though the fix applied, didn't make sense as I had already done their instructions. So I am back online now, and lost out on a summer sale advertisement 100%.

I agree, this update caused issues on a wide variety of hosts. More testing needs to be done, or they need to have a LTS version of WHMCS for those who need a stable setup.

I'm having a similar issue https://forum.whmcs.com/showthread.php?129043-v7-2-1-Errors/page2 , support took 3 days to reply, and their solution was to delete lang/langupdate.php Which didn't exist already, so that did not help my issue. My client area has been down for 5 days. Most of the admin area however works fine.

I am on a CentOS 6 VPS, and even with PHP Errors Off(as it always has been) I get the same Oops page error. Is there no fix for this? My business has been down for 5 days.

Anyone looking into this? Business has been offline for the entire weekend and no response. I can't roll back that I know of, as backups don't have all the new clients, payments, invoices, etc. I do have full backups, but they are now 4 days old.

Same issue here, still working on fixing it, I'm out of ideas though and waiting on a ticket response. The Admin area works fine, so I went a day thinking the upgrade went fine, when in reality my entire client area was down and caused a massive loss due to a weekend promotion. I will now be checking every client function manually each update, even minor ones, from now on. More work, but seems to be a common issue with WHMCS. The hotfix did not help. Also, isn't this against their own instructions? ---- Special Note About Error Reporting Level We recommend that you do _not_ change the $error_reporting_level within configuration.php or the corresponding PHP ini error_reporting directive at the environment level, during normal production or staging operation. Specifying a more sensitive $error_reporting_level, which observes non-critical warnings and notices, may result in pre-mature exit and prevent normal production behavior from functioning properly.

This post? https://bitbucket.org/Doctor_McKay/blockchain.info-whmcs-payment-gateway/issue/5/bitcoin-payment-gateway-not-working#comment-9132662 Or where do you download the new package?

Same here, would love an update, can tip some BTC

I'm interested in this as well.

Would there be a way to use the "free trial" feature from Paypal, where they would pay a pro-rated/full amount today, then the subscription starts billing when the "free trial" time runs out? WHMCS would change the free trial days amount at each cron for example so it always syncs up. Also a cancel paypal subscription from within WHMCS for clients and admins to use would be great.

I'm also interested in this triphost.

Thanks, I'm trying this now. Should any other files in custom templates be updated from 5.0.3 that are not listed here under template changes? http://docs.whmcs.com/Version_5.0_Release_Notes#Version_5.0.3

Is everyone still having this problem?

I'm still having this exact issue. Clients who had their card stored in the vault before the update work fine. However new clients are not able to use the gateway at all. I have not been able to take a single new client with Quantum Vault via WHMCS since 5.1.2 was released.

Has anyone used this with 5.1.2 ? Anything I should know? Great module, thank you for donating your time and effort for this free module.