AffordableDomainsCanada Posted January 15, 2017 Share Posted January 15, 2017 I was trying to access the admin area for the Security Questions, and I was getting a blank white screen so I turned on error reporting etc.. and went back and was getting a error with a file from the /vendor/whmcs/whmcs-foundation/ folder so I re uploaded all the files and now I am geting the update error message. Down for Maintenance (Err 2) An upgrade is currently in progress... Please come back soon... How do I get the site to load and not display this upgrade in progress message ? Ticket #HER-564998 opened, just seeing if I can get faster support in the community forums.. 0 Quote Link to comment Share on other sites More sharing options...
WHMCS ChrisD Posted January 15, 2017 Share Posted January 15, 2017 Hey Jason, Sounds like theres a version conflict, Just grabbed and replied to your ticket 0 Quote Link to comment Share on other sites More sharing options...
AffordableDomainsCanada Posted January 15, 2017 Author Share Posted January 15, 2017 Downloaded a fresh copy of 7.1.1 and uploaded all the files and now I am having a new error show. Parse error: syntax error, unexpected '"', expecting identifier (T_STRING) or variable (T_VARIABLE) or number (T_NUM_STRING) in /home/jafforda/public_html/vendor/whmcs/whmcs-foundation/lib/License.php on line 0 Fatal error: Exception thrown without a stack frame in Unknown on line 0 0 Quote Link to comment Share on other sites More sharing options...
AffordableDomainsCanada Posted January 15, 2017 Author Share Posted January 15, 2017 After some further trouble shooting with Chris, it appears to have been a hook issue. I have since resolved the issue by fixing the recent hook. 0 Quote Link to comment Share on other sites More sharing options...
twhiting9275 Posted January 16, 2017 Share Posted January 16, 2017 Downloaded a fresh copy of 7.1.1 and uploaded all the files and now I am having a new error show. These errors are really, really annoying. It used to be that the proper error was shown, so the developer could identify what needed to be fixed. Now, you've got some generic garbage here.. Can we PLEASE have the old errors back, or at least show the proper error!! Sorry, not trying to hijack a thread, but this is just beyond insane. Run into this quite a few times since 7.1 and it's incredibly time consuming 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.