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
Build visual feedback to assist users when there is no data to show (why?) #404
Comments
Increasingly important where piwik is a hosted by 3rd parties providing support, eg Sourceforge hosted apps (where I noticed some tickets being opened for piwik). |
this could also simply be a notice message "There is no data for this day. More information" with a link to the FAQ: http://piwik.org/faq/troubleshooting/#faq_58 |
I had the same 'problem' and I think the notice matt proposed is the best thing for a quick (first?) solution. I just didn't realize I was on the wrong day, so the hint 'for this day' is really good. |
The message should link to the Javascript code for the website! |
The inline help / link should only be displayed if the number of visits for the period is zero. |
Not a major support issue... delaying |
Also, we should check value of enable browser archiving & if cron is running |
What do you think about this feature? There's potential to easily improve the "default state - no visit view". |
Again a feedback today: |
Proposed feature:
When user visits Piwik
- the controller fetches the Archive, if number of visits for the period is 0
– check a flag in option table, to see if for this website there was tracking data found in the logs
– select count() if first time querying
- if there is some data in earlier or later dates, display “there is no data in this report” normal behavior
- if there is no log in the piwik DB, have a Notice/Help message displayed at the top in the In-app message, on the left of “About Piwik 1.2”
– the message would explain there is no log found for this website, maybe a problem with the tracking code? Link to FAQ.
Requires: in-app messaging #1358
The text was updated successfully, but these errors were encountered: