| Age | Commit message (Collapse) | Author |
|---|
|
:tada: time to party!! :tada:
|
|
|
|
|
|
|
|
|
|
|
|
* Replace all occurences of Piwik in english translations of Actions plugin
* translation update
* Replace all occurences of Piwik in english translations of API plugin
* translation update
* Replace all occurences of Piwik in english translations of core
* replace Piwik occurrences
* Rename widget piwik.org blog => matomo.org blog
* fix widget name
* replaced some more piwik mentions
* Renamed to Matomo a few strings
* Replaced more strings to Matomo in JSON files, twig templates
* Replaced more strings to Matomo in INI file
* Replaced more strings to Matomo in API docs, error messages, feedback forms
* introduce API.getMatomoVersion and ExampleAPI.getMatomoVersion API + deprecate old ones
|
|
* renaming more Piwik mentions
* some more updates
* fix some tests
* support matomo partially as require string
* fix tests
* fix failing system test
* fix tests
* fix system test
* fix test
|
|
|
|
(#12401)
so we do not show the stack trace in that case, follows up https://github.com/piwik/piwik/pull/12357
eg on https://demo.piwik.org/?module=API&method=VisitsSummary.getVisits&idSite=1&period=day&date=last10&format=xmls&token_auth=x
|
|
|
|
|
|
* respect encoded entities in truncate filter
* adds some simple tests
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* If a period is filtered out, the result of the periods array becomes an object which breaks the period selector which expects an array.
* Use $onInit instead of directive constructor. Seems angular.js silences errors when this is done.
* Parse previousN/lastN dates correctly in angular periods service.
* Parse periods using piwikPeriods client side, since we cannot assume a date range. Also if an invalid is used for period/date, display ERROR in the period selector.
* Angular will swallow errors from datepicker.parseDate, so add a console.log for developer sanity + make sure period selector has consistent state even when period/date values are invalid (& result in failed date parsing).
* Update misc/log-analytics submodule to latest.
|
|
* New "Event URL" segment `eventUrl` to segment on any Segment URL
Useful for many use cases for example:
* Creating Custom Reports such as "Top page URLs by Event action"
* Segmenting by Event URL and view events triggered on a specific Page URL
* Fixes #11131 Action URL segment could filter both Page URLs OR Event URLs (as advertised originally in the 2.16.0 changelog but it wasn't actually fully working yet)
* fix typo no capital letter
* remove column type to prevent new column being created in the log_link_visit_action table
* set correct action type for segment eventUrl
* modify test
* eventUrl needs action data
* fix suggested values for eventUrl
* update test files
* event url is stored without protocol
* update test file
|
|
* add possibility to restrict piwik login by ip
* better whitelist implementation
* move classes to corehome
* better error message
* better config
* make sure ips can be overwritten via DI
* fix ui tests
|
|
* Adds help screen for shortcuts
* Dynamically create shortcut summary by using new js method piwikHelper.registerShortcut
* Update CHANGELOG.md
|
|
|
|
(#12233)
* Extract mail configuring parts of sendReport method & write tests for them.
* Use twig in AttachedFileReportEmailGenerator.
* Extract header/footer of html scheduled report email into re-usable View subclasses & use for PDF/CSV emails.
* Fixing test failures.
* Integrationt est
|
|
|
|
* Improve serialize dataTable performance
This seems to improve the performance of serializing a data table which is useful when archiving. In my case it made the archiving of a monthly archive twice as fast from about 120 seconds down to like 70seconds.
* remove no longer needed variable
* faster check whether an array key is set
It is known that array_key_exists is quite a bit slower than `isset`. As this is executed easily a few million times this makes a difference in performance but here `array_key_exists` and `isset` work the same in logic as we never set `$consecutiveSubtableIds[$id]=null`
* Assignment should be no longer needed as passing by reference
|
|
There is no need to recursively iterate over all dataTables, when there is no column to rename.
|
|
InvalidateReports plugin (#12286)
* Minor changes to wording
* Add a mention to the InvalideReports plugin
|
|
As long as it does not create performance regression or impact, it would be really useful to have this by default in Piwik, makes it useful to troubleshoot archiving problems without having to patch this file and uncomment this logger line.
|
|
|
|
"rewrite ^/piwik/(.*)$ /$1 break;" (nginx.conf), you can provide a header "proxy_set_header X-Forwarded-Uri /piwik;" which will be considered to the current script name. (#12011)
It's necessary, because the redirect after login and links e.g. the logo are not working correctly without.
|
|
requests (#12207)
* Issue the CORS header (Access-Control-Allow-Origin) also on Tracking API requests
* Move CORS code to the Tracking API endpoint file
|
|
|
|
* Introduce config setting to show update notifications to superusers only. Fixes #7930
* By default, all users should see the update notification
* Changed description of config param
* Updates changelog
|
|
|
|
|
|
|
|
|
|
frontend (#11873)
* Add generate:angular-component command to generate an angular component.
* Do not modify Date prototype.
* Move period selector code from calendar.js to new angular directive (just move, no refactoring).
* Extract date picker code from period selector code and put into new directive.
* Extract range picking code into separate component than period selector.
* Extract single period calendar to separate component & extract period specific functionality to new extendable periods service.
* Fixing regressions in period selector behavior.
* Move bulk of period selector code from directive to controller, & fix variable name in date range picker template.
* Fix issue w/ yesterday date value, remove need to give period selector directive translations and make sure periods can be extended in the frontend.
* Make sure period selector still works outside of an angular routing context (ie, in embedded dashboard).
* In period selector UI test, hide ajaxLoadingCalendar using CSS since it is now managed by angular.
* Make sure selected period highlighting changes immediately after selecting, even if loading a new page.
* Put period selector top level element ID & classes on correct elements to ensure certain styles work properly.
* Make sure selected period text changes immediately after selecing period, even if loading a new page or changing the URL.
* Make sure range start/end changes immediately when a period is selected & selected period date range stops being highlighted immediately when a range period is selected, even if loading a new page.
* Updating expected screenshots.
* Updating screenshots.
* Assorted fixes for period selector refactor.
- Filter out invalid period labels (can happen if INI config for allowed periods is incorrect).
- When determining display text for range, don't try to format the startRangeDate/endRangeDate vars, they're both strings.
- Use correct selector when closing period selector.
* Set global piwik date/period values on location change, outside of period selector component.
* Do not skip parsing date if it does not start with an int (since the JS can handle today/yesterday/now).
* Assorted fixes for period selector refactor:
- use $onChanges instead of watches in datepicker (watches get triggered every time, $onChanges doesn't)
- don't use arrays for selected/highlighted dates (for some weird reason, changing one of these arrays results in angular thinking it changes 3 times instead of once)
- don't redraw on triggered mouseover events (something triggers mouseover when a date is selected, probably jquery datepicker)
- draw after a setTimeout when a date is selected so our drawing occurs after jquery datepicker draws
* Achieving smoother rendering for period selector by removing click handlers jquery datepicker adds.
Also fixed bug where selecting the current period type reset the view date for the date picker.
* Bound range date in period selector by piwik min/max date, so inferred dates will always be within allowed pickable dates in picker.
* Removing ES6 used by accident + fix for issue when switching from non-year to year period (ui-datepicker-current-day class does not get removed).
* Fix for angularjs one way binding quirk: initial property value is set before $onInit not during construction.
* Avoid an exception when a date input in the date range picker is empty.
* Split up change/keyup event to solve strange race condition in IE 10 on browserstack.
* Change period selector "click again" tooltip to "double click".
* Remove tabindexes > 1 so period selector control can be tabbed through.
* Show visual cue for invalid dates in date range picker.
* Only hide period option tooltip if period is active period, not if period is selected period.
* In period selector, disable apply button if range is invalid. Also fix case when \$.datepicker.parseDate returns null instead of throwing.
|
|
* http://piwik.org -> https://piwik.org
* more HTTPS URLs
* some more HTTPS URLs
* test README
* don't show "Plugin Hompage" for Piwik plugins
* fix tests
* compile minified js
(hope I didn't break anything)
* some more small changes
* fix UI test
* comment length in piwik.js changed due to https links
* fix test
* update ui file
* update submodule
|
|
|
|
|
|
|
|
|
|
* fix bugs in table sorting query builder
* fix tests
|
|
Remove the word Piwik from CSV download filenames
|
|
|
|
|
