| Age | Commit message (Collapse) | Author |
|---|
|
* Removes deprecated Plugin.getListHooksRegistered and uses Plugin.registerEvents instead
* Removes deprecated method Piwik\Piwik::doAsSuperUser
* Remove deprecated SettingsPiwik::isPiwikInstalled and use SettingsPiwik::isMatomoInstalled instead
|
|
* platform tweaks
* prevent failing if loaded twice
* Update Config.php
* Update PluginList.php
* Update Config.php
* Update IniFileChain.php
* Update Config.php
* Update Config.php
* allow configure different path for custom logo
* only show install plugin button when activated
* allow disable users and sites management
* do not allow calling set super user access
* Update PluginList.php
* Update Config.php
* Update global.ini.php
* Update Config.php
* Update global.ini.php
|
|
* various performance tweaks
* tweak so tests dont fail
* Update Manager.php
* Update Plugin.php
* cache custom variables properly
|
|
I updated the link tag for all php files with the new matomo link.
Not sure if it is realistic that this will get merged but I though that someday someone has to do this(?)
|
|
fix #11029
|
|
|
|
* Make matomo.js and matomo.php the default Tracking API endpoints used
* few fixes
* fix few tests
* update matomo php tracker in composer
* make sure to record install version
* do not overwrite ever install version
* trying to fix test
* more tweaks and fix tests
* prefer matomo endpoint in the ui, fix some tests
* file was still needed
* apply review feedback
* fix ui tests
|
|
refs a couple of issues I think. Eg https://github.com/matomo-org/matomo/issues/11029
For some reason that I cannot explain, it stored `127.0.0.1` as the matomo URL in the DB causing a bug in tag manager. So I opened a regular page in Matomo and was expecting it to correct the value in the option table but it didn't. I think this is because of the above change where it checks whether the previous URL is not a local host whereas it maybe should check on the current URL?
See the debugger picture where it did not overwrite 127.0.0.1 with the correct current url/host because the host is currently a local host (127.0.0.1). If it checked whether the actual host is a local host, it would have updated it.
|
|
* 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
|
|
* 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
|
|
|
|
* disable outgoing communication with one setting
* disabled piwik blog if isInternetEnabled=0
* better description for enable_internet_features
* reenable plugin
|
|
Need this method in a plugin.
|
|
Super User display the full safe mode to troubleshoot further (#11082)
* When safe mode is displayed, and Super User was not logged in already, let Super User display the full safe mode to troubleshoot further
* meant for a different PR
* Catch exceptions during CSS/Less compiling
* when there's an error during Twig template processing, or during LESS css compiling, display the safe mode
* Deactivate plugin as super user when authenticated with i_am_super_user
* when user is not logged as Super User, Make deactivate plugin work by forwarding the i_am_super_user URL parameter
* Display plugin version in safe mode fixes https://github.com/piwik/piwik/issues/11043
* Added a text to indicate users to first disable third party plugins
* Updated UI test
* clarify that salt is a secret
* reuse helper method
* minor
* Catching PHP7 errors and making it work on php5
|
|
* starting to port marketplace to piwik 3
* updating tests
* fix translation key
* fix various issues
* use material select
* fix plugin upload
* deprecate license_homepage plugin metadata and link to a LICENSE[.md|.txt] file if found (#10756)
* deprecate license_homepage plugin metadata, and link to a LICENSE[.md|.txt] file if found
* Make license view HTML only without menu
* fix tests and update
* fix some links did not work
* we need to show warnings even when plugin is installed, not only when activated. otherwise it is not clear why something is not downloadable
* fix install was not working
* improved responsiveness of marketplace
* fix more tests
* fix search was shown when only a few plugins are there
* fix ui tests
* fix some translations
* fix tests and remove duplicated test
|
|
still exists but is not readable (#10331)
* * In messages, make it more clear whether config file exists and/or is (not) readable
* When the config file exists but is not readable, provide users the choice between making the file readable, or starting a fresh install
* As long as Piwik is not installed, piwik.php should not return 500 when config file is not readable
* Fixes #10283
* UI tests: updated message when config file is not found
|
|
|
|
|
|
may be mis-configured
|
|
|
|
|
|
parameter in CronArchive.php class. New parameter limits list of segments that should be archived during archiving, all other segments are skipped.
|
|
|
|
|
|
refs https://github.com/PiwikPRO/plugin-MetaSites/issues/3
|
|
tests
|
|
using the static array - these are called 50 K times or more when only 100 websites when rendering a scheduled report
|
|
Conflicts:
tests/PHPUnit/Integration/LogTest.php
|
|
and commit commands are still shown in development mode only)
|
|
The `tmp/` path was hardcoded everywhere, which resulted in using `SettingsPiwik::rewriteTmpPathWithInstanceId()` to rewrite it for specific use cases.
I've moved that path into the config, and replaced all hardcoded usage (and calls to `rewriteTmpPathWithInstanceId()`) by a `get()` from the container.
Getting entries from the container is a bad practice and dependency injection should be preferred, but we do baby steps. When refactoring those classes to DI, we'll replace calls to the container with proper dependency injection.
Another thing we'll need to do too is move the hardcoded *sub-path* of `tmp/` (e.g. `tmp/sessions/`) into the config also (but again: baby steps).
Another future step would be to remove completely instance ID and let it be handled by a plugin (or by end-user config). Having the `tmp/` path in the config means that plugins or users can override it and know it will be taken into account everywhere in Piwik.
|
|
code, few refactorings, all as part of our code cleanup strategy
|
|
|
|
|
|
|
|
error message
|
|
to use free/libre instead of open source
|
|
single codebase)
|
|
|
|
|
|
|
|
|
|
|
|
core:archive` command
|
|
sure tmp/ folders are using hostname
|
|
|
|
http://forum.piwik.org/read.php?8,114216,page=1#msg-114795
|
|
|
|
|
|
though it may be cached as HTTP)
|
|
|
