Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Visitor Log always shows all data #1319

Closed
anonymous-matomo-user opened this issue May 1, 2010 · 14 comments
Closed

Visitor Log always shows all data #1319

anonymous-matomo-user opened this issue May 1, 2010 · 14 comments
Assignees
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Milestone

Comments

@anonymous-matomo-user
Copy link

I have discovered that the "visitor log" always shows the whole data. E.g. 30 April is selected but the table also shows data from 29 April and so on...
This behavior makes the "visitor log" very slow.

@julienmoumne
Copy link
Member

I have added a patch to solve the issue.

Do tell me what you think about it.

@julienmoumne
Copy link
Member

Attachment:
live.patch

@mattab
Copy link
Member

mattab commented May 24, 2010

looks good to me - did you test the patch with more than 1000 visits in one day? does the visitor log load faster with the patch? (visits generator can be found in misc/generateVisits.php)

@julienmoumne
Copy link
Member

After testing with a lot of data, there is a cap at 1000 visits (both before and after suggested patch).

You will see improvement if you select a day period with less than 1000 visits.

@mattab
Copy link
Member

mattab commented May 28, 2010

Core review: The private method loadLastVisitorDetailsFromDatabase() signature has changed (added $period parameter) but there are other calls to this method that haven't been updated to add the new $period parameter.

@julienmoumne
Copy link
Member

I have updated and tested required methods.

If you look at /plugins/Live/Controller.php there is an API call to method 'getLastVisits'. Method 'getLastVisits' has been updated to add $period and $date parameters.

I didn't know if the call at lign 133 had to be updated as well to provide period and date values. I tried to leave it as it is and also tried to provide the values. In both cases the values for period and date are provided to the API method 'getLastVisits'.

This is why I didn't update the API call.

Please advise on this matter.

@julienmoumne
Copy link
Member

Attachment:
#1319.patch

@mattab
Copy link
Member

mattab commented Jun 11, 2010

Call at line 133 builds a Piwik_Api_Request object, which will look into _GET for parameters not passed in the constructor string so this is OK.

@mattab
Copy link
Member

mattab commented Jul 14, 2010

sorry for delay,
I applied the patch but It breaks the Live! visitors plugin (not on first load, but after few seconds and reload).

maybe some API calls haven't passed new parameters?

@julienmoumne
Copy link
Member

My mistake.

When the API call is made with the jQuery spy plugin, no Date and no Period is provided to the call. The jQuery spy plugin receives the error "period parameter not provided" and breaks the widget.

I just had to specify that those parameters (date and period) are mendatory. Cf. new patch.

@julienmoumne
Copy link
Member

Attachment:
piwik-dev2 (#1319).patch

@julienmoumne
Copy link
Member

I meant "not mandatory".

@peterbo
Copy link
Contributor

peterbo commented Jul 25, 2010

Attachment: Can't we keep it simple with getting the date / period in the given method? Then we'll not make the Plugin even more complicated; Patch running without bugs in my local repository
LivePluginApiApplyDateRange.patch

@peterbo
Copy link
Contributor

peterbo commented Jul 29, 2010

(In [2784]) fixes #1375, #1319

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Projects
None yet
Development

No branches or pull requests

4 participants