@mattab opened this issue on February 8th 2008

This problem comes from the fact that we use ajax to load every content in piwik, so the URL remains the same all the time.

To fix this we can use the # in the URL, the same way Gmail does.

proposal - at least following variables should be persisted in V1: day/period/idSite/module/action - how to implement it? I would suggest the Facebook way (ie. the query after the #, eg. #module=Referers&action=getSearchEngines&idSite=1 etc.) - see http://dev.piwik.org/trac/wiki/HowToTestUI which lists all UI features; good place to start to get a feeling of what is necessary to persist


Currently changing the date in the calendar also changes the currently viewed section (reset to Dashboard).

Instead we should reload the same category.


See Jquery History

jQuery history plugin: It uses the hash (fragment) method that was mentioned earlier in this thread. You essentially need to be able to store some text that encapsulates the current page state so that it can be recreated by the browser on reload; no information beyond that in the URL is maintained in any reliable way. This particular plugin also has the effect of making the "back" and "forward" buttons undo and redo page state changes, which you may or may not want.

@mattab commented on March 12th 2009

kpham, thanks for patch.

I think however code can be improved, especially because in the future we'd like to persist more parameters than period/date/idsite/module/action therefore it should be modular.

Feedback On the architecture side: I would think of having a broadcaster javascript object that you would call with a simple api like: changeParameter(string). For example:

<a href="broadcast.changeParameter('module=Referers&action=getKeywords')">View full keywords report</
<a href="broadcast.changeParameter('date=yesterday&period=day&module=Referers&action=getKeywords')">View full keywords report for yesterday</a>

This function would update the hash. Then it would trigger an event that says "onParametersUpdate" for example, and this function would do the job to call the right url in ajax to load below the menu (ie. there will be some menu code moved from existing javascript to this function). Later we could persist other parameters and add the code necessary to restore the page state in this function.

What do you think about such a design?

Other feedback on the code - updateAnchor has a li_id parameter but it's not used? - for example, calendar.js shouldn't have to do substring matches, it should call a method on the broadcast object (eg. getVariableFromAnchor('date')) that would do the work and return the right variable from the hash, or false - isAnchorExists should return false rather than undefined - getParamValueFromUrl should work well when passed a URL with anchor (ie the api of the object to handle the hash should be very simple to use from outside) - also please have a look at Piwik Coding Standard

also: - does the back button work as expected on the browser? - we should aim to persist the parameters date and period as well. - Persisting idSite could wait for the V2 as it has some added complications (ie. you need to fetch the minDate for this website, fetch the website name and set it in the global piwik javascript array, etc.)

let me know what you think.

@mattab commented on May 6th 2009

(In [1095]) - Refresh and back button now work! great contribution by Khanh Pham fixed #103 it's using the jquery history plugin. period, date, idsite, module and action are persisted across requests, making Piwik much nicer and faster to use.

@mattab commented on May 6th 2009

(In [1096]) it should work better with the main broadcast.js file :) refs #5523

This issue was closed on January 22nd 2011
Powered by GitHub Issue Mirror