Unsupported operand types in Browscap.php

How about the other things?

You mean the user agent setting? You can turn that off now.

Hm,

would like to help you but I’m on a multi site WP installation. There are as many option sections in the table as there are sites. Most of all I would not break anything.

Is there something else you wanna know Greg?

OK,

found it out myselves. The plugin is up and running and I will provide you a export of the table you requested in about an hour.

OK,

waited all night and found no wp_statistics_visitor table in my database.

Hi there, I’m getting the same error:

Fatal error: Maximum execution time of 30 seconds exceeded in /home/*******/public_html/veganstart.org/wp-content/plugins/wp-statistics/includes/classes/Browscap.php on line 355

I upgraded the plugin ~24hrs ago, and noticed tonight that the site was acting very sluggishly…pages wouldn’t load completely. Spotted this error at the bottom. Have disabled, site works fine again…there’s something going on.

Please advise, thanks!!

– Dave

@hjvd: your table might have a different prefix (wp_) on it, look for a table ending in statistics_visitor.

For those who are having issues with the page load timing out, I’ve found the problem, it’s a bug in the version of the browscap library, you can get the current version here:

https://raw.githubusercontent.com/browscap/browscap-php/2.0.5/src/phpbrowscap/Browscap.php

and replace the wordpress/wp-content/plugins/wp-statistics/includes/classes/browscap.php file with it to resolve the issue.

Still working on the Fatal Error message issue.

Hi Gregg,

still interested in my table?

Did a search for %statistics_visitor% and again no luck.

Would you lik an export form statistics-visitor from the plugin it selves?

Henk

@hjvd: that’s ok, I’ve been able to reproduce the issue and have a fix for it.

I’ve found the issue, it has to do with the latest browscap.ini file. The problem stems from the pruning WP Statistics does on the browscap.ini file to reduce it’s size to a more manageable level.

I’ll release an new version later today to resolve the issue, but you’ll likely have to manually (ie go to the Statistics->Settings->Externals page and select the “Download browscap” option) refresh the browscap file.

Would it not be reasonable to assume that Fatal error is also associated with browscap library?

Would you like me to do the following:
– get the latest browscap library as you suggested
– enable “whatever” in the settings of your plugin
– check error log to see fi Fatal is still present. But I think that if ti is page will not load.

Just help me to identify what that “whatever” check-box is in the settings.
You have already educate me what to change in the table if problem happens.

@pressthewords: The problem isn’t, per say, in the browscap library, but in the way WP Statistics uses it.

What’s happening is that we prune out any browser that isn’t a crawler as well as all the extra information that normally is associated with the browscap file. This takes the normally 34meg browscap.ini file down to just ~300k.

However, in doing so we drop out any browser that isn’t a crawler. The brwoscap file support “parent” browsers, so multiple patterns effectively match a single browser. This is were the problem came up as if the child browser is a crawler but the parent browser isn’t, then the child points to a parent that doesn’t exist.

This hadn’t come up before the latest release of the browscap.ini file, and in fact there is still only one occurrence of it, but in that case it threw the fatal error.

The update will rebuild the browscap file and if a child is a crawler but the parent isn’t, it will be dropped from the file as well.

This will reduce the detection of some crawlers, but the only other way to fix the issue would be to include all parents and children (if you don’t include them all you could get some false positives), which would balloon the file size up closer to the 30meg again.

Checked the error log from the Apache server and no errors after the manual update from Greg here. Well done.

Very well then. I will wait for plugin update.

You have my contact info.
Feel free to get in touch if you need assistance in testing.

Good work.