Skip to content


Piwik_DataTable_Renderer doesn't use the Piwik_API_Request $request parms #561

anonymous-piwik-user opened this Issue · 3 comments

2 participants


Using this query string, I am trying to get back the full expanded datatable in the php array. CorpspediaActions.getActionsFilteredByUser is an extension of Actions that does its own archive processing based upon the original methods (essentially grouping by a custom user_id field).


I expected the “expanded” property to cause the php array to come back full loaded. But it was not, using a debugger, I can verify that the table and subtables ARE being built, but it is the rendering process that is not including the subtables in the final response.

The problem appears to be caused by the fact that the Piwik_API_Request builds a custon “request” array that it passes to the Piwik_API_ResponseBuilder (who eventually will handle the rendering). The problem is that in the constructor for Piwik_DataTable_Renderer, it doesn’t have access to the custom request array and therefore does not find the expanded parm that was set to “true”.

My gut tells me that we need to find a way to propagate the custom request array to the Renderer so that it can use that array (when available) instead of the plain $_REQUEST array (which is the default). Keywords: Datatable renderer


I am going to try and hack a solution so I can solve my immediate needs, but I hope that you can help with a more elegant solution. Thanks!

Piwik Open Source Analytics member

it’s actually a bug, and could be a limitation for people building plugin. increasing priority.

Piwik Open Source Analytics member

fixed in 944

refactored and added public method to set all customizations on the Renderer + updating tests

please svn up, test, and if still experience problems please reopen

@anonymous-piwik-user anonymous-piwik-user added this to the RobotRock milestone
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.