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
Getting the same error as reported in #2732 and a similar one, in my case after enabling ecommerce tracking on 1.6.0. For me, almost all widgets on the dashboard show:
Fatal error: Class 'Piwik_CustomVariables' not found in /var/php/piwik/plugins/Goals/Goals.php on line 583
On the ecommerce goals page, I get:
Fatal error: Class 'Piwik_CustomVariables' not found in /var/php/piwik/plugins/Goals/Goals.php on line 583
I've restarted the fcgi process and apache, checked that the code is the same as in the latest.zip file and verified file permissions. Interestingly, the error goes away once I switch the period to something not including today. So, I figure something got tracked since enabling the ecommerce tracking that causes the error to show.
The text was updated successfully, but these errors were encountered:
For a staging site where I tested the ecommerce tracking, I get a different error on the ecommerce goals page (above, I pasted the same error message twice):
Fatal error: Class 'Piwik_CustomVariables' not found in /var/php/piwik/plugins/Goals/API.php on line 292
Also, the errors are limited to the individual websites tracked. I.e. for the staging site and all others tracked by this piwik server, I still get a normal dashboard display.
Getting the same error as reported in #2732 and a similar one, in my case after enabling ecommerce tracking on 1.6.0. For me, almost all widgets on the dashboard show:
On the ecommerce goals page, I get:
I've restarted the fcgi process and apache, checked that the code is the same as in the latest.zip file and verified file permissions. Interestingly, the error goes away once I switch the period to something not including today. So, I figure something got tracked since enabling the ecommerce tracking that causes the error to show.
The text was updated successfully, but these errors were encountered: