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

Date range not available with idsubtable based api #1395

Closed
anonymous-matomo-user opened this issue May 29, 2010 · 5 comments
Closed

Date range not available with idsubtable based api #1395

anonymous-matomo-user opened this issue May 29, 2010 · 5 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. duplicate For issues that already existed in our issue tracker and were reported previously. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Milestone

Comments

@anonymous-matomo-user
Copy link

Hello,

To make this short, here is what I am talking about, while :
http://piwik.org/demo/?module=API&idSite=1&period=month&date=2010-04-22&format=JSON&filter_limit=25&method=Referers.getKeywordsFromSearchEngineId&idSubtable=34&token_auth=anonymous

Works as expected, the same one with a date range :
-piwik.org/demo/?module=API&idSite=1&period=month&date=2010-04-22,2010-05-22&format=JSON&filter_limit=25&method=Referers.getKeywordsFromSearchEngineId&idSubtable=34&token_auth=anonymous

does not, it results in this error :
Fatal error: Call to undefined method Piwik_DataTable_Array::getRowFromIdSubDataTable() in /***/plugins/Referers/API.php on line 102

If you use period=day, you get:
{"result":"error", "message":"You are requesting a precise subTable but there is not such data in the Archive."}

which is better, but.

So I assume that this is a bug in the current version, since date range should as well be available when using idSubtable.

Best regards,

dcz

@robocoder
Copy link
Contributor

duplicate of #572

@anonymous-matomo-user
Copy link
Author

Hello,

I must be missing something here, because I don't see the relation between a bug report (since there is an error showing up, it must be wrong, by no mean an url manipulation should lead to any) and a feature request.

If not the feature (being able to ask for any date range in all cases), the bug (error) should IMHO be fixed before 1.0.

Excuse my ignorance if I missed something.

Best regards,

dcz

@robocoder
Copy link
Contributor

Sorry, I was triaging tickets from my phone. There's another ticket open for handling API error messages.

@anonymous-matomo-user
Copy link
Author

Replying to vipsoft:

Sorry, I was triaging tickets from my phone. There's another ticket open for handling API error messages.

Ok, no problem, and thanks for you concern

Best regards,

dcz

@mattab
Copy link
Member

mattab commented May 31, 2010

This is expected: specific keywords/countries/page URLs/etc. have different idsubdatatable each day. If you want to lookup a specific keyword over several days, you must use the API parameters:

# filter_pattern ; defines the text we want to search for in the filter_column. Only the row with the given column matching the pattern will be returned.
# filter_column ; defines the column that we want to search for a text (see filter_pattern).

@anonymous-matomo-user anonymous-matomo-user added this to the Piwik 0.6.3 milestone Jul 8, 2014
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. duplicate For issues that already existed in our issue tracker and were reported previously. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Projects
None yet
Development

No branches or pull requests

3 participants