Opened 6 years ago

Closed 5 years ago

Last modified 5 years ago

#126 closed Bug (fixed)

Proper "Date" handling in graphs / UI / tables

Reported by: matt Owned by:
Priority: major Milestone: Piwik 0.6.1
Component: Core Keywords:
Cc: Sensitive:

Description (last modified by matt)

The generated date string are currently not modular; it is not really possible to add new date schemes (March, 8th instead of Wednesday 8th March for example)

We should have a proper date handling in:

  • graphs
    • titles
    • legends
    • x-y labels
  • in UI
  • in tables

This should be designed with i18n in mind.

in the API data output
Also, currently the XML output looks like example. To manipulate easily this data, one needs to have a "dateFrom" and a "dateTo" attribute in the XML element. Add these elements in the XML renderer, CSV.

Change History (5)

comment:1 Changed 6 years ago by matt (mattab)

  • Description modified (diff)

comment:2 Changed 6 years ago by matt (mattab)

  • Milestone changed from Stable release to DigitalVibes

comment:3 Changed 5 years ago by matt (mattab)

  • Description modified (diff)
  • Summary changed from Proper date handling in graphs / UI / tables to Proper "Date" handling in graphs / UI / tables

comment:4 Changed 5 years ago by matt (mattab)

  • Resolution set to fixed
  • Status changed from new to closed

(In [1072]) - API CHANGE: the API for the function Piwik_AddWidget has changed. The new 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)'

comment:5 Changed 5 years ago by koteiko

Note: See TracTickets for help on using tickets.