Skip to content
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

Browsers plugin graph report percentage instead of visits #1125

Closed
anonymous-matomo-user opened this issue Jan 25, 2010 · 24 comments
Closed
Labels
duplicate For issues that already existed in our issue tracker and were reported previously. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Milestone

Comments

@anonymous-matomo-user
Copy link

The current view of the plugins used are meaningless.
You can see in the graph how many people support this plugin but you have to look to another widget to see the count of people traced.

If i see it right in ticket #852 there are no detection for IE.

Proposal:

  • put percentage of visitors handling the plugin instead of number of visitors. This percentage would be based on all visits, excluding IE visits.
  • Add a note below the datatable explaining that Plugins detection doesn't work in IE and therefore the report is extrapolated based on non IE browsers.
    Keywords: browser, plugin, chart
@robocoder
Copy link
Contributor

Requires changes to Visualization and ViewDataTable classes to support this chart type and
data stream (Similar to #397.)

@mattab
Copy link
Member

mattab commented Feb 11, 2010

Renaming and increasing priority.

It would be easy to change the current graph and display percentage of users that have the plugin enabled. This would fix the main issue of this report.

@sgiehl
Copy link
Member

sgiehl commented Jul 10, 2010

(In [2469]) refs #1125 now shows table instead of bar chart, displaying percentage of visits (excluding ie visits)

@sgiehl
Copy link
Member

sgiehl commented Jul 10, 2010

would anyone please add the mentioned note to the view script/translation and close this ticket.
I have problems with finding a suitable phrase for that in english (only got some in german...)

@mattab
Copy link
Member

mattab commented Jul 12, 2010

Message proposal: Note: Plugins detection doesn't work in Internet Explorer. This report is based only on non IE browsers.

patch looks good!

@mattab
Copy link
Member

mattab commented Jul 12, 2010

(In [2474]) Refs #1125

@mattab
Copy link
Member

mattab commented Jul 13, 2010

(In [2493]) Fixes #1125

  • column translation was empty
  • displaying message in footer + adding general feature to display footer messages
  • fixing sorting was not working on the % Visits column because filter was queued and the Sort filter was executed before the new column was added. Instead, just applied the filter directly in API.

@mattab
Copy link
Member

mattab commented Jul 13, 2010

Attachment: after changes
plugins.png

@mattab
Copy link
Member

mattab commented Jul 14, 2010

Bug, see screenshot: cookie detection works on IE therefore should not remove IE users (or % visits is higher than 100%)

@mattab
Copy link
Member

mattab commented Jul 14, 2010

Attachment:
cookie works on all browsers.png

@sgiehl
Copy link
Member

sgiehl commented Jul 14, 2010

I guess the best solution to get representive values for all is to calculate the cookie value including IE users and the rest without those. Or shall we include ie to all values?

@mattab
Copy link
Member

mattab commented Jul 14, 2010

sounds good - I think we can leave the messaging as it is.

@sgiehl
Copy link
Member

sgiehl commented Jul 16, 2010

(In [2519]) fixes #1125 include ie users for cookie value calculation, now works for multiple periods like last10

@sgiehl
Copy link
Member

sgiehl commented Jul 16, 2010

Wasn't as easy as I thought. The last change for the API-function didn't work for multiple periods like last10. So I had to change a bit more than only the cookie value calculation. Maybe anyone sees an easier way of doing this...

@mattab
Copy link
Member

mattab commented Jul 17, 2010

code is too complicated I agree. Maybe this would be easy by writing a DataTable Filter? The Filter will access a standard datatable and therefore can contain the simple code contained currently in your API function.

The datatable array will simply apply the filter to all datatable inside it. It would in this case update all stats, except cookies.

Do you see what I mean?

@mattab
Copy link
Member

mattab commented Jul 20, 2010

(In [2595]) Refs #1125

  • Example of a simple filter to apply to the datatable in the API method. Filters will automatically work on all dataTable are are easy to write /maintain
  • Fixing tests

@sgiehl
Copy link
Member

sgiehl commented Jul 22, 2010

java detection seems to work in IE, too. see #1496

@mattab
Copy link
Member

mattab commented Jul 22, 2010

we can do this a bit later as code works as is. Let's focus on the secret project ;-)

@robocoder
Copy link
Contributor

(In [3031]) refs #1125 - partially revert r2595 ... the "%" (unit) is inconsistent with revenue (no unit); refs #1562

@robocoder
Copy link
Contributor

What's the remaining "todo" on this ticket?

@sgiehl
Copy link
Member

sgiehl commented Sep 27, 2010

Code works as it is, but code complexity is still a bit too hight. see https://github.com/piwik/piwik/blob/master/plugins/UserSettings/API.php#L93

Maybe that could be solved a better way by using an tablefilter. Problem is that some plugins are treated a special way, as their detection does work in IE aswell.

@mattab
Copy link
Member

mattab commented Nov 16, 2010

I'll take a look at the code and see if we can write a shorter version (maybe reusable). See also #1816

@mattab
Copy link
Member

mattab commented Jan 12, 2011

it seems sometimes the % visit might be wrong: http://wishuload.de/images/19232-42-2011-01-12142443.png

@mattab
Copy link
Member

mattab commented Mar 4, 2011

See #2133 for code improvement now affecting another code

Closing this ticket as request was implemented, SteveG your next patch will be closed a lot faster I promise :)

@anonymous-matomo-user anonymous-matomo-user added this to the Piwik 1.2.1 milestone Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate For issues that already existed in our issue tracker and were reported previously. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Projects
None yet
Development

No branches or pull requests

4 participants