-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An error has occured #37
Comments
Anyone? |
yes |
Any errors in your webserver logs? |
Hello, i get the Same error. `[15-Feb-2016 07:49:34 UTC] PHP Notice: Undefined variable: allCheckID in C:\xampp\htdocs\status\build\statuspage\statusPage.php on line 103 [15-Feb-2016 07:49:34 UTC] PHP Notice: Undefined variable: allCheckInfo in C:\xampp\htdocs\status\build\statuspage\statusPage.php on line 41 I am using : |
The variables are missing (undefined) if there are no monitors/accounts connected and therefore no loops accessed. I've added the missing variable definitions in my PR #38 |
Here is another error I got from the check.php: Warning: Invalid argument supplied for foreach() in /web/statuspage/statusPage.php on line 23 How do I fix this? |
@timhal15 do you use the contents from Have you checked out my fix ( Your warning from L49 occures when the variable contains no monitors. This is already fixed in the build/statuspage/statusPage.php#L51 |
@lduer yes I use the file you fixed, the unhappy face no longer exist. But still nothing shows up.... $.ajax.success @ statuspage.min.js:41 |
could you please paste the response you get from the |
I've tried with thx |
Quickfix: (works for me) private function getChecksJson($action)
} |
work very fine, thank You
|
@Zillionx @Chris6284 Thanks |
where Replace getChecksJson() and Replace API-KEY with your own Api-Key ? |
@wang259797 You gotta to get your own API-KEY from uptimebot, which will generate one for you in the dashboard. |
How do you restrict to say 3 monitors ? (edit - found answers here #27) |
I am getting the error below:
If i run the API call manually it all works fine - but the public page always returns this error :(
this is on a LNMP, I use Debian
The text was updated successfully, but these errors were encountered: