- get rid of some irritating error messages during package build 
  by (build) requiring:
  + php-pdo
  + php-iconv
  + php-mbstring
  Not really needed, but this reduces the error message to an error 
  message about a non-existing MySQL connection during build

• Files Changed
• Browse Source

- Update to 4.3.1
  + This release focuses on stability and reliability.
  + In terms of new features, under Evolution graphs, you can now 
    easily change the period shown in the graph.
  + Overall, over 140 tickets have been closed. Many small 
    improvements were made to the report generation in terms of 
    reliability and performance especially with relation to invalidating 
    older reports, and when there are many segments or websites.
  Some examples:
  #16776 When accessing UI with unsupported browser throw error 
         and suggest to use other browser
  #17488 Remove the “Visitor ID” segment when the “Visitor profile” 
         feature has been disabled
  #17242 Performance report table not displayed properly
  #17301 Store the segment hash in the DB table
  #17259 Performance metrics issues after 4.2 update
  #17374 Row evolution on subtables can cause errors randomly
  #17497 Re-allow tracking bots
  #17519 Allow invalidating empty site

• Files Changed
• Browse Source

- Update to 4.3.0
  + This release focuses on stability and reliability.
  + In terms of new features, under Evolution graphs, you can now 
    easily change the period shown in the graph.
  + Many small improvements were made to the archiving in terms of 
    reliability and performance especially with relation to 
    invalidating older reports, and when there are many segments 
    or websites.
  + We are grateful for all community members who reported feedback 
    and suggestions, our awesome team of translators for their work, 
    and our Premium features customers and Matomo Cloud hosting 
    customers for their amazing support.
  + 141 tickets have been closed by more than 19 contributors!
  Some examples:
  #17242 Performance report table not displayed properly 
  #15021 Show periods labels in the evolution graphs to make it 
         easier to change period 
  #17259 Performance metrics issues after 4.2 update
  #17285 Ask for password confirmation before installing all plugins 
  #17503 detect brute force login attempts from different ip addresses
  #17497 Re-allow tracking bots
  #16790 When a period has no data, but raw data, show a message
  #15203 France regions are not up-to-date
  #17364 check for openssl extension
  #17537 add new ini config to enable/disable the php profiler feature

• Files Changed
• Browse Source

- Update to 4.2.1
  All cookies created by the Matomo User Interface are now httpOnly 
  for added security (so far the matomo_lang cookie was not). 
  This new release also addresses minor archiving related issues and 
  prevents a possible error message during upgrade to 4.2.0. 
  Also many new devices brands, browsers and podcast apps are now 
  detected by Device Detector.
  33 tickets have been closed by more than 6 contributors! 
  Some examples:
  #17253 Critical error during database upgrade “The date ‘-0001-11-30’
   is a date before first website was online” when updating to 4.2.0
  #6689 Don’t use numeric keys as it breaks using Symfony YAML 
  #6692 hotfix incorrect YAML attribute `name` in mobile-app.yml

• Files Changed
• Browse Source

  + This release focuses on stability and reliability and security
  + A new ? (question mark) icon is now visible next to report names 
    in the left menu. Clicking on this icon will display a helpful 
    text explaining “Why” this particular report is useful.
  + A major security issue (but not critical) has already been fixed
    We fixed an issue where a Super User (and only a Super User) may 
    have been able to get a remote code execution on the Matomo server. 
    Since this was only exploitable by Super Users (who are considered
    trusted), we consider it a minor issue.

• Files Changed
• Browse Source

- Update to 4.2.0
  + many new devices added to the detection engine
  + 137 tickets closed. Some of them:
  #17159 Tracking requests might not be loaded because of CORB 
  #17077 Anonymous user settings not working after v4 upgrade 
  #17099 Real-Time Map description switches to "There is no data for this report." 
  #10881 Error page served with HTTP 200 status
  #17153 Tracking requests on PHP 8 might fail if an invalid encoding is sent 
  #17205 CustomLogo upload not working with PHP8
  #17062 Display help icons for categories/subcategories 
  #17115 Display the name of the user being edited
  #17121 Improve compatibility with jQuery 3 
  #17185 archiving job runs forever due to MultiChannelConversionAttribution
  #17233 Prevent possible error when accessing an index 
  #244 Added new command line option '--php-binary' 
  #287 Add consent methods to Matomo Tag Manager 
  #6467 Adds detection for Flow browser engine and for Flow browser

