Unsupported scripts and control panel web app for a hosting company
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758
  1. <?PHP
  2. define('SUPPORT_TITLE', 'What do I do if my site isn\'t working?');
  3. define('SUPPORT_BTITLE', 'What do I do if my site isn\'t working?');
  4. if (!defined('LIB_ACCOUNT')) { require('lib/account.php'); }
  5. addDashboardItem('Useful links', 'Site overview', 'sites');
  6. if (!defined('UID')) {
  7. addDashboardItem('Useful links', 'Login', 'login');
  8. }
  9. addDashboardItem('Related articles', 'How to raise a ticket', 'support/010');
  10. addDashboardItem('Related articles', 'HTTP error messages', 'support/012');
  11. addDashboardItem('Related articles', 'What does the status column mean?', 'support/004');
  12. $sbody = <<<SUPPORT
  13. <p>
  14. If you cannot access your website, there are a number of steps you can follow
  15. to try and locate the source of the problem. If you are unable to follow these
  16. steps, please raise a ticket, and a member of the UTD-Hosting staff will
  17. investigate the problem for you.
  18. </p>
  19. <p>
  20. The first thing to determine is what type of problem is occuring. If you see
  21. an error message from the web server (and not your browser) when you try to
  22. access your website, then the cause is probably an invalid setting, or a
  23. problem with a .htaccess file. To further diagnose this problem, please refer
  24. to the <em>HTTP error messages</em> article (linked on the right hand side),
  25. or raise a support ticket.
  26. </p>
  27. <p>
  28. If you can access your site, but you are receiving a UTD-Hosting error page
  29. instead of the site you requested, please raise a ticket and a member of staff
  30. will investigate. If you can access the site, but are receiving a non-HTTP
  31. error message (or are receiving any data that is not expected), it's probable
  32. that the error is due to a badly coded or configured script. If you are unable
  33. to track down the problem, raise the ticket and a member of staff will try to
  34. diagnose it.
  35. </p>
  36. <p>
  37. Finally, if you can not access your site at all, there are a few things that
  38. you can check. On the <em>account overview</em> page, the status column for
  39. the site you are trying to access should say 'OK'. If it displays 'DNS Error'
  40. or another error message, please refer to the <em>What does the status column
  41. mean?</em> article for an explanation of the error and the solution. If this
  42. does not solve the problem, or you are suffering from a problem not covered in
  43. this document, please raise a ticket and we will investigate.
  44. </p>
  45. SUPPORT;
  46. define('SUPPORT_BODY', $sbody);
  47. ?>