This is a changelog for Piwik platform developers. All changes for our HTTP API's, Plugins, Themes, etc will be listed here.
- New segment
actionType
lets you segment all actions of a given type, eg.actionType==events
oractionType==downloads
. Action types values are:pageviews
,contents
,sitesearches
,events
,outlinks
,downloads
- The JavaScript Tracker method
PiwikTracker.setDomains()
can now handle paths. This means when setting eg_paq.push(['setDomains, '*.piwik.org/website1'])
all link that goes to the same domainpiwik.org
but to any other path thanwebsite1/*
will be treated as outlink. - It is now possible to pass an option
php-cli-options
to thecore:archive
command. The given cli options will be forwarded to the actual PHP command. This allows to for example specifiy a different memory limit for the archiving process like this:./console core:archive --php-cli-options="-d memory_limit=8G"
- New less variable
@theme-color-menu-contrast-textSelected
that lets you specify the color of a selected menu item.
- When generating a new plugin skeleton via
generate:plugin
command, plugin name must now contain only letters and numbers. - JavaScript Tracker tests no longer require
SQLite
. The existing MySQL configuration for tests is used now. In order to run the tests make sure Piwik is installed and[database_tests]
is configured inconfig/config.ini.php
. - The definitions for search engine and social network detection have been moved from bundled data files to a separate package (see https://github.com/piwik/searchengine-and-social-list).
- In UI screenshot tests, a test environment
configOverride
setting should be no longer overwritten. Instead new values should be added to the existingconfigOverride
array in PHP or JavaScript. For example instead oftestEnvironment.configOverride = {group: {name: 1}}
usetestEnvironment.overrideConfig('group', 'name', '1')
.
- Add your own SMS/Text provider by creating a new class in the
SMSProvider
directory of your plugin. The class has to extendPiwik\Plugins\MobileMessaging\SMSProvider
and implement the required methods. - Segments can now be composed by a union of multiple segments. To do this set an array of segments that shall be used for that segment
$segment->setUnionOfSegments(array('outlinkUrl', 'downloadUrl'))
instead of defining a SQL column.
- The method
DB::tableExists
was un-used and has been removed.
- New command
config:set
lets you set INI config options from the command line. This command can be used for convenience or for automation.
- In Administration > Websites, for each website, there is a checkbox "Only track visits and actions when the action URL starts with one of the above URLs". In Piwik 2.14.0, any action URL starting with one of the Alias URLs or starting with a subdomain of the Alias URL would be tracked. As of Piwik 2.15.0, when this checkbox is enabled, it may track less data: action URLs on an Alias URL subdomain will not be tracked anymore (you must specify each sub-domain as Alias URL).
- New command
diagnostics:analyze-archive-table
that analyzes archive tables - New command
database:optimize-archive-tables
to optimize archive tables and possibly save disk space (even if on InnoDB) - New Command
core:invalidate-report-data
to invalidate archive data (w/ period cascading) (FAQ)
- Piwik 2.15.0 is now mostly compatible with PHP7.
- The JavaScript Tracker
piwik.js
got a new methodlogAllContentBlocksOnPage
to log all found content blocks within a page to the console. This is useful to debug / test content tracking. It can be triggered via_paq.push(['logAllContentBlocksOnPage'])
- The Class
Piwik\Plugins\Login\Controller
is now considered a public API. - The new method
Piwik\Menu\MenuAbstract::registerMenuIcon()
can be used to define an icon for a menu category to replace the default arrow icon. - New event
CronArchive.getIdSitesNotUsingTracker
that allows you to set a list of idSites that do not use the Tracker API to make sure we archive these sites if needed. - New events
CronArchive.init.start
which is triggered when the CLI archiver starts andCronArchive.end
when the archiver ended. - Piwik tracker can now be configured with strict Content Security Policy (CSP FAQ).
- Super Users can choose whether to use the latest stable release or latest Long Term Support release.
- The method
Dimension::getId()
has been set asfinal
. It is not allowed to overwrite this method. - We fixed a bug where the API method
Sites.getPatternMatchSites
only returned a very limited number of websites by default. We now return all websites by default unless a limit is specified specifically. - Handling of localized date, time and range formats has been changed. Patterns no longer contain placeholders like %shortDay%, but work with CLDR pattern instead. You can use one of the predefined format constants in Date class for using getLocalized().
- As we are now using CLDR formats for all languages, some time formats were even changed in english. Attributes like prettyDate in API responses might so have been changed slightly.
- The config
enable_measure_piwik_usage_in_idsite
which is used to track the Piwik usage with Piwik was removed and replaced by a new pluginAnonymousPiwikUsageMeasurement
- The following HTTP API methods have been deprecated and will be removed in Piwik 3.0:
SitesManager.getSitesIdWithVisits
API.getLastDate
- The following events have been deprecated and will be removed in Piwik 3.0. Use dimensions instead.
Tracker.existingVisitInformation
Tracker.getVisitFieldsToPersist
Tracker.newConversionInformation
Tracker.newVisitorInformation
Tracker.recordAction
Tracker.recordEcommerceGoal
Tracker.recordStandardGoals
- The Platform API method
\Piwik\Plugin::getListHooksRegistered()
has been deprecated and will be removed in Piwik 3.0. Use\Piwik\Plugin::registerEvents()
instead.
- When logging in, the username is now case insensitive
- URLs with emojis and any other unicode character will be tracked, with special characters replaced with
�
- A permanent warning notification is now displayed when PHP is 5.4.* or older, since it has reached End Of Life
- In
piwik.js
we replaced JSON2 with JSON3 to implement CSP (Content Security Policy) as JSON3 does not useeval()
. JSON3 will be used if a browser does not provide a native JSON API. We are usingJSON3
in a way that it will not conflict if your website is usingJSON3
as well. - The option
branch
of the console commanddevelopment:sync-system-test-processed
was removed as it is no longer needed. - All numbers in reports will now appear formatted (eg.
1,000,000
instead of1000000
) - Database connections now use
UTF-8
charset explicitely to force UTF-8 data handling
- The
UserSettings
API has been removed. The API was deprecated in earlier versions. UseDevicesDetection
,Resolution
andDevicePlugins
API instead. - Many translations have been moved to the new Intl plugin. Most of them will still work, but please update their usage. See matomo-org#8101 for a full list
- The JavaScript Tracker does now track outlinks and downloads if a user opens the context menu if the
enabled
parameter of theenableLinkTracking()
method is set totrue
. To use this new feature usetracker.enableLinkTracking(true)
or_paq.push(['enableLinkTracking', true]);
. This is not industry standard and is vulnerable to false positives since not every user will select "Open in a new tab" when the context menu is shown. Most users will do though and it will lead to more accurate results in most cases. - The JavaScript Tracker now contains the 'heart beat' feature which can be used to obtain more accurate visit lengths by periodically sending 'ping' requests to Piwik. To use this feature use
tracker.enableHeartBeatTimer();
or_paq.push(['enableHeartBeatTimer']);
. By default, a ping request will be sent every 15 seconds. You can specify a custom ping delay (in seconds) by passing an argument, eg,tracker.enableHeartBeatTimer(10);
or_paq.push(['enableHeartBeatTimer', 10]);
. - New custom segment
languageCode
that lets you segment visitors that are using a particular language. Example values:de
,fr
,en-gb
,zh-cn
, etc. - Segment
userId
now supports any segment operator (previously only operator Contains=@
was supported for this segment).
- The command
core:archive
now has two new parameter:--force-idsegments
and--skip-idsegments
that let you force (or skip) processing archives for one or several custom segments. - The command
scheduled-tasks:run
now has an argumenttask
that lets you force run a particular scheduled task.
- Updated pChart library from 2.1.3 to 2.1.4. The files were moved from the directory
libs/pChart2.1.3
tolibs/pChart
- To execute UI tests "ImageMagick" is now required.
- The Q JavaScript promise library is now distributed with tests and can be used in the piwik.js tests.
- The API method
Live.getLastVisitsDetails
does no longer support the API parameterfilter_sort_column
to prevent possible memory issues whenfilter_offset
is large. - The Event
Site.setSite
was removed as it causes performance problems. piwik.php
does now return a HTTP 400 (Bad request) if requested without any tracking parameters (GET/POST). If you still want to usepiwik.php
for checks please usepiwik.php?rec=0
.
- The method
Piwik\Archive::getBlob()
has been deprecated and will be removed from June 1st 2015. Use one of the methodsgetDataTable*()
methods instead. - The API parameter
countVisitorsToFetch
of the API methodLive.getLastVisitsDetails
has been deprecated asfilter_offset
andfilter_limit
work correctly now.
- There is now a
diagnostic:run
command to run the system check from the command line. - There is now an option
--xhprof
that can be used with any command to profile that command via XHProf.
- Visitor details now additionally contain:
deviceTypeIcon
,deviceBrand
anddeviceModel
- In 2.6.0 we added the possibility to use
filter_limit
andfilter_offset
if an API returns an indexed array. This was not working in all cases and is fixed now. - The API parameter
filter_pattern
andfilter_offset[]
can now be used if an API returns an indexed array.
- The referrer spam filter has moved from the
referrer_urls_spam
INI option (inglobal.ini.php
) to a separate package (see https://github.com/piwik/referrer-spam-blacklist).
- The deprecated method
Period::factory()
has been removed. UsePeriod\Factory
instead. - The deprecated method
Config::getConfigSuperUserForBackwardCompatibility()
has been removed. - The deprecated methods
MenuAdmin::addEntry()
andMenuAdmin::removeEntry()
have been removed. UsePiwik\Plugin\Menu
instead. - The deprecated methods
MenuTop::addEntry()
andMenuTop::removeEntry()
have been removed. UsePiwik\Plugin\Menu
instead. - The deprecated method
SettingsPiwik::rewriteTmpPathWithInstanceId()
has been removed. - The following deprecated methods from the
Piwik\IP
class have been removed, usePiwik\Network\IP
instead:sanitizeIp()
sanitizeIpRange()
P2N()
N2P()
prettyPrint()
isIPv4()
long2ip()
isIPv6()
isMappedIPv4()
getIPv4FromMappedIPv6()
getIpsForRange()
isIpInRange()
getHostByAddr()
API
classes should no longer have a protected constructor. Classes with a protected constructor will generate a notice in the logs and should expose a public constructor instead.- Update classes should not declare static
getSql()
andupdate()
methods anymore. It is still supported to use those, but developers should instead override theUpdates::getMigrationQueries()
andUpdates::doUpdate()
instance methods.
API
classes can now use dependency injection in their constructor to inject other instances.
- There is now a command
core:purge-old-archive-data
that can be used to manually purge temporary, error-ed and invalidated archives from one or more archive tables. - There is now a command
usercountry:attribute
that can be used to re-attribute geolocated location data to existing visits and conversions. If you have visits that were tracked before setting up GeoIP, you can use this command to add location data to them.
- The event
User.getLanguage
has been removed. - The following deprecated event has been removed:
TaskScheduler.getScheduledTasks
- Special handling for operating system
Windows
has been removed. Like other operating systems all versions will now only be reported asWindows
with versions likeXP
,7
,8
, etc. - Reporting for operating systems has been adjusted to report information according to browser information. Visitor details now contain:
operatingSystemName
,operatingSystemIcon
,operatingSystemCode
andoperatingSystemVersion
- The following methods have been deprecated in favor of the new
Piwik\Intl
component:Piwik\Common::getContinentsList()
: useRegionDataProvider::getContinentList()
insteadPiwik\Common::getCountriesList()
: useRegionDataProvider::getCountryList()
insteadPiwik\Common::getLanguagesList()
: useLanguageDataProvider::getLanguageList()
insteadPiwik\Common::getLanguageToCountryList()
: useLanguageDataProvider::getLanguageToCountryList()
insteadPiwik\Metrics\Formatter::getCurrencyList()
: useCurrencyDataProvider::getCurrencyList()
instead
- The
Piwik\Translate
class has been deprecated in favor ofPiwik\Translation\Translator
. - The
core:plugin
console has been deprecated in favor of the newplugin:list
,plugin:activate
andplugin:deactivate
commands - The following classes have been deprecated:
Piwik\TaskScheduler
: usePiwik\Scheduler\Scheduler
insteadPiwik\ScheduledTask
: usePiwik\Scheduler\Task
instead
- The API method
UserSettings.getLanguage
is deprecated and will be removed from May 1st 2015. UseUserLanguage.getLanguage
instead - The API method
UserSettings.getLanguageCode
is deprecated and will be removed from May 1st 2015. UseUserLanguage.getLanguageCode
instead - The
Piwik\Registry
class has been deprecated in favor of using the container:Registry::get('auth')
should be replaced withStaticContainer::get('Piwik\Auth')
Registry::set('auth', $auth)
should be replaced withStaticContainer::getContainer()->set('Piwik\Auth', $auth)
- You can now generate UI / screenshot tests using the command
generate:test
- During UI tests we do now add a CSS class to the HTML element called
uiTest
. This allows you do hide content when screenshots are captured.
- A new command (core:fix-duplicate-log-actions) has been added which can be used to remove duplicate actions and correct references to them in other tables. Duplicates were caused by this bug: #6436
- Updated AngularJS from 1.2.26 to 1.2.28
- Updated piwik/device-detector from 2.8 to 3.0
- UI specs were moved from
tests/PHPUnit/UI
totests/UI
. We also moved the UI specs directly into the Piwik repository meaning the piwik-ui-tests repository contains only the expected screenshots from now on. - There is a new command
development:sync-system-test-processed
for core developers that allows you to copy processed test results from travis to your local dev environment.
- API responses containing visitor information will no longer contain the fields
screenType
andscreenTypeIcon
as those reports have been completely removed - os, browser and browser plugin icons are now located in the DevicesDetection and DevicePlugins plugin. If you are not using the Reporting or Metadata API to get the icon locations please update your paths.
- The deprecated method
Piwik\SettingsPiwik::rewriteTmpPathWithHostname()
has been removed. - The following events have been removed:
Log.formatFileMessage
Log.formatDatabaseMessage
Log.formatScreenMessage
- These events have been removed as Piwik now uses the Monolog logging library. Learn more.
- The event
Log.getAvailableWriters
has been removed: to add custom log backends, you now need to configure Monolog handlers - The INI options
log_only_when_cli
andlog_only_when_debug_parameter
have been removed
- We added the
symfony/var-dumper
library allowing you to better print any arbitrary PHP variable viadump($var1, $var2, ...)
. - Piwik now uses Monolog as a logger.
- The tracker proxy (previously in
misc/proxy-hide-piwik-url/
) has been moved to a separate repository: https://github.com/piwik/tracker-proxy.
- Some duplicate reports from UserSettings plugin have been removed. Widget URLs for those reports will still work till May 1st 2015. Please update those to the new reports of DevicesDetection plugin.
- The API method
UserSettings.getBrowserVersion
is deprecated and will be removed from May 1st 2015. UseDevicesDetection.getBrowserVersions
instead - The API method
UserSettings.getBrowser
is deprecated and will be removed from May 1st 2015. UseDevicesDetection.getBrowsers
instead - The API method
UserSettings.getOSFamily
is deprecated and will be removed from May 1st 2015. UseDevicesDetection.getOsFamilies
instead - The API method
UserSettings.getOS
is deprecated and will be removed from May 1st 2015. UseDevicesDetection.getOsVersions
instead - The API method
UserSettings.getMobileVsDesktop
is deprecated and will be removed from May 1st 2015. UseDevicesDetection.getType
instead - The API method
UserSettings.getBrowserType
is deprecated and will be removed from May 1st 2015. UseDevicesDetection.getBrowserEngines
instead - The API method
UserSettings.getResolution
is deprecated and will be removed from May 1st 2015. UseResolution.getResolution
instead - The API method
UserSettings.getConfiguration
is deprecated and will be removed from May 1st 2015. UseResolution.getConfiguration
instead - The API method
UserSettings.getPlugin
is deprecated and will be removed from May 1st 2015. UseDevicePlugins.getPlugin
instead - The API method
UserSettings.getWideScreen
has been removed. UseUserSettings.getScreenType
instead. Piwik\SettingsPiwik::rewriteTmpPathWithInstanceId()
has been deprecated. Instead of hardcoding thetmp/
path everywhere in the codebase and then callingrewriteTmpPathWithInstanceId()
, developers should get thepath.tmp
configuration value from the DI container (e.g.StaticContainer::getContainer()->get('path.tmp')
).- The method
Piwik\Log::setLogLevel()
has been deprecated - The method
Piwik\Log::getLogLevel()
has been deprecated
- The HTTP Tracker API does now respond with a HTTP 400 instead of a HTTP 500 in case an invalid
idsite
is used
- New URL parameter
send_image=0
in the HTTP Tracking API to receive a HTTP 204 response code instead of a GIF image. This improves performance and can fix errors if images are not allowed to be obtained directly (eg Chrome Apps).
core:plugin list
lists all plugins currently activated in Piwik.
- Development related console commands are only available if the development mode is enabled. To enable the development mode execute
./console development:enable
. - The command
php console core:update
does no longer have a parameter--dry-run
. A dry run is now executed by default followed by a question whether one actually wants to execute the updates. To skip this confirmation step one can use the--yes
option.
- Most methods of
Piwik\IP
have been deprecated in favor of the new piwik/network component. - The file
tests/PHPUnit/phpunit.xml
is no longer needed in order to run tests and we suggest to delete it. The test configuration is now done automatically if possible. In case the tests do no longer work check out the[tests]
section inconfig/global.ini.php
- Code for manipulating IP addresses has been moved to a separate standalone component: piwik/network. Backward compatibility is kept in Piwik core.
- Updated AngularJS from 1.2.25 to 1.2.26
- Updated jQuery from 1.11.0 to 1.11.1
- The Auth interface has been modified, existing Auth implementations will have to be modified. Changes include:
- The initSession method has been moved. Since this behavior must be executed for every Auth implementation, it has been put into a new class: SessionInitializer. If your Auth implementation implements its own session logic you will have to extend and override SessionInitializer.
- The following methods have been added: setPassword, setPasswordHash, getTokenAuthSecret and getLogin.
- Clarifying semantics of each method and what they must support and can support.
- Read the documentation for the Auth interface to learn more.
- The
Piwik\Unzip\*
classes have been extracted out of the Piwik repository into a separate component named Decompress.Piwik\Unzip
has not moved, it is kept for backward compatibility. If you have been using that class, you don't need to change anything.- The
Piwik\Unzip\*
classes (Tar, PclZip, Gzip, ZipArchive) have moved to thePiwik\Decompress\*
namespace (inside the new repository). Piwik\Unzip\UncompressInterface
has been moved and renamed toPiwik\Decompress\DecompressInterface
(inside the new repository).
- The
Piwik::setUserHasSuperUserAccess
method is deprecated, instead use Access::doAsSuperUser. This method will ensure that super user access is properly rescinded after the callback finishes. - The class
\IntegrationTestCase
is deprecated and will be removed from February 6th 2015. Use\Piwik\Tests\Framework\TestCase\SystemTestCase
instead. - The class
\DatabaseTestCase
is deprecated and will be removed from February 6th 2015. Use\Piwik\Tests\Framework\TestCase\IntegrationTestCase
instead. - The class
\BenchmarkTestCase
is deprecated and will be removed from February 6th 2015. Use\Piwik\Tests\Framework\TestCase\BenchmarkTestCase
instead. - The class
\ConsoleCommandTestCase
is deprecated and will be removed from February 6th 2015. Use\Piwik\Tests\Framework\TestCase\ConsoleCommandTestCase
instead. - The class
\FakeAccess
is deprecated and will be removed from February 6th 2015. Use\Piwik\Tests\Framework\Mock\FakeAccess
instead. - The class
\Piwik\Tests\Fixture
is deprecated and will be removed from February 6th 2015. Use\Piwik\Tests\Framework\Fixture
instead. - The class
\Piwik\Tests\OverrideLogin
is deprecated and will be removed from February 6ths 2015. Use\Piwik\Framework\Framework\OverrideLogin
instead.
- The pivotBy and related query parameters can be used to pivot reports by another dimension. Read more about the new query parameters here.
- Updated AngularJS from 1.2.13 to 1.2.25
generate:angular-directive
Let's you easily generate a template for a new angular directive for any plugin.
- Piwik 2.8.0 now requires PHP >= 5.3.3.
- If you use an older PHP version, please upgrade now to the latest PHP so you can enjoy improvements and security fixes in Piwik.
- Several APIs will now expose a new metric
nb_users
which measures the number of unique users when a User ID is set. - New APIs have been added for Content Tracking feature: Contents.getContentNames, Contents.getContentPieces
- The
Piwik\Menu\MenuAbstract::add()
method is deprecated in favor ofaddItem()
. Read more about this here: #6140. We do not plan to remove the deprecated method before Piwik 3.0.
- It is now easier to generate the URL for a menu item see #6140, urlForDefaultAction(), urlForAction(), urlForModuleAction()
core:clear-caches
Lets you easily delete all caches. This command can be useful for instance after updating Piwik files manually.
- The
'json'
API format is considered deprecated. We ask all new code to use the'json2'
format. Eventually when Piwik 3.0 is released the'json'
format will be replaced with'json2'
. Differences in the json2 format include:- A bug in JSON formatting was fixed so API methods that return simple associative arrays like
array('name' => 'value', 'name2' => 'value2')
will now appear correctly as{"name":"value","name2":"value2"}
in JSON API output instead of[{"name":"value","name2":"value2"}]
. API methods like SitesManager.getSiteFromId & UsersManager.getUser are affected.
- A bug in JSON formatting was fixed so API methods that return simple associative arrays like
- If an API returns an indexed array, it is now possible to use
filter_limit
andfilter_offset
. This was before only possible if an API returned a DataTable. - The Live API now returns only visitor information of activated plugins. So if for instance the Referrers plugin is deactivated a visitor won't contain any referrers related properties. This is a bugfix as the API was crashing before if some core plugins were deactivated. Affected methods are for instance
getLastVisitDetails
orgetVisitorProfile
. If all core plugins are enabled as by default there will be no change at all except the order of the properties within one visitor.
core:run-scheduled-tasks
Let's you run all scheduled tasks due to run at this time. Useful for instance when testing tasks.
- We removed our own autoloader that was used to load Piwik files in favor of the composer autoloader which we already have been using for some libraries. This means the file
core/Loader.php
will no longer exist. In case you are using Piwik from Git make sure to runphp composer.phar self-update && php composer.phar install
to make your Piwik work again. Also make sure to no longer includecore/Loader.php
in case it is used in any custom script. - We do no longer store the list of plugins that are used during tracking in the config file. They are dynamically detect instead. The detection of a tracker plugin works the same as before. A plugin has to either listen to any
Tracker.*
orRequest.initAuthenticationObject
event or it has to define dimensions in order to be detected as a tracker plugin.
- Javascript Tracking API: if you are using
getCustomVariable
function to access custom variables values that were set on previous page views, you now must also callstoreCustomVariablesInCookie
before the first call totrackPageView
. Read more about Javascript Tracking here. - The settings API will receive the actual entered value and will no longer convert characters like
&
to&
. If you still want this behavior - for instance to prevent XSS - you can define a filter by setting thetransform
property like this:$setting->transform = function ($value) { return Common::sanitizeInputValue($value); }
- Config setting
disable_merged_assets
moved fromDebug
section toDevelopment
. The updater will automatically change the section for you. API.getRowEvolution
will throw an exception if a report is requested that does not have a dimension, for instanceVisitsSummary.get
. This is a fix as an invalid format was returned before see #5951MultiSites.getAll
returns from now on always an array of websites. In the past it returned a single object and it didn't contain all properties in case only one website was found which was a bug see #5987
The following events are considered as deprecated and the new structure should be used in the future. We have not scheduled when those events will be removed but probably in Piwik 3.0 which is not scheduled yet and won't be soon. New features will be added only to the new classes.
API.getReportMetadata
,API.getSegmentDimensionMetadata
,Goals.getReportsWithGoalMetrics
,ViewDataTable.configure
,ViewDataTable.getDefaultType
: use Report class instead to define new reports. There is an updated guide as well Part1WidgetsList.addWidgets
: use Widgets class instead to define new widgetsMenu.Admin.addItems
,Menu.Reporting.addItems
,Menu.Top.addItems
: use Menu class insteadTaskScheduler.getScheduledTasks
: use Tasks class instead to define new tasksTracker.recordEcommerceGoal
,Tracker.recordStandardGoals
,Tracker.newConversionInformation
: use Conversion Dimension class insteadTracker.existingVisitInformation
,Tracker.newVisitorInformation
,Tracker.getVisitFieldsToPersist
: use Visit Dimension class insteadViewDataTable.addViewDataTable
: This event is no longer needed. Visualizations are automatically discovered if they are placed within aVisualizations
directory inside the plugin.
As a plugin developer you might want to reuse existing translation keys. You can now find all available translations and translation keys by opening the page "Settings => Development:Translation search" in your Piwik installation. Read more about internationalization here.
It is now possible to use the filter_sort_column
parameter when requesting Live.getLastVisitDetails
. For instance &filter_sort_column=visitCount
.
We are using @since
annotations in case we are introducing new API's to make it easy to see in which Piwik version a new method was added. This information is now displayed in the Classes API-Reference.
- Report to add a new report
- Action Dimension to add a dimension that tracks action related information
- Visit Dimension to add a dimension that tracks visit related information
- Conversion Dimension to add a dimension that tracks conversion related information
- Dimension to add a basic non tracking dimension that can be used in
Reports
- Widgets to add or modfiy widgets
- These Menu classes got new methods that make it easier to add new items to a specific section
- MenuAdmin to add or modify admin menu items.
- MenuReporting to add or modify reporting menu items
- MenuUser to add or modify user menu items
- Tasks to add scheduled tasks
generate:theme
Let's you easily generate a new theme and customize colors, see the Theming guidegenerate:update
Let's you generate an update filegenerate:report
Let's you generate a reportgenerate:dimension
Let's you enhance the tracking by adding new dimensionsgenerate:menu
Let's you generate a menu class to add or modify menu itemsgenerate:widgets
Let's you generate a widgets class to add or modify widgetsgenerate:tasks
Let's you generate a tasks class to add or modify tasksdevelopment:enable
Let's you enable the development mode which will will disable some caching to make code changes directly visible and it will assist developers by performing additional checks to prevent for instance typos. Should not be used in production.development:disable
Let's you disable the development mode
Find the general Piwik Changelogs for each release at piwik.org/changelog