I'm using Drupal 6.0RC2 and BAWStats 6.x-0.1. I can run the standalone BAWStats to see my AWStats report. But when I tried to see it in Drupal (http://xxx/admin/bawstats), I got the error.
Do I miss anything ?

Fatal error: Call to undefined function baw_data_read_data() in D:\drupal\sites\all\modules\bawstats\includes\bawstats.stats.inc on line 105

Comments

anaru’s picture

anaru commented
Assigned: Unassigned » anaru
Status: Active » Fixed

Thanks for finding this bug. Its in a function that only gets called when there is a stats year problem. I have produced a new release that I hope fixes this (and fixes a number of other non critical issues). If you are still having problems let me know.

dennys’s picture

dennys commented

I upgraded to 0.2 (uninstall and install) and refresh the screen, but the screen is empty. So, I checked the watchdog and see the following message:

* warning: include(./modules/search/search-theme-form.tpl.php) [function.include]: failed to open stream: No such file or directory in D:\drupal\includes\theme.inc on line 955.
* warning: include() [function.include]: Failed opening './modules/search/search-theme-form.tpl.php' for inclusion (include_path='.;D:\xampp\php\pear\') in D:\drupal\includes\theme.inc on line 955.
* warning: include(./modules/system/page.tpl.php) [function.include]: failed to open stream: No such file or directory in D:\drupal\includes\theme.inc on line 955.
* warning: include() [function.include]: Failed opening './modules/system/page.tpl.php' for inclusion (include_path='.;D:\xampp\php\pear\') in D:\drupal\includes\theme.inc on line 955.

Is it Drupal's problem? I'm using Drupal 6.0-rc2

anaru’s picture

anaru commented

Do you see this error at any time when BAWstats is not installed?

dennys’s picture

dennys commented

When I disable BAWstats, this error disappear. But I cannot make sure the root cause, maybe not due to BAWstats. Do you have any suggestion to distinguish ?

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.