| Age | Commit message (Collapse) | Author |
|---|
|
catching them and re-throwing them.
|
|
FrontController to FrontController.
|
|
methods instance methods, create Update instances via DI, make Columns\Updater use instance methods instead of static, and add integration test for Columns\Updater.
|
|
show progress of update. Also remove CLI output code from CoreUpdater\Controller::runUpdaterAndExit.
|
|
errors caused by change to Updates.php and add some more functionality to ConsoleCommandTestCase base class.
|
|
update process and document UpdateListener.
|
|
Columns\Updater and document methods in Updater.
|
|
CoreUpdater static functions to core/Updater class, remove use of static methods in Updater, don't use static method setUpdater in ColumnsUpdater).
|
|
broken race conditions
|
|
implementation59925362d527fbd051a4e12113abcab282983436
|
|
code, few refactorings, all as part of our code cleanup strategy
|
|
|
|
file. Added possibility to copy methods from one class into another including use statements and documentation, added possibility to directly make a translation and modify or create a language file during generation
|
|
report_and_dimension_refactoring
Conflicts:
core/Updates/0.4.2.php
core/Updates/0.6.3.php
core/Updates/1.2-rc1.php
core/Updates/1.9-b9.php
core/Version.php
tests/PHPUnit/Fixture.php
tests/PHPUnit/Fixtures/UITestFixture.php
tests/PHPUnit/Integration/Core/JsProxyTest.php
|
|
are executed more than once, add test for multiple update and allow updates to specify more than one error code to ignore.
|
|
c01d57bc17, this might work... basically the idea was ok but we should check for this only if the column actually already exists. If the column does not exist yet we need to make sure it will be installed
|
|
2.5.0-b1 the updater wanted to update all dimensions (meaning alter all columns in log_visit, link_action and conversion) to the same column type. This was happening because the system did not know those dimensions were already installed from a previous Piwik version. There was an update script that was supposed to tell Piwik those components are actually already installed since we only moved them from core to plugins but it cannot work as it is an update as well and therefore not executed before the actual update check. I tried many solutions to overcome this issue including reverting all the columns to the initial MySql Schema but even then there are problems as some plugins like DevicesDetection are not defined in MySql Schema but in the plugin. It is especially complicated since users might update from 2.4 to a future version where the column type of one of those dimension changes and we need to make sure to actually execute an alter update if one of those dimension changes. In such a case we cannot directly mark the component as successfully recorded. The conclusion was for me it is only possible to solve this problem by listing all dimensions that were moved from core to plugins including their version at that time hard coded...
|
|
|
|
once and not as often as dimensions are there... makes updater much faster, still does not fix the purge data test
|
|
column in case the type changes making it super easy for developers, not sure if everything works already and need to xhprof it
|
|
added the platform should detect this and run an update script. also if a dimension suddenly handles new cases such as conversion it should automatically add a column to log_conversion after a user confirms. Have not tested update and/or installation yet
|
|
to use free/libre instead of open source
|
|
reported issues.
|
|
segmented metrics. Removed Archiver and API. Old segmented VisitFrequency metrics will not be accessible.
|
|
upgrades, if any.
Run it via: ./console core:update --dry-run
|
|
refs #4609
|
|
|
|
Option::get and Option::set and Option::delete
|
|
|
|
successfully installed + should fix the build (thx ArchiveCronTest)
|
|
|
|
|
|
|
|
longer strings ( fields config_os_version and config_device_type are not large enough )
Refs #4204 Plugin schema example with DevicesDetection
|
|
|
|
not be loaded because they are not compatible with Piwik 2
|
|
Conflicts:
core/Tracker/Request.php
core/ViewDataTable.php
core/ViewDataTable/HtmlTable/Goals.php
plugins/Actions/Actions.php
plugins/Annotations/API.php
plugins/CoreHome/CoreHome.php
plugins/DBStats/DBStats.php
plugins/DevicesDetection/DevicesDetection.php
plugins/Goals/Goals.php
plugins/Live/Live.php
plugins/Referers/Referers.php
plugins/UserSettings/UserSettings.php
plugins/UsersManager/API.php
plugins/VisitTime/VisitTime.php
plugins/VisitorInterest/VisitorInterest.php
|
|
|
|
\Piwik\Plugins\*
Added namespaces to functions.php files in the five plugins that had one
Work in progress
|
|
|
|
core/ conversion
|
|
Removed many Piwik_ functions, in Piwik 2 it is best practise to use the methods calls instead
Todo: finish converting core/ classes + convert plugins/ classes to use \Piwik\Plugin namespace + fix build + Merge master
|
|
|
|
Notice that auto refactoring has created a nested namespace. Not sure this is what we want - so we might have to edit those nested namespaces afterwards (I think they don't look so good)
|
|
Notice that auto refactoring has created a nested namespace. Not sure this is what we want - so we might have to edit those nested namespaces afterwards (I think they don't look so good)
|
|
creating new archive entry
|
|
Converting Piwik core source files, PHP, JS, TPL, CSS
More info: http://piwik.org/participate/coding-standards/
|
|
|
|
git-svn-id: http://dev.piwik.org/svn/trunk@6814 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
|
git-svn-id: http://dev.piwik.org/svn/trunk@6790 59fd770c-687e-43c8-a1e3-f5a4ff64c105
|
