| Age | Commit message (Collapse) | Author |
|---|
|
API is Piwik_AddWidget( $widgetCategory, $widgetName, $controllerName, $controllerAction, $customParameters = array()). See examples of calls in all the core Piwik plugins. This change was necessary to make widgets more modular (they now accept custom parameters).
- API CHANGE: a small number of CSV outputs for some API calls would change following the simplification of DataTable_Simple implementation. Affected calls are VisitsSummary.get, Goals.get, VisitFrequency.get. This is due to a change in the implementation of DataTable_Simple (we simplified implementation).
- FIXED #84 Added proper translations for all columns, in tables, and graphs.
- FIXED #322 piwik is now using open flash chart 2
- FIXED #126 all dates should be correctly displayed in all graphs. For example, evolution graph for days would show, on the X axis "Mon 29", "Wed 31". For months it would show "Aug 2009", etc.
- ADDED: when hovering any of the sparklines, the UI makes it clear that clicking will refresh the evolution graph. This feature was in Piwik for months, and even Google Analytics implemented this UI feature after Piwik. However in Piwik it wasn't clear to the user that the sparklines were clickable.
- ADDED: now widgets can be created with custom parameters. This makes it possible to create a widget that calls a controller->action with other custom parameters, this is used in Piwik to draw an evolution graph (module=VisitsSummary & action=getEvolutionGraph) for a given metric (&columns[]=nb_visits). These custom parameters are automatically forwarded to the sparkline url, the flash graph when clicked on sparkline, etc.
- The widget layout is now saved as a JSON string rather than a custom data structure. The dashboard code should be able to read & restore most of the layouts from the old format (except the evolution graphs widgets). Simplified the Dashboard.js, widgetMenu.js, cleaned up what was a messy code.
- Added sentence in Widgetize to let users know they can easily export the Piwik dashboard in an iframe.
- Changed the way translations used in Javascript are loaded: all translations strings finishing by _js will be loaded to be used in the templates when calling {loadJavascriptTranslations plugins='YOUR_PLUGIN_NAME'}
- Moved all templates in plugins under plugins/$PLUGIN/templates/
- 'Khtml (Konqueror, Safari)' now displayed as 'KHTML (Safari, Chrome)'
|
|
http://piwik.org/contribute/
|
|
will link to a page that asks for either: automatic one click upgrade, or manual download.
if automatic one click update is selected, Piwik will download piwik.org/last.zip, unzip, does very basic check on unzipped file, backup config file, copy all files over existing files, and shows feedback to user.
there are several point of failures and the code should be tested on normal linux environment, I believe for example we can make it more robust by trying to chmod the files in 0644 if copy() of the new files over the existing ones fails.
this mechanism should help driving piwik update rates from existing users, minimising risks of security holes, and maximising usage of latest piwik features.
|
|
api.piwik.org to check if a new piwik release is available. If a new release is available, the top right orange message will display: "Piwik 0.2.30 is available! Please update now (see changes)." with link to piwik.org/docs/update and piwik.org/changelog
- adding helper function to send http request with enforced timeout (to make sure that the piwik UI doesn't hang for 30 seconds when checking for a new release once a day, if piwik.org down)
- adding some installation strings that weren't in the translation file already
- adding two checkboxes during installation: register to piwik major & security releases newsletter, register for general piwik newsletter.
|
|
|
|
|
|
- adding Chinese
- adding version number in UI
-
|
|
|
|
looking at the demo
|
|
Fixed javascript handling of translations: we can now load translations strings in several places in the templates, they will all be concatenated into one bigger object
Fixed handling japanese error messages in API with correct charset
Finished (hopefuly?) to make all strings translatable.
Added colored logo now in login screen
All templates now defined the dates necessary to build the calendar, as we notice that most pages want to show the calendar.
Added destructor to LogStats/Db.php so that plugins don't have to call disconnect() on the object
Made JS tag smaller
Improved templates structuring, refactored CSS, etc. still lots to do in this area, if you wanna help?
|
|
- cleaning admin UI
- adding widgetize module
- cleaning template architecture
|
