when showing all time data, Pi-hole uses Dec 31st 1969 as the oldest date.
Or maybe add some setting that allows us to set the oldest date manually?
same for all other range when data is not yet available.
Am I missing something or this should be a good feature to add to Pi-hole?
Implemented by
pi-hole:devel ← rdwebdesign:lt_graph_changes
opened 01:12AM - 12 Nov 21 UTC
**By submitting this pull request, I confirm the following:**
- [x] I have r… ead and understood the [contributors guide](https://github.com/pi-hole/AdminLTE/blob/master/CONTRIBUTING.md), as well as this entire template.
- [x] I have made only one major change in my proposed changes.
- [x] I have commented my proposed changes within the code.
- [x] I have tested my proposed changes.
- [x] I am willing to help maintain this change if there are issues with it later.
- [x] I give this submission freely and claim no ownership.
- [x] It is compatible with the [EUPL 1.2 license](https://opensource.org/licenses/EUPL-1.1)
- [x] I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html))
- [x] I have Signed Off all commits. ([`git commit --signoff`](https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---signoff))
---
**What does this PR aim to accomplish?:**
Fix #1968
**How does this PR accomplish the above?:**
- this PR changes the minimum date allowed for the "daterangepicker", ensuring that the beginning of the displayed graph matches the oldest data contained in the database.
- The maximum date is limited to "today" (the limits apply to all ranges).
- a call to the API retrieves the oldest date from the database (`getMinTimestamp`);
- this value is used to limit the `daterangepicker` selector.
- the code that controls the "interval" between ticks was changed too.
**What documentation changes (if any) are needed to support this PR?:**
none
and released with Pi-hole FTL v5.12, Web v5.9 and Core v5.7 released