Firestats Stopped Working After WordPress 2.3.3 Upgrade

[Anthony@…]

I've been unable to get FireStats to work after upgrading to Wordpress 2.3.3. I continually get 0 hits... go get some traffic when I view the Firestats page. I'm getting traffic... but firestats is now broken. I've gone as far as to delete firestats from blog/wp-content/plugins/firestats I've deleted the database tables... and reinstalled. The tables get re-created... but I continually see 0 hits. Not sure what the problem is, but... i miss the data that firestats was providing FYI: I did pay your nominal usage fee (don't recall the exact amount) for this product when I saw how valuable the data it provided was. Thanks for any help you can provide.

Anthony

[omry]

Hi Anthony,

• did you also upgrade your theme? if so, check the FAQ (look for wp_head there).
• what does the diagnostics page say?
• check your phpinfo, what is your php memory limit?

[omry]

also, following your email - I found your blog and saw that your FireStats is renamed to firestats-broken. rename it back and re-activate it, see if that helps.

[omry]

hmm, not just broken - but also deleted. reinstall it.

[anonymous]

Replying to omry:

hmm, not just broken - but also deleted. reinstall it.

firestats-broken was the original version that worked under WP2.0.2. I renamed it as i began the debug/reinstall process firestats was installed/reinstalled/deleted Tried firestats-installer. That didn't work so I re-installed by hand.. but still left me showing 0 traffic Most recent install shows 0 traffic FireStats System Test Shows the following:

Some of your tables are not using the InnoDB engine, which is required by FireStats. wierd things may happen (wp_firestats_archive_countries, wp_firestats_archive_pages, wp_firestats_archive_ranges, wp_firestats_archive_referrers, wp_firestats_archive_sites, wp_firestats_archive_useragents, wp_firestats_excluded_ips, wp_firestats_hits, wp_firestats_options, wp_firestats_sites, wp_firestats_url_metadata, wp_firestats_urls, wp_firestats_useragent_classes, wp_firestats_useragents, wp_firestats_users, wp_firestats_version)

I've not changed my database? Still using the same version of MySQL. I did delete the wp_firestats tables. These were re-created upon subsequent re-install attempts... but I still get this message when the test runs.

Not sure how this installed and worked so easily the first time... only to be so difficult to get running now?

I'm running the same theme. The only thing that changed... leading to firestats no longer working... was upgrading to WP2.3.3

Thoughts?

[omry]

• The error message you see (about InnoDB) is a warning. it should work even at this state.
• do you have a call to wp_head() in your theme header?
• any PHP error in the server log?
• You did not answer me about the memory limit.

[anonymous]

No call to wp_head in the theme header. This did not change recently. How do I view php server error logs. I'm on a Yahoo host... they don't seem to allow access to much of anything :-\ memory limit should be accessible from the attached phpinfo.php.html file, right? Thanks!

[omry]

Anthony, look inside your entire theme for wp_head(). if it's missing I can assure you that FireStats will NOT count hits from your page.

this is required by FireStats.

[anonymous]

:/opt/lampp/htdocs/wordpress/wp-content/themes/starry$ find . -name "*.*" | xargs grep wp_head ./functions.php:add_action('wp_head', 'kubrick_head');

this is the only one i found this is the way it was (working) before the wp2.3.3 upgrade

In a theme I'm not using, I found the following:

./default/header.php:<?php wp_head(); ?>

I can see about adding this?

[omry]

hmm. do call wp_head() as you seen on the other header.php file. it will have the side effect of also calling kubrik_head, which may or may not be desired. just see what happens when you call wp_head() in the header.

[anonymous]

Finally got into my logs.... Lots of the following:

[10-Apr-2008 11:27:04] WordPress database error Got error 134 from storage engine for query SELECT * FROM wp_bas_visitors, wp_bas_refer, wp_bas_ua, wp_bas_os WHERE referer = referer_id AND osystem = os_id AND useragent = ua_id AND lasthere > DATE_SUB(NOW(), INTERVAL 20 MINUTE) AND visit_ip = 1254686290 AND ua_string = ORDER BY lasthere DESC LIMIT 1

I don't see anything related to wp_firestats_*

[omry]

one of your plugins, not sure which.

"bas visitors" maybe?

[omry]

* bad visitors is not related to firestats. * assuming adding a call to wp_head() solved it.