issue_owner_repo listlengths 2 2 | issue_body stringlengths 0 262k ⌀ | issue_title stringlengths 1 1.02k | issue_comments_url stringlengths 53 116 | issue_comments_count int64 0 2.49k | issue_created_at stringdate 1999-03-17 02:06:42 2025-06-23 11:41:49 | issue_updated_at stringdate 2000-02-10 06:43:57 2025-06-23 11:43:00 | issue_html_url stringlengths 34 97 | issue_github_id int64 132 3.17B | issue_number int64 1 215k |
|---|---|---|---|---|---|---|---|---|---|
[
"matomo-org",
"matomo"
] | To build some plugins it would be useful to easily access a list of developer friendly flags:
- isAdmin
- isSuperUser
- isAnonymous
- isView
- ?
- document the postEvent smarty hook. Do we use the filter feature? what we need is simply way to print out html in templates from plugins; clarify.
- document all of the variables accessible in smarty in the piwik wiki.
| Developer doc: update ExamplePlugin which lists available smarty flags that plugin dev can use | https://api.github.com/repos/matomo-org/matomo/issues/5535/comments | 2 | 2008-02-08T15:42:05Z | 2014-07-08T10:17:11Z | https://github.com/matomo-org/matomo/issues/5535 | 37,356,218 | 5,535 |
[
"matomo-org",
"matomo"
] | This is currently not optimized as it can be called multiple times and is computed over and over again. Maybe some sort of cache would be useful.
But we first need to profile to see what's happening exactly.
| Optimize getDateStart getDateEnd in *period | https://api.github.com/repos/matomo-org/matomo/issues/5534/comments | 1 | 2008-02-08T15:40:10Z | 2014-07-08T10:17:10Z | https://github.com/matomo-org/matomo/issues/5534 | 37,356,217 | 5,534 |
[
"matomo-org",
"matomo"
] | After expanding/collapsing the actions multiple times, the +/- break. It may be a mistake in the jquery selector used.
| The actions table sometimes doesnt display the +/- image properly | https://api.github.com/repos/matomo-org/matomo/issues/5533/comments | 1 | 2008-02-08T15:38:50Z | 2014-07-08T10:17:10Z | https://github.com/matomo-org/matomo/issues/5533 | 37,356,216 | 5,533 |
[
"matomo-org",
"matomo"
] | And plugins should be able to add/remove entries of this menu.
| Build a menu in the admin section. | https://api.github.com/repos/matomo-org/matomo/issues/5532/comments | 2 | 2008-02-08T15:37:57Z | 2014-07-08T10:17:10Z | https://github.com/matomo-org/matomo/issues/5532 | 37,356,215 | 5,532 |
[
"matomo-org",
"matomo"
] | The labels should be truncated.
| Pie chart legend breaks with long labels | https://api.github.com/repos/matomo-org/matomo/issues/5531/comments | 2 | 2008-02-08T15:37:13Z | 2014-07-08T10:17:10Z | https://github.com/matomo-org/matomo/issues/5531 | 37,356,214 | 5,531 |
[
"matomo-org",
"matomo"
] | currently the pie chart only plots the top 5 results. It should instead plot all 100% of the data.
| Fix pie charts | https://api.github.com/repos/matomo-org/matomo/issues/5530/comments | 4 | 2008-02-08T15:36:50Z | 2014-07-08T10:17:10Z | https://github.com/matomo-org/matomo/issues/5530 | 37,356,213 | 5,530 |
[
"matomo-org",
"matomo"
] | The plugin manager should check that plugins which have an install() method are actually installed.
| PluginsManager should run install() when plugins are activated already but not installed | https://api.github.com/repos/matomo-org/matomo/issues/5529/comments | 0 | 2008-02-08T15:36:08Z | 2008-02-18T17:21:19Z | https://github.com/matomo-org/matomo/issues/5529 | 37,356,212 | 5,529 |
[
"matomo-org",
"matomo"
] | When clicking an action name very fast, we can load the same action tree multiple times. This should only load the action once.
In the implementation, we must make sure that we don't set a global variable but only a n object variable, as this must work well with multiple datatable_actions in the same page.
| Click action multiple times load action multiple times | https://api.github.com/repos/matomo-org/matomo/issues/5528/comments | 1 | 2008-02-08T15:35:22Z | 2014-07-08T10:17:10Z | https://github.com/matomo-org/matomo/issues/5528 | 37,356,211 | 5,528 |
[
"matomo-org",
"matomo"
] | The default widget list is not optimal.
We need to
- think about the best widgets to include by default (not too many, not too few)
- change the string in the JS code
| Update list of default widgets | https://api.github.com/repos/matomo-org/matomo/issues/5527/comments | 1 | 2008-02-08T15:33:33Z | 2014-07-08T10:17:10Z | https://github.com/matomo-org/matomo/issues/5527 | 37,356,210 | 5,527 |
[
"matomo-org",
"matomo"
] | we need to group all the administration links in one page (currently there are in the user interface on the right).
this admin UI would be linked from the footer & header of piwik.
Also add links to this page on the admin plugins page and on generate visits page
Footer = api home devzone feedback seo
| Admin index page interface | https://api.github.com/repos/matomo-org/matomo/issues/5526/comments | 5 | 2008-02-08T15:32:05Z | 2014-07-08T10:17:10Z | https://github.com/matomo-org/matomo/issues/5526 | 37,356,209 | 5,526 |
[
"matomo-org",
"matomo"
] | build a page for plugins administration
- colors for activated/deactivated plugins
- better table style
I have in mind the WORDPRESS plugins admin page which looks really good, we could get inspiration from it
| Nice admin interface for plugin management | https://api.github.com/repos/matomo-org/matomo/issues/5525/comments | 3 | 2008-02-08T15:31:11Z | 2014-07-08T10:17:10Z | https://github.com/matomo-org/matomo/issues/5525 | 37,356,207 | 5,525 |
[
"matomo-org",
"matomo"
] | Currently changing the date in the calendar also changes the currently viewed section (reset to Dashboard).
Instead we should reload the same category.
See also #103
| Changing the date in the calendar should not reset the current viewed section | https://api.github.com/repos/matomo-org/matomo/issues/5524/comments | 1 | 2008-02-08T15:29:55Z | 2014-07-08T10:17:10Z | https://github.com/matomo-org/matomo/issues/5524 | 37,356,206 | 5,524 |
[
"matomo-org",
"matomo"
] | This problem comes from the fact that we use ajax to load every content in piwik, so the URL remains the same all the time.
To fix this we can use the # in the URL, the same way Gmail does.
**proposal**
- at least following variables should be persisted in V1: day/period/idSite/module/action
- how to implement it? I would suggest the Facebook way (ie. the query after the #, eg. #module=Referers&action=getSearchEngines&idSite=1 etc.)
- see http://dev.piwik.org/trac/wiki/HowToTestUI which lists all UI features; good place to start to get a feeling of what is necessary to persist
**Calendar**
Currently changing the date in the calendar also changes the currently viewed section (reset to Dashboard).
Instead we should reload the same category.
**Ressources**
See [Jquery History](http://www.mikage.to/jquery/jquery_history.html)
jQuery history plugin: It uses the hash (fragment)
method that was mentioned earlier in this thread. You essentially need to be able to store some text that encapsulates the current page state so that it can be recreated by the browser on reload; no information beyond that in the URL is maintained in any reliable way. This particular plugin also has the effect of making the "back" and "forward" buttons undo and redo page state changes, which you may or may not want.
| Hitting the refresh button should refresh the exact same page | https://api.github.com/repos/matomo-org/matomo/issues/5523/comments | 7 | 2008-02-08T15:28:49Z | 2014-07-08T10:17:10Z | https://github.com/matomo-org/matomo/issues/5523 | 37,356,204 | 5,523 |
[
"matomo-org",
"matomo"
] | Find where this bug comes from + to try to fix it the best way.
| Dashboard very slow under Opera, slow under safari | https://api.github.com/repos/matomo-org/matomo/issues/5522/comments | 1 | 2008-02-08T15:26:43Z | 2014-07-08T10:17:09Z | https://github.com/matomo-org/matomo/issues/5522 | 37,356,203 | 5,522 |
[
"matomo-org",
"matomo"
] | Run the YSlow! analyze on the piwik User interface and fix the problems using Yahoo suggestions.
| YSlow analyze + fix the mistakes | https://api.github.com/repos/matomo-org/matomo/issues/5521/comments | 5 | 2008-02-08T15:25:41Z | 2014-07-08T10:17:09Z | https://github.com/matomo-org/matomo/issues/5521 | 37,356,201 | 5,521 |
[
"matomo-org",
"matomo"
] | Plugin to display general statistics about the site SEO:
- Google Pagerank, Alexa, Compete,
- number of incoming links on google, yahoo, live. Page from google/yahoo fetched in php, grep for the number of links; maybe php library exists to do this
## SEO PLUGIN
see #1459 for the new ticket
## (old) SEO widget proposal
Widget would be really simple, providing a form for URL customizable below, like the feedburner widget. URL would be auto-completed with main website URL.
Widget would display the 3 ranks + 3 number of incoming links.
Plugin would expose the alexarank, google pagerank, all other data in the API.
Optionally, results could be cached for days in the db so that lookup is fast.
See [15 Tools for Monitoring a Websites Popularity](http://sixrevisions.com/tools/tools_monitoring_website_popularity/)
| Plugin for SEO piwik: alexa, google pagerank, incoming links | https://api.github.com/repos/matomo-org/matomo/issues/5520/comments | 19 | 2008-02-06T13:09:25Z | 2014-07-08T10:17:09Z | https://github.com/matomo-org/matomo/issues/5520 | 37,356,199 | 5,520 |
[
"matomo-org",
"matomo"
] | The user should be able to build quickly a composite dashboard, displaying statistics for several of his websites and widget at different timescale.
This involve adding a mini configuration interface (calendar) for each widget.
| Multi site / multi period dashboard | https://api.github.com/repos/matomo-org/matomo/issues/5519/comments | 0 | 2008-02-06T13:01:21Z | 2008-07-23T13:38:02Z | https://github.com/matomo-org/matomo/issues/5519 | 37,356,198 | 5,519 |
[
"matomo-org",
"matomo"
] | Button to export in one click a widget (or even better a whole dashboard layout) to netvibes / igoogle / ...
| Simple export widget to netvibes/igoogle | https://api.github.com/repos/matomo-org/matomo/issues/5518/comments | 1 | 2008-02-06T12:58:48Z | 2014-07-08T10:17:09Z | https://github.com/matomo-org/matomo/issues/5518 | 37,356,197 | 5,518 |
[
"matomo-org",
"matomo"
] | A global database agregating some interesting statistics of several websites using piwik could create very interesting figures for the webmaster : profile/quality of his visitors in comparison with global internet user...
| Plugin to publish statistics on a centralized database | https://api.github.com/repos/matomo-org/matomo/issues/5517/comments | 0 | 2008-02-06T12:56:51Z | 2008-10-10T16:57:10Z | https://github.com/matomo-org/matomo/issues/5517 | 37,356,196 | 5,517 |
[
"matomo-org",
"matomo"
] | Compute a global performance score based on page view/referers number/keyword number/evolution/... "kind of evolued google page rank"
The score could then be displayed in a little widget to be published on the website itself (blog, etc) or in community-based website like facebook
| Plugin to compute the website "Piwik Rank" | https://api.github.com/repos/matomo-org/matomo/issues/5516/comments | 1 | 2008-02-06T12:53:02Z | 2014-07-08T10:17:08Z | https://github.com/matomo-org/matomo/issues/5516 | 37,356,195 | 5,516 |
[
"matomo-org",
"matomo"
] | At the moment we use a mix of normal and mignify javascript.
However for performance reasons we will use only mignified javascript when possible.
Let's convert all Jquery libs to mignify.
At the moment we don't convert the datatable.js, etc. as the conversion should happen as a post commit hook / or during the build.
| Mignify all javascript used in piwik (except those piwik made) | https://api.github.com/repos/matomo-org/matomo/issues/5515/comments | 1 | 2008-01-31T23:47:01Z | 2014-07-08T10:17:08Z | https://github.com/matomo-org/matomo/issues/5515 | 37,356,194 | 5,515 |
[
"matomo-org",
"matomo"
] | because when we make a change to the javascript code, it's important to test all the features of the UI to make sure there is no regression. WE know how to test those things, but YOU don't.
Therefore we are going to write a guide to explain it to you.
Well, Julien is going to.
- also speak about this website in the guide http://browsershots.org/ (example on http://browsershots.org/http://piwik.org/demo )
| Write "how to test all the features of the UI checklist?" | https://api.github.com/repos/matomo-org/matomo/issues/5514/comments | 1 | 2008-01-30T01:12:02Z | 2014-07-08T10:17:08Z | https://github.com/matomo-org/matomo/issues/5514 | 37,356,192 | 5,514 |
[
"matomo-org",
"matomo"
] | Sometimes you lost the position of the datatable (for instance datatable -> tag cloud), we should do an automatic scroll...
| ScrollTo on ajax reload of datatables | https://api.github.com/repos/matomo-org/matomo/issues/5513/comments | 0 | 2008-01-30T01:00:16Z | 2008-03-11T15:13:00Z | https://github.com/matomo-org/matomo/issues/5513 | 37,356,191 | 5,513 |
[
"matomo-org",
"matomo"
] | When you try to find a keyword that doesn't exist on a classic DataTable, the result is "No data for this table", and the find box disappear, so you can't cancel the search filter.
| Find box disappear after a 'bad search' on DataTable | https://api.github.com/repos/matomo-org/matomo/issues/5512/comments | 0 | 2008-01-30T00:58:32Z | 2009-08-14T09:54:10Z | https://github.com/matomo-org/matomo/issues/5512 | 37,356,190 | 5,512 |
[
"matomo-org",
"matomo"
] | currently done in Home/Controller/setgeneralvariablesview()
but there should be a controller child that sets these
| There should be a controller that sets general variables | https://api.github.com/repos/matomo-org/matomo/issues/5511/comments | 0 | 2008-01-29T23:55:10Z | 2008-10-10T16:47:40Z | https://github.com/matomo-org/matomo/issues/5511 | 37,356,189 | 5,511 |
[
"matomo-org",
"matomo"
] | The user could want to save the default appearance of his widgets.
Currently only the widget name is saved. But it would be nice to also save the "state" of the widget, in this case defined by the "viewDataTable" parameter.
For instance he can decide to view getCountry with a pie-chart by
default.
Parameters would be stored in the JSON as an array.
see also #380
Keywords: persistance view widgets
| Widgets should be able to persist some parameters (eg. viewDataTable) | https://api.github.com/repos/matomo-org/matomo/issues/5510/comments | 5 | 2008-01-29T23:27:25Z | 2014-07-08T10:17:08Z | https://github.com/matomo-org/matomo/issues/5510 | 37,356,188 | 5,510 |
[
"matomo-org",
"matomo"
] | We need to create a user friendly API that will generate the javascript code to fetch widget from piwik.
For instance : <script type="text/javascript" src="http://localhost/piwik-src/?module=Widgetize&action=js&moduleToWidgetize=Home&actionToWidgetize=getPlugin&idSite=1&period=day&date=yesterday</script>
Could be rewritten in php like that:
getWidget(array("module"=>"Home", "action"=>"getPlugin", ...));
| Create API in several languages to embed piwik widgets in other websites | https://api.github.com/repos/matomo-org/matomo/issues/5509/comments | 2 | 2008-01-29T15:18:41Z | 2014-07-08T10:17:08Z | https://github.com/matomo-org/matomo/issues/5509 | 37,356,187 | 5,509 |
[
"matomo-org",
"matomo"
] | see the phpmv login form http://www.phpmyvisites.us/phpmv2/index.php?site=1&date=2008-03-10&period=1&mod=login
see
see for usability tips on registration form
http://www.getelastic.com/registration-usability-tips-ecommerce/
| Design nice login screen | https://api.github.com/repos/matomo-org/matomo/issues/5508/comments | 2 | 2008-01-28T21:07:53Z | 2014-07-08T10:17:08Z | https://github.com/matomo-org/matomo/issues/5508 | 37,356,186 | 5,508 |
[
"matomo-org",
"matomo"
] | In the provider plugin we can have an unknow Provider. instead or redirecting to piwik.org we could redirect to a wiki help page that explains why we have an unknown provider.
| Unknow provider redirects to wiki help | https://api.github.com/repos/matomo-org/matomo/issues/5507/comments | 0 | 2008-01-26T02:26:41Z | 2009-02-11T03:00:14Z | https://github.com/matomo-org/matomo/issues/5507 | 37,356,185 | 5,507 |
[
"matomo-org",
"matomo"
] | Instead of redirecting to the login page, it should redirect to the referer.
Careful: must be tested with API auth / external piwik auth / no referers / etc.
NB: IDEM for logout
| After login, the login module should redirect to referer | https://api.github.com/repos/matomo-org/matomo/issues/5506/comments | 1 | 2008-01-26T02:25:29Z | 2014-07-08T10:17:08Z | https://github.com/matomo-org/matomo/issues/5506 | 37,356,184 | 5,506 |
[
"matomo-org",
"matomo"
] | When archiving data for a period that is not finished (today, this week, this month, etc.) the archive is not definitive and one day piwik will compute the data of this period. At this point we will still have the temporary archive in the DB ; it should be deleted.
- day: delete where period = day and date1 = DATE(ts_archived)
delete archives for a given date that were archived this same day
- week: delete where period = week and date1 = startWeek and date2= endWeek and DATE(ts_archived) <= date2
etc.
| Temporary archives should be deleted | https://api.github.com/repos/matomo-org/matomo/issues/5505/comments | 1 | 2008-01-24T03:29:30Z | 2014-07-08T10:17:08Z | https://github.com/matomo-org/matomo/issues/5505 | 37,356,183 | 5,505 |
[
"matomo-org",
"matomo"
] | A report is defined by its data, but this is not enough.
We also need to somehow define in the report
- a date format (for graphs it may be 'Week 2' but when displayed in the UI it would be 'Week of January, 21st')
- legends for graphs (eg. '%s visits' or '%s distinct keywords')
- title for the report (eg. 'Distinct keywords' 'Countries')
- titles for graphs (eg. 'Evolution of the number of %s', or simply use the report title as is)
- existing bug, in Visitors > Overview, the graph always shows the english word 'days' eg. in french: volution sur les 30 derniers days
- other..?
Also see #5546
This has to be specified first as I think I may have forgotten some points.
| Proper handling of strings description of data (report titles, legends, date handling) | https://api.github.com/repos/matomo-org/matomo/issues/5504/comments | 2 | 2008-01-20T20:23:26Z | 2014-07-08T10:17:08Z | https://github.com/matomo-org/matomo/issues/5504 | 37,356,181 | 5,504 |
[
"matomo-org",
"matomo"
] | Google analytics Tracking API seems really powerful.
We wouldn't need so much but the concept is good.
http://code.google.com/apis/analytics/docs/gaJSApi.html
| Investigate a javascript tracking API | https://api.github.com/repos/matomo-org/matomo/issues/5503/comments | 2 | 2008-01-19T21:01:12Z | 2014-07-08T10:17:08Z | https://github.com/matomo-org/matomo/issues/5503 | 37,356,180 | 5,503 |
[
"matomo-org",
"matomo"
] | There should be the ability to add modules in the client javascript. It would make the piwik.js much easier to maintain and extend.
The client modules would be things such as:
Outbound link tracking
Click tracking for heatmaps
Displaying information in the pages being tracked
The modules will be able to hook in various points during execution:
'run' - as soon the script is run
'load' - as soon the DOM is loaded
'log' - when an action is logged
'unload' - when script is unloaded
About the packer/compiler:
There should be a php script that takes the base piwik js along with any js modules and joins/packs/minifies them in one file.
| Modular architecture for client javascript plus packer/compiler | https://api.github.com/repos/matomo-org/matomo/issues/5502/comments | 4 | 2008-01-15T03:16:15Z | 2014-07-08T10:17:46Z | https://github.com/matomo-org/matomo/issues/5502 | 37,356,179 | 5,502 |
[
"matomo-org",
"matomo"
] | Review files for any Apache specific code. Create any needed rewrite rules for lighty's url rewriting mechanisms.
Explore relevant modules such as:
# mod_geoip - IP based Country/City lookup
# mod_useronline - Online User Tracker Tracks and reports users online by unique ip
# mod_usertrack - Cookie-based user tracker
# mod_mem_cache - caches static files in memory for faster serving
# mod_magnet - Magnet - Replaces mod_cml
Keywords: lighttpd
| lighttpd compatibility | https://api.github.com/repos/matomo-org/matomo/issues/5501/comments | 1 | 2008-01-15T03:01:27Z | 2014-07-08T10:17:07Z | https://github.com/matomo-org/matomo/issues/5501 | 37,356,178 | 5,501 |
[
"matomo-org",
"matomo"
] | In Piwik_LogStats_Visit::getRefererInformation() we backported a code from phpmyvisites that is supposed to handle non-utf8 search engine keywords. I'm not sure it's really working because it hasn't been tested in Piwik.
We would need to test it on websites that get visits from chinese/hebrew search engines.
| Test the support of non utf8 search engines | https://api.github.com/repos/matomo-org/matomo/issues/5500/comments | 0 | 2008-01-10T22:35:05Z | 2009-01-30T06:31:18Z | https://github.com/matomo-org/matomo/issues/5500 | 37,356,177 | 5,500 |
[
"matomo-org",
"matomo"
] | This feature exists in phpMyVisites.
It should be possible in the admin area, to add new partners' URLs, for a campaign.
For example, visitors coming from "sourceforge.net/*/piwik/" (broad match supported) would be classified automatically under the campaign "Campaign Sourceforge".
See for reference [source:/trunk/config/global.ini.php]
```
169 ; variable name to track any campaign, for example CPC campaign
170 ; Example: If a visitor first visits 'index.php?piwik_campaign=Adwords-CPC' then it will be counted as a campaign referer named 'Adwords-CPC'
171 campaign_var_name = piwik_campaign
172
173 ; variable name to track any campaign keyword
174 ; Example: If a visitor first visits 'index.php?piwik_campaign=Adwords-CPC&piwik_kwd=My killer keyword' then it will be counted as a campaign referer named 'Adwords-CPC' with the keyword 'My killer keyword'
175 campaign_keyword_var_name = piwik_kwd
```
| Plugin to automatically define the Campaign name based on the referer URL | https://api.github.com/repos/matomo-org/matomo/issues/5499/comments | 2 | 2008-01-10T16:58:45Z | 2024-09-13T09:13:20Z | https://github.com/matomo-org/matomo/issues/5499 | 37,356,176 | 5,499 |
[
"matomo-org",
"matomo"
] | in [source:/trunk/modules/ViewDataTable.php] method`
getJavascriptVariablesToSet()` we load GET parameters values and print them in the javascript code to "forward" the values to the Javascript logic (used in the Jquery code).
Is this safe? We use`
Piwik_Common::getRequestVar()` to sanitize the value but is it safe enough? Or could some hijacking/xss/etc be possible here?
| Check that printing GET parameters in the JS code is secure | https://api.github.com/repos/matomo-org/matomo/issues/5498/comments | 2 | 2008-01-10T16:09:59Z | 2014-07-08T10:17:07Z | https://github.com/matomo-org/matomo/issues/5498 | 37,356,175 | 5,498 |
[
"matomo-org",
"matomo"
] | Such an integration could range from very simple to very complex depending on the developper time & passion.
A few ideas
- add country flags / browser / OS icons to comments
- easy integration of the javascript code in the footer
- integration of the widget showing some basic statistics in WP sidebar / in admin dashboard
- loading piwik interface from within wordpress interface
- check the following list for good ideas:
!http://lorelle.wordpress.com/2007/02/12/counting-wordpress-statistics-wordpress-plugins/
| Plugin to provide a Wordpress integration | https://api.github.com/repos/matomo-org/matomo/issues/5496/comments | 5 | 2008-01-06T03:14:04Z | 2014-07-08T10:17:07Z | https://github.com/matomo-org/matomo/issues/5496 | 37,356,174 | 5,496 |
[
"matomo-org",
"matomo"
] | During the install process, if the database collation is "unicode-", the table log_profiling cannot be created; the following error is raised: SQLSTATE[42000]: Syntax error or access violation: 1071 La cl est trop longue. Longueur maximale: 1000'
| install: table creation fails, when database collation is "unicode" | https://api.github.com/repos/matomo-org/matomo/issues/5495/comments | 2 | 2008-01-05T19:17:12Z | 2014-07-08T10:17:07Z | https://github.com/matomo-org/matomo/issues/5495 | 37,356,173 | 5,495 |
[
"matomo-org",
"matomo"
] | phpMyVisites supports ClickHeat (http://www.labsmedia.com/clickheat/) and Piwik could do the same.
The DEV version is available on http://www.labsmedia.com/clickheat/piwik/piwik-clickheat.tar.gz This is DEV only and may not work with latest trunk.
If you're interested to contribute please contact hello at piwik.org and yvan DOT taviaud at m4am.net
Keywords: third-party-plugin
| Plugin for Click map | https://api.github.com/repos/matomo-org/matomo/issues/5493/comments | 158 | 2008-01-04T02:23:33Z | 2017-03-24T16:44:49Z | https://github.com/matomo-org/matomo/issues/5493 | 37,356,168 | 5,493 |
[
"matomo-org",
"matomo"
] | The idea behind the plugin is to make it possible to export reports by email.
It would be possible also to specify preferences such as
- daily / weekly / monthly reports
- reports contained in the email
The implementation is not defined yet though, as we need to finish the task #54 first.
| Plugin to send reports by email | https://api.github.com/repos/matomo-org/matomo/issues/5492/comments | 14 | 2008-01-04T02:22:07Z | 2014-07-08T10:17:02Z | https://github.com/matomo-org/matomo/issues/5492 | 37,356,167 | 5,492 |
[
"matomo-org",
"matomo"
] | Users need to share Piwik reports with colleagues, customers or externals. PDF is the standard way of exchanging rich data, with graphs, colors, consistent design.
# Proposed features set of Piwik PDF export
For the first release of PDF export in Piwik, I think the following features would be important to have:
- Create the pdf: the PDF would not be customizable and would include all Piwik reports. The tables would be "all columns" tables, ie. they contain Visits, unique visitors, bounce rate, goal conversion rate, etc.
- Send & receive the PDF: the PDF would be downloadable via a click in the "User Settings" page. Also, a click on a link would send an email with the PDF attached to the given email addresses (easier for users to forward the emails to others rather than create a new email, attaching the PDF, etc.).
- Look and feel: the PDF reports would contain tables, that look similar to the tables in Piwik reports. For example, search engine icons, countries flags would be displayed. Each page would contain the title of the report, and as many rows as can fit on the page (maybe 20 rows per table?).
- Internationalization. The PDF reports would be localized in any of the 35+ languages.
Other features probably for later releases:
- Customize PDF: each user would be able to customize which reports make it in the PDF. Possibility to create several PDF reports, per website, or for a given website.
- Receive the PDF by email: using a new hook, see #1184, the PDF reports plugin could automatically generate and send PDF reports by email to each user that requested delivery. Users could customize the frequency (daily, weekly, monthly), and recipients (themselves and others) to send the PDF reports to.
- PDF contains sparklines
- Each Piwik widget/report can be exported in PDF (add a new export link below the table, next to CSV, XML, etc.).
Features currently not considered
- PDF contains graphs: bar, pie, evolution charts. Graphs export in PDF would be a major maintenance / time intensive task, as we would have to support a second graphing library, as OFC is flash based and can't generate PNGs.
# Thoughts about implementation
Here are some thoughts about the implementation. Please discuss before implementing, there might be better solutions.
## API to render PDF
Rendering a PDF could then be done by using following call:
```
module=API&
method=PDF.getReport&
report=$REPORT_ID&
idSite=$WEBSITE_ID&
token_auth=$TOKEN&
date=...&period=...
```
In V1, when customReports are not implemented, we would have a function PDF.getFullWebsiteReport which would return the PDF containing all reports for a given website.
There could also be a PDF.getWebsitesDashboard which would return a simple PDF containing main metrics for all websites visible to the user.
## Flow of a request to generate a PDF containing all reports
When called, the PDF API function would then:
- create and setup as default the PDF view.
- init the PDF: set colors, margins, titles, properties, generated time, etc.
- loop over all controllers, and methods that we wish to render.
- call the methods in each plugin's controller which add data to the PDF. All methods would render the "all columns" data table (that shows visits, pages, time per visit, etc.) rather than just the simple table with only the visits column.
- render the final PDF and output it to the browser
Basic skeleton for the API method PDF.getReport
```
function getReport($report, $idSite, $date, $period)
{
// set the default View to PDF Piwik_View::setDefaultView(new Piwik_View_PDF());
// define an array of Controllers/methods to call to render in this PDF,
// eg. array( array( 'Goals', 'index'), array('UserSettings', 'getBrowser') )
// loop over all the array of methods to render
// here we could add a new page, a pdf page title for the next report, etc.
// for each controller method, call it, for example
$content = Piwik_FrontController::getInstance()->fetchDispatch( 'Goals', 'index');
// this will call the index() on Goals/Controller.php
// which will, at the end, render the view eg. $view->getView()->render()
// this will result in Piwik_View_PDF->render() call which adds the right data to the PDF file being built.
// once all reports have been added to PDF, return PDF to the user
}
```
## A new View type
Currently in plugins Controllers, views are created with:
```
$view = new Piwik_View('Goals/templates/single_goal.tpl');
```
The view object encapsulates the Smarty implementation. Variables are set to the view`
$view->name = $goalDefinition['name'];` and the view is rendered at the end of the controller method:`
echo $view->render();`
In order to add PDF export with minimal effort, PDF could be a new View class, implementing the iView interface.
Currently there is core/View.php which should probably be moved to core/View/Smarty.php
there is some generic code in render() which could probably be left in the new core/View.php parent object.
We could have Piwik_View_Smarty extends Piwik_View
then we would build Piwik_View_PDF extends Piwik_View
When building a PDF report, each controller's method would be called, and the data would be added to the PDF report hold in this object. The report builder API would then output this aggregated PDF to the user.
## Adding renderer
Piwik_View_PDF could look at the template name passed in the view constructor, and based on this find out if it knows how to render this template. For example, calling the Goals.goalReport method (in plugins/Goals/Controller.php), the View is using the template Goals/templates/single_goal.tpl - if the view does know how to render this (given the variables are set properly like on the smarty template), then it can render it. If not, an error can be output. The PDF view would have logic that says: "Goals/templates/single_goal" must be rendered this way. Most templates are generic (datatable, etc.) so most of the work to render the reports would be done only once and automatically work for most reports.
## Rendering text, tables in the PDF
The library might support automatic conversion of HTML into the PDF, but most likely this doesn't work very well.
We will most likely have to write a basic PDF renderer for the datatable (equivalent of datatable.tpl).
## Custom reports
By default, we can include all tables in the PDF. But reports are useful only if they contain the subset of information a given user is interested in. We could have a simple UI, listing all available reports, with a click and add to report feature. This would be internally linked to calls to controller methods. The layout could be saved as JSON in the reports table.
## UI integration
PDF reports do not apply on per report basis, like Bar graphs or Pie charts apply. There could be a link to generate a PDF report for the current website in the header.
# Contributions
Interested by this feature? Let us know in the comments.
| Plugin to provide PDF export of data | https://api.github.com/repos/matomo-org/matomo/issues/5491/comments | 39 | 2008-01-04T02:21:02Z | 2014-07-08T10:22:43Z | https://github.com/matomo-org/matomo/issues/5491 | 37,356,165 | 5,491 |
[
"matomo-org",
"matomo"
] | To make it easy to move from phpmyvisites to Piwik such a plugin is necessary.
It would make its best to convert statistics from phpmyvisites 2.x to piwik, maximizing the user base conversion rate and making the process as smooth as possible.
**The plugin is not currently under development - if you would like to help sponsoring this plugin, please contact Piwik Consultants that would be able to help!**
| Plugin to import statistics from phpmyvisites 2.x | https://api.github.com/repos/matomo-org/matomo/issues/5490/comments | 8 | 2008-01-04T02:19:03Z | 2014-07-08T10:17:00Z | https://github.com/matomo-org/matomo/issues/5490 | 37,356,164 | 5,490 |
[
"matomo-org",
"matomo"
] | A visitor **interested** is a visitor that, for example,
- has visited more than 1 page
- stayed more than 30 seconds
- comes back 3 times a week at least
We could show in a simple report:
- countries
- keywords used
- pages visited
of the people who are defined as **interested** in the website. This would give an easy look at what segment of the visitors are potentially more interested by the content.
| Plugin to show the characteristics of people who are interested in the website | https://api.github.com/repos/matomo-org/matomo/issues/5487/comments | 1 | 2008-01-04T01:16:05Z | 2014-08-03T11:21:09Z | https://github.com/matomo-org/matomo/issues/5487 | 37,356,163 | 5,487 |
[
"matomo-org",
"matomo"
] | The plugin would make it easy to observe specific events. Example:
- when total visitors > threshold,
- when visitor per day/week/month > threshold,
- when a given keyword is used,
- when a given provider/company visit the website,
- etc.
We could then send an email, display a big red box in the UI, etc.
| Plugin to be notified when some special events happen (keyword, visits > threshold, etc.) | https://api.github.com/repos/matomo-org/matomo/issues/5486/comments | 1 | 2008-01-04T01:12:24Z | 2014-07-08T10:17:00Z | https://github.com/matomo-org/matomo/issues/5486 | 37,356,161 | 5,486 |
[
"matomo-org",
"matomo"
] | When user lost their password they should have the ability to receive it by email.
| Lost your password? module | https://api.github.com/repos/matomo-org/matomo/issues/5485/comments | 6 | 2008-01-04T01:02:04Z | 2014-07-08T10:17:00Z | https://github.com/matomo-org/matomo/issues/5485 | 37,356,160 | 5,485 |
[
"matomo-org",
"matomo"
] | It would be useful to have a page listing the
- database usage by tables
- number of rows by table
- index size
- etc.
So that people would have a simple way to copy paste their DB information in case they want, for example, to add a bug report concerning a performance problem.
| Plugin to show statistics about the Database usage and tables | https://api.github.com/repos/matomo-org/matomo/issues/5484/comments | 1 | 2008-01-04T01:00:46Z | 2014-07-08T10:16:59Z | https://github.com/matomo-org/matomo/issues/5484 | 37,356,159 | 5,484 |
[
"matomo-org",
"matomo"
] | Piwik work well with HTTPS pages - see FAQ at http://piwik.org/faq/general/#faq_68
| Compatibility with SSL (https) pages | https://api.github.com/repos/matomo-org/matomo/issues/5483/comments | 5 | 2008-01-04T00:58:57Z | 2014-07-08T10:16:59Z | https://github.com/matomo-org/matomo/issues/5483 | 37,356,157 | 5,483 |
[
"matomo-org",
"matomo"
] | There is still work to make piwik fully translatable.
We have to all strings
- in templates
- in JS variables
- design a generic system for the php exceptions to handle multilingual error messages
Keywords: i18n translation translate internationalization
| Making piwik translation ready | https://api.github.com/repos/matomo-org/matomo/issues/5482/comments | 44 | 2008-01-04T00:38:30Z | 2014-07-08T10:16:59Z | https://github.com/matomo-org/matomo/issues/5482 | 37,356,155 | 5,482 |
[
"matomo-org",
"matomo"
] | A plugin could display in a small box some global website information such as
- alexa ranking
- technorati ranking
- Pagerank
- number of backlinks
- delicious tags
- etc.
This plugin could be an example plugin of how to use external web services in a Piwik plugin.
- see http://sixrevisions.com/tools/tools_monitoring_website_popularity/
| Plugin to show global information about the website | https://api.github.com/repos/matomo-org/matomo/issues/5481/comments | 2 | 2008-01-04T00:24:00Z | 2014-07-08T10:16:58Z | https://github.com/matomo-org/matomo/issues/5481 | 37,356,154 | 5,481 |
[
"matomo-org",
"matomo"
] | In #4183 support is added for "require" piwik and / or a php version.
- Some plugins may also "require" other Piwik plugins (core or third party) to be installed at a particular minimum version.
- When a plugin has other required plugins, when possible, ask user & then install required plugins first, then this plugin.
As a result, it will be clean and almost error-free to use a plugin, as long as the developer set the "require" flags properly. This would be a subtle yet useful new feature.
| Add plugins dependency capability | https://api.github.com/repos/matomo-org/matomo/issues/5480/comments | 4 | 2008-01-04T00:08:36Z | 2024-09-13T09:13:20Z | https://github.com/matomo-org/matomo/issues/5480 | 37,356,152 | 5,480 |
[
"matomo-org",
"matomo"
] | The feedburner feeds statistics could be included in the piwik interface, using the convenient feedburner API.
Data to be included:
- clickthroughs,
- nb of items views,
- nb of subscribers
| Plugin for feedburner integration using the feedburner API | https://api.github.com/repos/matomo-org/matomo/issues/5479/comments | 15 | 2008-01-04T00:02:46Z | 2014-07-08T10:16:58Z | https://github.com/matomo-org/matomo/issues/5479 | 37,356,149 | 5,479 |
[
"matomo-org",
"matomo"
] | This is the initial spec of the Goal tracking plugin in Piwik. The plugin has been released in beta state in the list of Piwik plugins, but disabled by default. There is a ticket containing existing bugs and feature requests: #774
## Initial specs
Goal tracking notes:
- a goal is defined by a URL or a action name (is, contains, begin with)
- detects if the specified goals have been reached; for each goal give the
- conversion
- conversion rate
- coming from which referer type? (direct entry, search engines, newsletters, CPC)
- websites referers used
- search engines used
- organic keyword used
- newsletter used
- CPC list
- [ country : plugins ? ]
- partners used
- for each goal, display
- the goal statistics in the interface using the same style as the referers tables (one table for websites, se, kwd, etc.)
- the main numbers: conversion, conversion rate, etc.
- display an aggregate of all the goals using the same presentation as a goal report
Also see concerns raised by #219
Keywords: ecommerce goal conversion
| Plugin for goal tracking | https://api.github.com/repos/matomo-org/matomo/issues/5478/comments | 4 | 2008-01-03T23:59:15Z | 2014-07-08T10:16:56Z | https://github.com/matomo-org/matomo/issues/5478 | 37,356,148 | 5,478 |
[
"matomo-org",
"matomo"
] | Update: see follow up issue https://github.com/piwik/piwik/issues/5246
Most popular pages/keywords/etc. are popular every day, and it is hard to know what changed since the day before. What would be interesting would be to visualize:
- Which pages significantly increased/decreased?
- Which URLs links/SE keywords brought me significantly more/less traffic compared to last period?
This could help answer questions such as:
- Why did the website traffic suddenly decrease? Traffic from some Keywords/Referers significantly decreased, and some pages significantly were less seen.
- Similar with answering "Why did traffic suddenly increase?" Why are my Ecommerce orders growing so much, how do I know the overall positive contributors explaining our growth?
# User interface updates for new reports & hints
## New report: Overall Movers and Shakers
This report would have to query in particular: page URL, page Titles, Keywords, websites, campaigns, maybe 8 reports, for current AND previous periods. Making 16 API calls should work fine and comparison would be pretty fast hopefully.
This report could be available as a widget showing the top 5 movers and shakers overall (increased keywords, pages, etc.).
## Extend existing report: Highlight Movers and Shakers
Currently reports display "Label", "Visits count" by default. There is a button to display 5 more columns and a view for Goal conversions metrics.
We could maybe improve at least the "basic" view showing only visits.
In this view we could for example display in a new column on the right, a green or red % increase, when there is a a major change (threshold set to +/- 10% for example). Otherwise leave blank. See also #291
## Extend report: Display Movers & Shakers in all reports' footer
Below the report, or above?, we could display these rows from the report that have significantly changed since yesterday.
We could put threshold of minimum visits impacted = 20
minimum % increase or decrease = 2% for example?
So it would not display minor changes that are not interesting.
They could be displayed on top of the report
```
*Best countries*
(green sign) India (+50%) and Scotland (+33%)
(red sign) France (-33%) and Germany (-44%)
|---------|--------|
| Country | Visits |
|---------|--------|
| India | 176 |
| Scotland| 54 |
| France | 23 |
| Germany | 23 |
[....]
Next >
```
## Display evolution % next to all sparklines
Idea is to show the increase and decrease of Visits, Conversions, etc. basically next to each Sparkline. There is a proposal mockup at: http://issues.piwik.org/attachments/5711/sparklines.png
# Implementation
To produce a report "Period VS Previous period" for each keyword, we would need to select all keywords from both periods (2 datatables), and compare both to extract significant increases/decreases.
The code would be optimized so that it returns in less than 2 seconds when calling 8 different APIs so comparing 16 datatables.
The algorithm will typically extract:
- items with a growth of N %
- new items (new keyword since yesterday) with at least M %
- Never show items with less than P visits
- By default, we should enable the display in the UI for only the very significant changes, with a high threshold of visits impacted. The feature should not bring noise if the changes are not that interesting.
New widget to show this great insights:
- New smart widget to show what's changed in dashboard automatically based on last login date: #3250
# Similar tickets
- compare 2 periods: #291
- show evolution for a given keyword/page: #534
| Better Data Insights. Show me what's increased and decreased, movers and shakers (beta) | https://api.github.com/repos/matomo-org/matomo/issues/5477/comments | 45 | 2008-01-03T23:57:13Z | 2014-09-09T12:39:22Z | https://github.com/matomo-org/matomo/issues/5477 | 37,356,143 | 5,477 |
[
"matomo-org",
"matomo"
] | A server can be located in the US but the website being used by people from WEST EUROPE. Piwik user wants to see his reports in the WEST EUROPE timezone.
## UI changes
- add a new setting Timezone in the admin UI
- the timezone is website based - each website can have a different timezone set. All users looking at stats for a given website will see the data in the website' specified timezone.
- (optional) a "default timezone" can be set by the Super User, that would be used to define the timezone by default when creating new websites. When creating new websites, the timezone dropdown would be pre-selected with this "default timezone" but users could still change it. If the Super User doesn't define this default timezone, it falls back to the server timezone (current behavior).
## API changes
- timezone being an attribute of the website, the SitesManager API would have to slightly updated to reflect the new parameter. We should keep backward compatibility if possible. The timezone wuold for example become the last parameter of`
addSite( $siteName, $urls, $timezone )`} and would be optional. If not specified, the timezone would default to the general "default timezone" (see above).
## Tracking
- all dates and times must be stored in the DB in UTC. This means that in the various log_\* tables, any field that is DATE or DATETIME should be set with dates and datetimes that are based in UTC.
- currently in the Archiving process, a standard archiving query looks like:
```
SELECT name,
type,
count(distinct t1.idvisit) as nb_visits,
count(distinct visitor_idcookie) as nb_uniq_visitors,
count(*) as nb_hits
FROM (".$archiveProcessing->logTable." as t1
LEFT JOIN ".$archiveProcessing->logVisitActionTable." as t2 USING (idvisit))
LEFT JOIN ".$archiveProcessing->logActionTable." as t3 USING (idaction)
WHERE visit_server_date = ?
AND idsite = ?
GROUP BY t3.idaction
ORDER BY nb_hits DESC
```
You can see that the WHERE is currently on the visit_server_date field which is a DATE only, which is a problem for selecting records that are in a given timezone.
- for queries working on the log_visit table, the WHERE should probably be on visit_first_action_time instead. The INDEX on the log_visit table should be updated to include visit_first_action_time instead of visit_server_date.
- for queries working on the log_conversion table, the WHERE should probably be on server_time instead of visit_server_date. The INDEX on the log_conversion table should also be updated to include this field.
- I believe mysql is clever and is able to use the INDEX on a DATETIME field for a range query. We should double check that this is the case :)
## Archiving
- After these changes to the tracking tables, it will be possible to update the few queries doing the archiving and instead of using visit_server_date, make them use the right UTC time fields, and select records that are between the website specified timezone.
For example, the selected date (June 25 2009) to the website timezone:
```
visit_server_date = '2009-06-25'
```
would become for example
```
visit_first_action_time >= '2009-06-24 16:00:00'
AND visit_first_action_time <= '2009-06-24 15:59:59'
```
- this conversion of the date object would probably be done around Archive::build() - and the few archiving queries would have to be updated
## Other notes
- when changing the timezone setting for a given website, all previous stats are not re-processed and will still show in the previously selected timezone. The new timezone is applied only to future reports. Note: this is how a lot of software work (including GA, adwords, etc.)
| Support for editing the site timezone | https://api.github.com/repos/matomo-org/matomo/issues/5476/comments | 32 | 2008-01-03T23:38:24Z | 2014-07-08T10:16:54Z | https://github.com/matomo-org/matomo/issues/5476 | 37,356,140 | 5,476 |
[
"matomo-org",
"matomo"
] | A plugin that would make it easy to delete all the data for a given website in piwik.
It would be mainly useful for tests.
| Reset Statistics of one website | https://api.github.com/repos/matomo-org/matomo/issues/5475/comments | 5 | 2008-01-03T23:27:47Z | 2024-09-13T09:13:21Z | https://github.com/matomo-org/matomo/issues/5475 | 37,356,139 | 5,475 |
[
"matomo-org",
"matomo"
] | This feature is complex. We will be working very hard on this during the next few weeks.
Soon this ticket will contain information about how we are planning to implement this.
The idea is basically to let the user customize the interface as he wants, like the Google analytics dashboard or Netvibes.com
We are also trying to think of a way to use the widgets on other widget platforms such as Igoogle / netvibes / windows vista or the apple dashboard.
Any idea or suggestion is more than welcome.
| Widget architecture for the interface | https://api.github.com/repos/matomo-org/matomo/issues/5474/comments | 2 | 2008-01-03T23:20:38Z | 2014-07-08T10:16:53Z | https://github.com/matomo-org/matomo/issues/5474 | 37,356,138 | 5,474 |
[
"matomo-org",
"matomo"
] | The main reason that people stop using Piwik on small websites is because the DB grows out of control. Often users have 25Mb or 50m for the whole Mysql database. After installing the CMS, it is common for Piwik to have only 20M of space. We should try to make it easy to run Piwik with basic history and keep DB space below 20M.
**Proposal "Lightweight Piwik" feature**
- Display the current DB size. Reuse API code from: #3004
- Have a new setting "General settings" to select number of months to keep data for
- By default, keep all historical data
- In the dropdown selecting the number of months, put estimate of DB size that will be freed
- When setting enabled,
- Delete old archive_blob tables that are older than N months
- delete from all archive_numeric all rows except a critical metrics (visits, pageviews, ecommerce/goal metrics).
- also delete all segment data, numeric and blob
- Propose a dropdown to select number of months
- For each month choice "delete older than [years,4 years,custom](3,6,9,12,18,2)". Once entry is selected, refresh the space free "delete older than [months](18) (N Gb will be deleted, Total Piwik DB size will become MGb)"
- When the feature is enabled, execute it as a scheduled task (safer for huge DBs). But on page reload, we could also display a link to let the user execute the purge code NOW (when in a hurry to get the DB size under control).
Note: it would be very nice to also get rid of #2805 - just one SQL query away after all...
PS: and this one too #3003
V2 of this feature (to be put as "feature request" ticket)
- User could choose exactly which reports to purge.
- Have a "less agressive" purge mode that would keep more data, but still delete a lot of useless old reports nobody would care about
- The list would be pre-selected with our estimate of the most useful reports (eg. Keywords, Page URLs/Page Titles, Websites, Campaigns, All goal reports...) and delete all others. Call our selection "Recommended historical reports to keep"
- The list would handle numeric and blob.
- "Delete data for segmented reports" or "Keep reports for segmented data"
| Lightweight Piwik mode: Setting to purge aggregated reports older than N days from the database | https://api.github.com/repos/matomo-org/matomo/issues/5473/comments | 39 | 2008-01-03T23:09:37Z | 2014-07-08T10:16:53Z | https://github.com/matomo-org/matomo/issues/5473 | 37,356,136 | 5,473 |
[
"matomo-org",
"matomo"
] | It would be useful to be able to backup the piwik tables in a .tar.gz file on the server.
Then we could download this file or send it by email.
We also have to plan a "Import backup" tool.
Wordpress has such a feature.
| Plugin database export as zip, send by email, import | https://api.github.com/repos/matomo-org/matomo/issues/5472/comments | 1 | 2008-01-03T22:48:14Z | 2014-07-08T10:16:52Z | https://github.com/matomo-org/matomo/issues/5472 | 37,356,135 | 5,472 |
[
"matomo-org",
"matomo"
] | The API calls are currently not cached at all, except if the plugins take care of caching their own data.
It would be interesting to have a generic system for caching results of APIs calls. By default the cache would be disabled but the user could specify
- max cache size
- cache lifetime
- disable cache for some specific APIs methods
- set different parameters for specific APIs methods
Keywords: outofscope
| Generic cache system for API results | https://api.github.com/repos/matomo-org/matomo/issues/5471/comments | 2 | 2008-01-03T22:12:47Z | 2014-08-03T11:30:04Z | https://github.com/matomo-org/matomo/issues/5471 | 37,356,134 | 5,471 |
[
"matomo-org",
"matomo"
] | Currently the piwik.php renders a 1*1 transparent GIF.
We could instead display a piwik logo that would help spread the word about Piwik.
The plugin would
\* add logo field to site table in DB
\* display logo at the end of log process
\* provide an administration interface to show the different logos available and the user would choose one from them.
The logo would be on a per site basis ; you could display a logo for the site 1 but no logo for site 2 and 3.
| Plugin to display a logo, configured per site | https://api.github.com/repos/matomo-org/matomo/issues/5470/comments | 1 | 2008-01-03T21:47:28Z | 2014-07-08T10:16:52Z | https://github.com/matomo-org/matomo/issues/5470 | 37,356,133 | 5,470 |
[
"matomo-org",
"matomo"
] | Piwik now has [internal search keywords tracking](http://piwik.org/docs/site-search/). Awesome!
Functionnality:
- specify an URL + parameter for the internal search query
- give the general metrics: number of searches, visits with searches, unique searches, etc. (see comment below)
- display the list of internal searches in a new report under Actions
- can we auto detect google CSE? #426
- [see hack 64 & 65 in peterson's book](http://books.google.com/books?id=v3ebu7RJT3oC&lpg=PP1&ots=-D2kqTg_07&dq=eric%20perterson%20Web%20%20Site%20Measurement%20Hacks%3A&pg=PA253#v=onepage&q&f=false)
| Plugin Internal search tracking - search analytics reports | https://api.github.com/repos/matomo-org/matomo/issues/5469/comments | 73 | 2008-01-03T21:45:03Z | 2014-07-08T10:16:52Z | https://github.com/matomo-org/matomo/issues/5469 | 37,356,132 | 5,469 |
[
"matomo-org",
"matomo"
] | Display the latest **new search terms** used by visitors to reach the website along with the date and the page linked to.
Keywords: third-party-plugin
| Plugin latest new searches | https://api.github.com/repos/matomo-org/matomo/issues/5468/comments | 6 | 2008-01-03T21:44:24Z | 2014-08-03T11:23:55Z | https://github.com/matomo-org/matomo/issues/5468 | 37,356,131 | 5,468 |
[
"matomo-org",
"matomo"
] | Display the latest **new links** used by visitors to arrive on the website along with the date and the page linked to.
| Plugin latest new websites | https://api.github.com/repos/matomo-org/matomo/issues/5467/comments | 2 | 2008-01-03T21:43:48Z | 2014-07-08T10:16:49Z | https://github.com/matomo-org/matomo/issues/5467 | 37,356,130 | 5,467 |
[
"matomo-org",
"matomo"
] | It requires the precise geo localization plugin (#45).
We could plot the last N visitors on a google maps with the exact position of the visitors. A click on the dot could show basic information about the visitors.
| Plugin Google maps of the last N visitors | https://api.github.com/repos/matomo-org/matomo/issues/5466/comments | 3 | 2008-01-03T21:39:03Z | 2014-07-08T10:16:49Z | https://github.com/matomo-org/matomo/issues/5466 | 37,356,129 | 5,466 |
[
"matomo-org",
"matomo"
] | **GeoIp Plugin**
- When installed, the plugin will detect more accurately the country of your visitors using the MaxMind database.
- The existing reports for country and continent will be replaced by the more accurate GeoIp report in your Piwik interface.
- Piwik will also detect the city of your visitors. You can see all cities by clicking on the country row in the table.
- You can apply the GeoIp data to all your previous visits and re-generate your reports, see below.
**Requirements**
You need at least Piwik 0.2.33 to run the GeoIp plugin.
**How to install?**
- [Download Piwik GeoIp Plugin](http://issues.piwik.org/attachments/5465/GeoIP.zip?format=raw)
- Unzip the plugin and copy the extracted directory "GeoIp" in the directory piwik/plugins/
- Configure the MaxMind database:
- Either download MaxMind GeoLite City or GeoIP City database from http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz
Uncompress this file and copy it in plugins/GeoIP/libs/GeoLiteCity.dat
- For more performance, it is recommanded to install the module apache mod_geoip.
Configure your Apache according to: http://www.maxmind.com/app/mod_geoip
- Enable GeoIP plugin in Piwik. Go to Piwik > Settings > Plugins > Geoip, click Enable
**How to apply the GeoIp to all your previous visits to fix your previous reports**
You can apply GeoIP precise localization on your past data:
- run geoipUpdateRows.php script, from command line (or from the browser, but risk of timing out if your database is large)
- wait a few minutes until all your visitors data from the piwik_log_visit table have been processed.
- you now need to force Piwik to re-process all the past reports: drop all piwik_archive_\* tables in your Piwik database. Piwik will automatically create them and re-process the reports.
- You should see Visitors countries and cities in your Visitors>Location report.
**Authors**
- Mikael Letang
- Maciej Zawadziski
- Matthieu Aubry
- Anthon Pang
**Changelog**
- version 0.7: cleaned up code, compatible with Piwik 0.2.33, improved documentation
- version 0.8: fixed bug in geoIpUpdateRows.php (thanks looztra)
- version 0.9: all fields now NULLable to make sure that insert still work fine after plugin is disabled
- version 0.10: compatibility with 0.2.35 after API change in the AddWidget function
- version 0.11: fixing bug with country detection
- version 0.12: updated for auto loader
- version 0.13: Compatible with Piwik 0.6
- version 0.14:
- Fixed geoipUpdateRows script which was failing with errors. It also now checks that logged in user is Super User, and that the GeoIP plugin is enabled.
- Fixed memory leak when using visitor generator.
- Fixed .htaccess was blocking users from executing the script with the browser.
- Added .htaccess to allow to execute the script directly from the browser.
- Fixed Sparkline distinct countries
- version 0.15:
- Updated for Piwik 1.3 (refactoring for upgrade.php)
- No match for country now set to 'xx' (unknown)
- version 0.16:
- fix bootstrap in geoipUpdateRows.php and clean-up package
- geoipUpdateRows.php - MYSQLI compatibility
- default to disk-based search; load into memory if multiple tracking requests
- version 0.17:
- fixes from peterb & mruge
- version 0.18: compatible with Piwik 1.6
**Feedback**
Please leave a comment if you have any feedback, suggestion, or bug report.
Keywords: third-party-plugin
| Plugin using GeoIP to accurately detect visitor countries, cities, and continent | https://api.github.com/repos/matomo-org/matomo/issues/5465/comments | 183 | 2008-01-03T20:31:36Z | 2014-07-08T10:16:49Z | https://github.com/matomo-org/matomo/issues/5465 | 37,356,120 | 5,465 |
[
"matomo-org",
"matomo"
] | **ALPHA version currently**
Current Piwik contains a disabled-by-default plugin called Live! that, when enabled, add a new widget in the widget list, that will show your latest visitors in real time. However this plugin is not very useful as such, and was built as a proof of concept. Improving the plugin has been one of the most requested user feature for months! If you would like to help, please post a comment, or submit a patch. Enjoy
**Concept**
The page should be entertaining to watch, fed with real time data, and open the webmaster to dig more into the other reports that Piwik offer.
**Background**
This feature is heavily requested by the community (http://feedback.phpmyvisites.net/feedbacks/2630-last-n-visitor-details-config-info-path-etc) and would be really providing a plus to Piwik feature set.
**Data provided**
- at top of screen, clear summary:
- Today you had: N visits, M pages today
- In the last 30 minutes you had: X visits, Y pages
- list of the last N visitors with their information
- settings (os, browser, resolution, plugins) - icons only, details on icon hover
- referer (keyword, name, icon, clickable url - useful for SEO)
- country icon
- IP for piwik users with admin permission or super user
- count of pages seen during this visit
- time spent during this visit
- number of goals converted, click on goals would show the list of pages with goals highlighted (see below)
- for each visit, it is possible to view pages:
- page title,
- page url that links to it,
- outlinks are shown different colors (icon ?)
- downloads are shown different colors (icon ?)
- when the page view was a Goal trigger, different color (icon ?) along with goal name and revenue.
**UI features**
- this page should make it possible to view all past visits for a current returning visitor. The idea would be to have an icon when the visitor is a returning visitor. Clicking on this icon would show the past visits for this visit. This is a UI challenge to make it look good and make it usable. for examples, previous visits rows could be shown below the visit row with a left margin and below a title "This visitor previously visited the website:".
- by default, the spy mode would be enabled, therefore the page would reload regularly (every 2 seconds?) and show the new visits. We need a way to pause/resume the spy mode, if traffic is too big or if user wants to take more time to analyze existing traffic snapshot
- all the data would be shown in a one page interface, to simplify browsing and discovery; this poses UI challenges to make the page usable and looking clean.
- all data would be provided through the Live! plugin API.
- there is an open question on how to refresh visits for which visitors view a new page. For example, we could highlight the visit row in yellow background and add the new page row below the visit. Or we could automatically move the visit with the new page view at the top of the page and highlight (eg. yellow background) the new page view.
**in V2**
- on the right of the spy, or on a different "spy page", we could show a auto-refreshing google map with the new visits in real time. see #5466
Any feedback? Anybody would like to help implementing this interesting new plugin and UI challenge?
| Finish the Plugin Live! Reports detailed information on the last N visitors | https://api.github.com/repos/matomo-org/matomo/issues/5464/comments | 38 | 2008-01-03T20:30:46Z | 2014-07-08T10:16:42Z | https://github.com/matomo-org/matomo/issues/5464 | 37,356,115 | 5,464 |
[
"matomo-org",
"matomo"
] | We want to be able to exclude a list of IPs, and/or a list of IP ranges (using _._.123.34 notation) from being tracked by Piwik.
The list of IPs to exclude would be stored in the website cache file (where goals and alias URLs are stored).
In the UI, the feature should be available
- general exclusion list (only available to the super user): would apply to all website registered in Piwik, would need their own cache file (that applies to all websites)
- for each website, we can define a list of IPs. All IPs in this list + in the general list are checked at each Piwik request.
As an inline help, the UI would show the user current IP that he could copy paste in the list.
The UI would call the API in JSON (like the existing screens).
The UI for this feature should be designed to be part of a "preference page" for a website, as we need to add several new preferences for each website: #41, #42, #43, #56. Ideally, all the UI would be ajax (very quick to go from the list of websites in the admin UI, to load one website details page, to come back to the list of websites).
Outstanding question: should it be in the SiteManager plugin, or a new plugin? Should it be part of the core (to minimize overhead of loading plugins at Tracker time...)
| Plugin to exclude the webmaster based on IP or IP range | https://api.github.com/repos/matomo-org/matomo/issues/5463/comments | 9 | 2008-01-03T20:23:56Z | 2014-07-08T10:16:41Z | https://github.com/matomo-org/matomo/issues/5463 | 37,356,114 | 5,463 |
[
"matomo-org",
"matomo"
] | Feature available in phpMyVisites.
The plugin makes it easy to create a cookie so that visits by the piwik user are not registered in the piwik.php process and not counted in the statistics.
The plugin would hook during the installation process and make the cookie by default (opt out)[[Image()]]
| Plugin to exclude the webmaster based on a cookie | https://api.github.com/repos/matomo-org/matomo/issues/5462/comments | 13 | 2008-01-03T20:22:44Z | 2014-07-08T10:16:41Z | https://github.com/matomo-org/matomo/issues/5462 | 37,356,113 | 5,462 |
[
"matomo-org",
"matomo"
] | This feature in phpMyVisites was very useful.
It is mostly used on websites with no readable URLs (?module=news&newsid=14&action=view)
The plugin would provide:
- exclude given parameters from URLs
- include only given parameters
- exclude all parameters during statistics logging
This feature would be available:
- "exclude parameters" would be available
*\* in a general list applying to all websites (by default it would exclude PHPSESSID, jsessionid, SESSIONID, etc.)
*\* at the website level: each website define their own parameters to exclude (evaluated on top of the global list)
- "Include only given parameters" available for each website
- "Exclude all parameters" available for each website
- by default, Piwik campaigns parameter would be excluded from URLs
The UI would call the API directly, hence ensuring that all these features are available through the UI too.
For example the url`
example.com/page/index.php?userid=8571498752487&module=homepage` could be`
example.com/page/index.php?module=homepage` after removing the userid parameter.
The UI for this feature should be designed to be part of a "preference page" for a website, as we need to add several new preferences for each website: #41, #42, #43, #56. Ideally, all the UI would be ajax (very quick to go from the list of websites in the admin UI, to load one website details page, to come back to the list of websites).
Outstanding question: should it be in the SiteManager plugin, or a new plugin? Should it be part of the core (to minimize overhead of loading plugins at Tracker time...)
| Plugin to exclude / include only some Urls parameter | https://api.github.com/repos/matomo-org/matomo/issues/5461/comments | 11 | 2008-01-03T20:21:08Z | 2014-07-08T10:16:40Z | https://github.com/matomo-org/matomo/issues/5461 | 37,356,111 | 5,461 |
[
"matomo-org",
"matomo"
] | This plugins is heavily requested by the community (http://feedback.phpmyvisites.net/feedbacks/3135-external-link-clicks-statistics).
- Outlink tracking
- activation requires a flag in the javascript file + optional list of host alias for each site ID (so we don't save clicks on internal Urls)
- detects automatically the external links via some JS magic and record these clicks
- display the list of out clicks as actions in the piwik interface
- Download tracking
- activation requires a flag in the JS file
- detects automatically the clicks on files (given a list of extensions in the JS file : zip, exe, doc, pdf, etc. )
- display the list of downloads as actions in the piwik interface
| Outlink tracking, Download tracking plugin | https://api.github.com/repos/matomo-org/matomo/issues/5460/comments | 11 | 2008-01-03T20:12:31Z | 2014-07-08T10:16:40Z | https://github.com/matomo-org/matomo/issues/5460 | 37,356,110 | 5,460 |
[
"matomo-org",
"matomo"
] | Once the feature [Provide an easy way to access historical data in APIs](ticket:38) is done, we can generate RSS feeds for all the data in Piwik, at the same level as we currently generate CSV/XML reports.
We can imagine reports such as
- RSS feed of the best 10 keywords for the last days
- RSS feed of the best 50 refering websites for the last days
- any other report...
PS: at this point ATOM feeds would be just a few lines of code ahead obviously
| RSS feed output for every DataTable | https://api.github.com/repos/matomo-org/matomo/issues/5459/comments | 1 | 2008-01-03T20:03:10Z | 2014-07-08T10:16:40Z | https://github.com/matomo-org/matomo/issues/5459 | 37,356,109 | 5,459 |
[
"matomo-org",
"matomo"
] | This feature is very important.
Currently it is easy to get data for a given day for a given report.
We need to be able to easily access data for a set of dates, eg
- the last 30 days
- the last month
- the last week
- week 2
- month of march 2007
etc.
This has to be implemented in such a way that this is globally available to all APIs and plugins without hack. This is part of the core.
Once this feature is ready we can imagine to easily generate RSS feeds for everything, giving reports for the last N days (see #5459).
| Provide an easy way to access historical data in APIs | https://api.github.com/repos/matomo-org/matomo/issues/5458/comments | 2 | 2008-01-03T20:00:42Z | 2014-07-08T10:16:39Z | https://github.com/matomo-org/matomo/issues/5458 | 37,356,108 | 5,458 |
[
"matomo-org",
"matomo"
] | This test is very important as it will lead to necessary changes and optimization in
1. the DB design (index optimization, fields types)
2. the logging engine (how it behaves under heavy load, how the statistics logging can be optimized)
3. the archiving process (memory usage, saving computation time)
4. the interface (the DataTable scalable?)
This test will require to add new features such as
- [Add possibility to limit the number of rows saved in the datatable during the archiving](ticket:36)
| Test piwik on a 50,000+ visits per day website | https://api.github.com/repos/matomo-org/matomo/issues/5457/comments | 1 | 2008-01-03T19:54:09Z | 2014-08-03T11:21:09Z | https://github.com/matomo-org/matomo/issues/5457 | 37,356,107 | 5,457 |
[
"matomo-org",
"matomo"
] | Currently all the statistics are processed and nothing is pruned. However this is not necessary to keep all the statistics. In phpMyVisites we used a simple technique that worked well, we kept only the first N elements for each data (N ~ 300 for example).
For example we keep only the first 300 keywords. We keep the first 150 URLs referers.
This will lead to a big time and disk space saving for huge websites.
| Add possibility to limit the number of rows saved in the datatable during the archiving | https://api.github.com/repos/matomo-org/matomo/issues/5456/comments | 1 | 2008-01-03T19:50:47Z | 2014-07-08T10:16:39Z | https://github.com/matomo-org/matomo/issues/5456 | 37,356,106 | 5,456 |
[
"matomo-org",
"matomo"
] | The documentation needs to be reviewed by someone else and his feedback incorporated in the documentation.
See #5453.
This is part of the sub project "Make piwik easy to understand by someone new to the project".
| Make sure the phpDoc generated is complete, clear, useful | https://api.github.com/repos/matomo-org/matomo/issues/5454/comments | 1 | 2008-01-03T19:41:25Z | 2014-08-03T11:21:09Z | https://github.com/matomo-org/matomo/issues/5454 | 37,356,105 | 5,454 |
[
"matomo-org",
"matomo"
] | This is part of the sub project "Make piwik easy to understand by someone new to the project".
| write comprehensive phpDocumentation for all core classes | https://api.github.com/repos/matomo-org/matomo/issues/5453/comments | 6 | 2008-01-03T19:40:29Z | 2014-07-08T10:16:39Z | https://github.com/matomo-org/matomo/issues/5453 | 37,356,104 | 5,453 |
[
"matomo-org",
"matomo"
] | Currently all APIs in Piwik and Plugins are not versionned. This means that if people start using the APIs and if the developpers decide to change some parameters in the method calls, the software would stop working.
This is annoying and not a good practise. We need to have a way to provide a backward compatibility APIs. There are simple ways to do it, like adding a new parameter "version" to every function call, or prefixing the API URL by the version number.
| API should provide a backward compatibility feature | https://api.github.com/repos/matomo-org/matomo/issues/5452/comments | 1 | 2008-01-03T19:10:45Z | 2014-07-08T10:16:39Z | https://github.com/matomo-org/matomo/issues/5452 | 37,356,103 | 5,452 |
[
"matomo-org",
"matomo"
] | Plugins should be easy to update from one version to another.
We could use the same system as we are planning to use for the Piwik core (see [Process to update the Piwik software easily](ticket:30)).
| Process to update a plugin | https://api.github.com/repos/matomo-org/matomo/issues/5451/comments | 1 | 2008-01-03T18:59:20Z | 2014-07-08T10:16:39Z | https://github.com/matomo-org/matomo/issues/5451 | 37,356,102 | 5,451 |
[
"matomo-org",
"matomo"
] | This feature could be implemented as in phpMyVisites (it works well)
It makes it easy and secure to update from one version to another.
The software checks that the version in the database is the same as the version in the version.php.
If the version.php has a newer version, we update the database with all the changes that were done between both versions.
We can also execute some random php code as every version provides a file containing the changes to apply. This way of doing things is easy and very modular (you can do what you want during the update).
**Display version number**
Task also include display the version number somewhere in the admin UI, in the META tags on all piwik generated pages, an in the error/exception messages.
**To do by default in first piwik release that has update feature**
when updating from previous to first version with update system we need to:
- create indices now created at install: see comment below
- purge old archive tables containing temporary archive data
- remove cookie detection as it is completely wrong
- remove color_depth field
- alter table piwik_site and remove the update CURRENT_TIME
| Process to update piwik | https://api.github.com/repos/matomo-org/matomo/issues/5450/comments | 2 | 2008-01-03T18:57:50Z | 2014-07-08T10:16:39Z | https://github.com/matomo-org/matomo/issues/5450 | 37,356,101 | 5,450 |
[
"matomo-org",
"matomo"
] | We have to finish the development of the !OpenAds plugin.
- using the ../../openads_piwik_bridge class,
- do the prototype to make sure we can print the piwik image with DOM from the header
- update the openads_piwik_bridge class comment and the specification
- test using the openads interface
| OpenAds plugin development | https://api.github.com/repos/matomo-org/matomo/issues/5449/comments | 0 | 2008-01-03T18:53:13Z | 2014-08-03T11:21:09Z | https://github.com/matomo-org/matomo/issues/5449 | 37,356,100 | 5,449 |
[
"matomo-org",
"matomo"
] | In the piwik.php process, we could do without all the information in the cookie except for the idvisitor. We could select the information last_action_time, last_id_action, etc. assuming we have the idvisitor in the cookie ; this would allow to save the logs in the DB later by big bulk and save a lot of time.
| piwik.php optimization using cookie information | https://api.github.com/repos/matomo-org/matomo/issues/5448/comments | 1 | 2008-01-03T18:51:25Z | 2014-07-08T10:16:39Z | https://github.com/matomo-org/matomo/issues/5448 | 37,356,099 | 5,448 |
[
"matomo-org",
"matomo"
] | Currently piwik display a warning message asking the user to create the database.
But it could try to create it itself and if it fails, display the warning message.
| When the database doesn't exist, piwik could try to create it | https://api.github.com/repos/matomo-org/matomo/issues/5447/comments | 2 | 2008-01-03T18:44:09Z | 2014-08-03T11:21:09Z | https://github.com/matomo-org/matomo/issues/5447 | 37,356,098 | 5,447 |
[
"matomo-org",
"matomo"
] | In the config.ini.php, it is not possible to set a configuration settings in a config file without setting the whole category in this config file.
We should have some sort of merging that would make possible to set only a sub configuration variable from the global.ini.php into the config.ini.php. This way, during an upgrade, we could keep only the config/config.ini.php and overwrite the other config files with the updated piwik version and we would keep the user changes.
Example
In global.ini.php
[Test]
value1=test1
value2=test2
In config.ini.php it is NOT YET possible to change only value1 doing something like
[Test]
value1=test1edited
Currently the user has to paste the whole category to change only this variable
[Test]
value1=test1edited
value2=test2
| The user config file cannot only define a variable, it has to define the whole "category" of variables | https://api.github.com/repos/matomo-org/matomo/issues/5446/comments | 2 | 2008-01-03T18:42:32Z | 2024-01-03T05:03:47Z | https://github.com/matomo-org/matomo/issues/5446 | 37,356,097 | 5,446 |
[
"matomo-org",
"matomo"
] | The method name is not consistent with the rest of the application naming style.
| Rename setColumnsToDisplay() to setColumnsIdsToDisplay() for consistency | https://api.github.com/repos/matomo-org/matomo/issues/5445/comments | 4 | 2008-01-03T18:39:07Z | 2014-07-08T10:16:39Z | https://github.com/matomo-org/matomo/issues/5445 | 37,356,096 | 5,445 |
[
"matomo-org",
"matomo"
] | We have to make it easy for plugins to have their own Configuration file, the same way they have their own translation file, etc.
| Plugins should have easy access to their own configuration file | https://api.github.com/repos/matomo-org/matomo/issues/5444/comments | 4 | 2008-01-03T18:37:38Z | 2024-01-03T10:00:34Z | https://github.com/matomo-org/matomo/issues/5444 | 37,356,095 | 5,444 |
[
"matomo-org",
"matomo"
] | Using the magic keywords for the date GET parameter has not been fully tested yet.
We need to test to archive days, weeks, months, using the today/yesterday magic keywords.
| Check that using the date parameters magic keywords "today" "yesterday" is bug free | https://api.github.com/repos/matomo-org/matomo/issues/5443/comments | 0 | 2008-01-03T18:36:10Z | 2009-08-18T19:04:29Z | https://github.com/matomo-org/matomo/issues/5443 | 37,356,094 | 5,443 |
[
"matomo-org",
"matomo"
] | We have to ensure that all parameters in the API methods are all checked against security rules and sanitized.
| Ensure that all parameters to the API are checked against security rules | https://api.github.com/repos/matomo-org/matomo/issues/5442/comments | 0 | 2008-01-03T16:53:51Z | 2010-01-29T15:46:04Z | https://github.com/matomo-org/matomo/issues/5442 | 37,356,093 | 5,442 |
[
"matomo-org",
"matomo"
] | This would improve the package size, the interface loading speed, solve problems PNG has with transparency support under IE, etc. and GIF is now patent free.
| Convert all PNG images to GIF | https://api.github.com/repos/matomo-org/matomo/issues/5441/comments | 1 | 2008-01-03T16:53:09Z | 2014-07-08T10:16:38Z | https://github.com/matomo-org/matomo/issues/5441 | 37,356,092 | 5,441 |
[
"matomo-org",
"matomo"
] | Archive::build() must have the same parameters order as all the API calls that use idSite, Period, Date.
| Archive::build() parameters order is not consistent with API | https://api.github.com/repos/matomo-org/matomo/issues/5440/comments | 3 | 2008-01-03T16:51:52Z | 2014-07-08T10:16:38Z | https://github.com/matomo-org/matomo/issues/5440 | 37,356,091 | 5,440 |
[
"matomo-org",
"matomo"
] | It would make the logging script faster and with a better memory usage.
| when the plugins are not used in the piwik.php logging script, don't load the related files | https://api.github.com/repos/matomo-org/matomo/issues/5439/comments | 1 | 2008-01-03T16:51:09Z | 2014-07-08T10:16:38Z | https://github.com/matomo-org/matomo/issues/5439 | 37,356,090 | 5,439 |
[
"matomo-org",
"matomo"
] | By some magically bad code using jquery, we could end up doing ajax requests several times when clicking several times, or when clicking one time would trigger the Ajax request multiple times.
The JS code needs to be checked to make sure the number of Ajax requests is optimal.
| Check ajax calls are made only once per request | https://api.github.com/repos/matomo-org/matomo/issues/5438/comments | 1 | 2008-01-03T16:50:14Z | 2014-07-08T10:16:38Z | https://github.com/matomo-org/matomo/issues/5438 | 37,356,089 | 5,438 |
[
"matomo-org",
"matomo"
] | When sorting the !DataTable columns, the width are changing under Opera 9.23. It is a visually annoying effect.
| Columns width are changing under Opera 9.23 | https://api.github.com/repos/matomo-org/matomo/issues/5437/comments | 0 | 2008-01-03T16:43:04Z | 2010-01-29T15:35:27Z | https://github.com/matomo-org/matomo/issues/5437 | 37,356,087 | 5,437 |
[
"matomo-org",
"matomo"
] | In the Actions plugin, expanding or collapsing doesn't work.
It always expands.
Multiple clicks load the content multiple times.
| Actions expand/collapse doesn't work under Opera 9.23 | https://api.github.com/repos/matomo-org/matomo/issues/5436/comments | 0 | 2008-01-03T16:42:13Z | 2010-01-29T15:38:21Z | https://github.com/matomo-org/matomo/issues/5436 | 37,356,086 | 5,436 |
[
"matomo-org",
"matomo"
] | The icon under the Tag Cloud / Graph / Table is currently not hidden ; this is not user friendly.
| When a given output is chosen (for example Tag Cloud) the corresponding icon should be hidden | https://api.github.com/repos/matomo-org/matomo/issues/5435/comments | 0 | 2008-01-03T16:40:58Z | 2010-01-29T15:39:47Z | https://github.com/matomo-org/matomo/issues/5435 | 37,356,085 | 5,435 |
[
"matomo-org",
"matomo"
] | Searching on countries should search on the final label, ie. the country name.
Currently the search is done on the ISO code.
This is a limitation of the DataTable class and it should be fixed. The developer should be able to define the field on which the search takes place.
| Searching on countries within the DataTable is not working properly | https://api.github.com/repos/matomo-org/matomo/issues/5434/comments | 1 | 2008-01-03T16:37:39Z | 2014-07-08T10:16:38Z | https://github.com/matomo-org/matomo/issues/5434 | 37,356,084 | 5,434 |
[
"matomo-org",
"matomo"
] | For example a user loading piwik under PHP4 would be surprised to see that nothing is working and that there is no error message.
It would be good to display the error message in a nice interface.
| The minimum PHP version should be checked | https://api.github.com/repos/matomo-org/matomo/issues/5433/comments | 3 | 2008-01-03T16:35:39Z | 2014-07-08T10:16:38Z | https://github.com/matomo-org/matomo/issues/5433 | 37,356,083 | 5,433 |
[
"matomo-org",
"matomo"
] | Handling the images.google.x is different from the other search engines.
Indeed we need to read the prev GET variable and then read the q GET variable, which gives the keyword.
See trunk/modules/LogStats/Visit.php getRefererInformation()
| images.google.x is not counted as a search engine | https://api.github.com/repos/matomo-org/matomo/issues/5432/comments | 1 | 2008-01-03T16:34:00Z | 2014-07-08T10:16:38Z | https://github.com/matomo-org/matomo/issues/5432 | 37,356,082 | 5,432 |
[
"matomo-org",
"matomo"
] | If the user deletes some lines from the config.ini.php file, there should be a warning message asking the user to add the lines that were deleted (helping the user giving the default values for example).
Or shall we use some default values contained in a "default" configuration file?
| Deleted elements from the configuration file should raise a warning | https://api.github.com/repos/matomo-org/matomo/issues/5431/comments | 2 | 2008-01-03T16:32:38Z | 2014-08-03T11:21:09Z | https://github.com/matomo-org/matomo/issues/5431 | 37,356,081 | 5,431 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.