Fixes #3220 When the core is not dispatching the request (PIWIK_ENABLE_DISPATCH is not set, or set to false), then getPiwikUrl will not update the value in the DB.
Thanks for the report & again sorry for such long delay to fix it!

Fixes #3116 If website is ecommerce, do not limit custom variables reports to 1,000 rows. Limit to 50,000 instead.

Let's see if build is still passing

this will make sure that visitFrequency, when calling VisitsSummary.get with a segment=visitorType==returning, then it will be pre-processed at all times by archive.php.

Fixes #2981 Calling API.get in CronArchive. This will result in VisitFrequency.get being called therefore pre-processed as well.

Moving back &_viewts affects the VisitFrequency, VisitorInterest reports and <daysSinceLastVisit> all work as expected.

Allow templates postEvent() calls to also pass parameters. For example this is done in the twig template:
```
{{ postEvent("Template.jsGlobalVariables", minDateYear, maxDateYear) }}
```
and you can hook on this event, by doing:
```
    public function addTrackingHostnamesToJs(&$out, $minDateYear, $maxDateYear)
    {
        // printout out the data as a comment for testing
        $out .= "/* " . $minDateYear . " - " . $maxDateYear . " */";
```

Updating: viewts, refts, idvc and idts. It affects visitCount and daysSinceLastVisit. There seems to be a bug.