You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a Kohana backend application which uses Piwik API to show tracking statistics.
Calling the API with PHP creates a directory /tmp/templates_c in my application public folder. This directory should not be created in my application folder but in Piwik installation folder.
The only difference between the example and my work is that my application doesn't directly include Piwik : my application and piwik are separated apache subdomains.
One thing : in the Piwik code, folders like tmp/templates_c are relatives, not absolutes. They should be prefixed with PIWIK_INCLUDE_PATH.
This a real bug and not a code mistake as i have exactly done the same thing than in the wiki example.
The text was updated successfully, but these errors were encountered:
(In [fixes #2001 - add comments and flesh out example; confirmed that tmp/templates_c is prefixed by PIWIK_USER_PATH and that the PIWIK_ defines are documented (wiki:API/CallingTechniques) links to [wiki:API/IncludePiwikInYourProject])
I have a Kohana backend application which uses Piwik API to show tracking statistics.
Calling the API with PHP creates a directory /tmp/templates_c in my application public folder. This directory should not be created in my application folder but in Piwik installation folder.
First, i have coded exactly what it is described on the wiki page : http://dev.piwik.org/trac/wiki/API/CallingTechniques
The only difference between the example and my work is that my application doesn't directly include Piwik : my application and piwik are separated apache subdomains.
One thing : in the Piwik code, folders like tmp/templates_c are relatives, not absolutes. They should be prefixed with PIWIK_INCLUDE_PATH.
This a real bug and not a code mistake as i have exactly done the same thing than in the wiki example.
The text was updated successfully, but these errors were encountered: