-
-
Notifications
You must be signed in to change notification settings - Fork 566
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
Fix api.php?status ( replicate #2031 and pi-hole/pi-hole#4485) #2052
Conversation
(#2031 and pi-hole/pi-hole#4485) Signed-off-by: rdwebdesign <[email protected]>
This pull request has been mentioned on Pi-hole Userspace. There might be relevant details there: |
Signed-off-by: rdwebdesign <[email protected]>
Signed-off-by: rdwebdesign <[email protected]>
Signed-off-by: rdwebdesign <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tried it locally and it worked as expected.
http://pi.hole/admin/api.php?status
returned the correct status now.
* Replicating changes made by other PRs (#2031 and pi-hole/pi-hole#4485) Signed-off-by: rdwebdesign <[email protected]> * Use the same messages used in #2031 Signed-off-by: rdwebdesign <[email protected]> * Keep the old responses to avoid break things Signed-off-by: rdwebdesign <[email protected]> * More comments less variables Signed-off-by: rdwebdesign <[email protected]>
This pull request has been mentioned on Pi-hole Userspace. There might be relevant details there: https://discourse.pi-hole.net/t/pi-hole-ftl-v5-14-web-v5-11-and-core-v5-9-released/53529/1 |
By submitting this pull request, I confirm the following:
git rebase
)git commit --signoff
)What does this PR aim to accomplish?:
Fix #2051
How does this PR accomplish the above?:
Fixing the code to replicate the new behavior created for #2031.
What documentation changes (if any) are needed to support this PR?:
none, I think.