Jump to content

HostSlayer

Member
  • Posts

    3
  • Joined

  • Last visited

About HostSlayer

HostSlayer's Achievements

Junior Member

Junior Member (1/3)

0

Reputation

  1. I forgot to keep everyone updated. So this hot fix did work for me. But i mean i think its WHMCS job to assure they have the correct files out there before they decide to upgrade their system.
  2. The first error I want to post is the cron jobs. I had it set to 5minutes before, and after upgrading to v7.2.1 I get this error ; <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Critical Error</title> <style> body { margin: 30px 40px; background-color: #f6f6f6; } .error-container { padding: 50px 40px; font-family: "Helvetica Neue",Helvetica,Arial,sans-serif; font-size: 14px; } h1 { margin: 0; font-size: 48px; font-weight: 400; } h2 { margin: 0; font-size: 26px; font-weight: 300; } a { color: #336699; } p.back-to-home { margin-top: 30px; } p.debug{ padding: 20px 0px; font-family: "Courier New", Courier, monospace, serif; font-size: 14px; } </style> </head> <body> <div class="error-container"><h1>Critical Error</h1><p>Undefined index: SCRIPT_NAME</p></div> </body> </html> The 2nd error is this. I made a fresh new installation and then get the following error when visiting my WHMCS Oops! Something went wrong and we couldn't process your request. Please go back to the previous page and try again.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated