Skip to content
Extraits de code Groupes Projets
  1. juil. 23, 2013
  2. juil. 20, 2013
  3. juil. 02, 2013
  4. mai 31, 2013
    • Benaka Moorthi's avatar
      Refactored archive data querying code. Removed tree-like data structure from... · 6abbacb9
      Benaka Moorthi a rédigé
      Refactored archive data querying code. Removed tree-like data structure from Piwik_Archive, added memory optimizations for archiving (not storing archive processing instances), added optimization for querying data indexed by site + date, added ability to select multiple blobs/metrics at once (from different plugins), added optimization to Piwik_ArchiveProcessing_Period where numerics/records are selected all at once instead of one at a time.
      
      Also added data access layer object for archive querying code, allowed anonymous function objects to be used as DataTable filters, and removed 'timestamp' DataTable metadata.
      6abbacb9
  5. mai 23, 2013
  6. avr. 17, 2013
  7. avr. 02, 2013
    • Timo Besenreuther's avatar
      refs #1700 performance analytics · fb5f11a5
      Timo Besenreuther a rédigé
       * adding avg_time_generation to Actions.get + integration tests
       * adding sparkline for average generation time to Visitors > Overview
       * changing number formatting to 0.XXs instead of XXXms + test cases
       * tooltip for reports with avg. generation time: "average based on X hit(s)"
       * log import: support generation_time_milli (not only generation_time_micro)
       * example for importing generation time from logs in read me
      fb5f11a5
  8. mars 27, 2013
  9. mars 26, 2013
    • Timo Besenreuther's avatar
      refs #1700 basic performance analytics: handle server generation time for each page and page title · 65458d09
      Timo Besenreuther a rédigé
      CORE
      
       * formatting sub-second times
       * getColumn() method on data table array (in order to behave the same as the regular data table class)
       * data tables can store in their meta data, which columns are empty (this is used in order to dynamically hide the new "generation time" column)
       * ViewDataTable and Api.getProcessedReport act according to the empty column meta data
      
      
      SCHEMA
      
       * new column custom_float_1 in log_link_visit_action
       * new version to apply the change
      
      
      TRACKER
      
       * Piwik_Tracker::setGenerationTime
       * tracking parameter "generation_time_me"
       * value is stored in new custom_float_1 column
       * the log importer can handle a group "generation_time_micro" which can be used in a custom log format. _micro is used because apache can log the time in microseconds but piwik processes milliseconds.
       * note: extension of JS tracker still missing
      
      
      ACTIONS PLUGIN
      
       * for pages and page titles, add new columns sum_time_generation and nb_hits_with_time_generation to the blob archives
       * if they are set, compute avg_time_generation on the API level. if not, remove the columns and mark them as empty in the data table meta data.
       * show new column "avg. generation time" in the pages and page titles reports
      
      
      plus TESTS for everything
      65458d09
  10. mars 11, 2013
  11. fév. 11, 2013
  12. fév. 10, 2013
  13. fév. 05, 2013
  14. déc. 24, 2012
  15. nov. 24, 2012
  16. oct. 15, 2012
    • mattpiwik's avatar
      Refs #2992 Site Search KABOOM, Refs #49 · 53649590
      mattpiwik a rédigé
      Implementing Site Search tracking & reporting in Piwik core!
      
       * New Admin UI to customize, for each site, wheter site search is enabled. Also options to set default values to use.
       * New Reports: Searches, Searches with no result, Search categories, Top Pages Following a Search
       * to track "No result keyword" users will have to tag their site with a JS call, or add a new parameter to the search result page &search_count=X (X being zero for no result searches)
       * Reports works with Row evolution, PDF/HTML reports, Piwik Mobile
       * idaction_url is now NULLable because, Site Search records a page with idaction_name == Keyword, and idaction_url == NULL. This ensures that the Site Searches don't create "Page URL Not defined" records. 
       * updates to Tracker JS API, new function trackSiteSearch, also added in PHP tracker
       * New fields in log_visit to track searches
       * new segment, "searches" which can be used to select visitors who did a search ie. searches>0 or those who searched a lot, ie searches>10
       
       TODO: 
        * commmit integration test, TESTING, DOCS, FAQ, release, and a nice Prayer to the universe and the stars, hoping that I can code a major new feature without any bug...
        * It would be awesome to have compatiblity with Transitions so we can see, for a given site search, what are the starting pages and Destination pages
        
       Thank you for your patience Timo, 
       and thank in advance everyone for your help Testing this new feature!
       
      
      
      git-svn-id: http://dev.piwik.org/svn/trunk@7190 59fd770c-687e-43c8-a1e3-f5a4ff64c105
      53649590
  17. oct. 04, 2012
  18. oct. 03, 2012
  19. sept. 27, 2012
  20. sept. 24, 2012
  21. août 20, 2012
  22. août 19, 2012
  23. août 17, 2012
  24. août 16, 2012
  25. août 05, 2012
  26. août 02, 2012
  27. août 01, 2012
  28. juil. 29, 2012
Chargement en cours