• Files Changed
• Browse Source

- Update to 4.1.1
  There are few small improvements in the user experience. Every 
  report in Matomo now has a report description (we’ll keep improving
  the help messages over time).
  In the Administration section, the menu is now collapsible, so 
  you can find the menu you need more easily.
  This release also includes fixes for regressions (and some minor 
  bugs), including one where reports processing was not working in 
  some cases when a segment was applied. And more devices are now 
  detected.
  A new plugin has also been published called Tracking Spam prevention,
  to help prevent Visits and Pageviews spam. Get the free and open 
  source Tracking Spam Prevention plugin from the Marketplace. This 
  plugin offers various options to prevent spammers and bots from 
  making your data inaccurate so you can rely on your data again

• Files Changed
• Browse Source

• Files Changed
• Browse Source

move some defines after the header, to work with SLE12

• Files Changed
• Browse Source

- (temporary?) ignore piwik.min.js and vendor/wikimedia/less.php/bin/lessc
  in manifest checks

• Files Changed
• Browse Source

- require php-intl (new dependency in 4.x)

• Files Changed
• Browse Source

- Update to 4.1.0
  In this release we’re mostly addressing bugs that were reported in
  the previous releases and also making minor small improvements. 
  * 61 tickets closed in Matomo 4.1.0
    see https://matomo.org/changelog/matomo-4-1-0/ for details

• Files Changed
• Browse Source

- Update to 4.0.3
  + Change referrer url size to 1500 (#16835)
  + Trim referrer url if needed (#16836)
  + Create robots.txt to prevent bots from indexing Matomo app (#16795)
  + Improve php8 compatibility (#16838)
  + re-add missing condition for --skip-segments-today (#16777)

• Files Changed
• Browse Source

- Update to 4.0.2
  Breaking changes in Matomo JS tracker
  + Matomo no longer polyfills the JSON object in the JavaScript tracker. 
    This means IE7 and older, Firefox 3 and older will be no longer 
    suppported in the tracker.
  + The JavaScript tracker now uses sendBeacon by default if supported 
    by the browser. You can disable this by calling the tracker method
    disableAlwaysUseSendBeacon. As a result, callback parameters won't
    work anymore and a tracking request might not appear in the developer
    tools. This will improve the load time of your website.
  + The JS tracker event PiwikInitialized has been renamed to MatomoInitialized
  + Support for tracking and reporting of these browser plugins has been
    discontinued: Gears, Director
  + Plugins that extend the JS tracker should now add their callback to
    matomoPluginAsyncInit instead of piwikPluginAsyncInit
  + The visitor ID cookie now contains less data (due to the _idvc, _idts, 
    _viewts and _ects tracking parameters no longer being used). 
    This is a breaking change if you use the Matomo PHP Tracker and forward 
    the visitor cookie to it, and you will need to upgrade the PHP tracker
    to use with Matomo 4.
  + The tracker method setVisitStandardLength has been removed as there 
    is no need for it anymore.
  Deprecations in Matomo JS tracker
  + The JS Tracker method getPiwikUrl has been deprecated and getMatomoUrl
    should be used instead.
  + The JS Tracker init method piwikAsyncInit has been deprecated and 
    matomoAsyncInit should be used instead.
  + The JS object window.Piwik has been deprecated and window.Matomo 
    should be used instead.
  Recommendations for Matomo JS tracker

• Files Changed
• Browse Source

• Files Changed
• Browse Source

• Files Changed
• Browse Source

• Files Changed
• Browse Source

• Files Changed
• Browse Source

trigger service run

• Files Changed
• Browse Source

• Files Changed
• Browse Source