rvry

It might be because of this line in wp-power-stats.php : 276

It’s checking if $data[‘search_engine’] is an array and if it is then it’s passing it to sanitize_data, which is expecting a string in strip_tags and not an array.

Could this also be why search keywords never appear in the statistics overview box?

// Get search engine keywords
self::$data[‘keywords’] = (is_array(self::$data[‘search_engine’])) ? self::sanitize_data(self::$data[‘search_engine’][‘keywords’]) : “”;

The php warnings are still appearing after updating ??

• This reply was modified 7 years ago by rvry.

I am exploring another plugin wp-power-stats which looks to be setting it’s own cookie rather than using PHPSESSID and it looks promising. I’m just making sure it’s not too heavy that it slows down WordPress loading times – that’s something I liked about this plugin, it looked very light indeed.

Strangely when I comment out session_start(), which stops PHPSESSID from being generated, it hasn’t helped Varnish to start caching my website. So whilst it is good if this plugin could be Varnish friendly I need to troubleshoot my own website.

Yes that’s where. I flattened the array into a string knowing the else condition on line 292 would pick it up while preserving the array check to minimise the changes.

ok I will try. Now that I now about the rename directory trick I feel more confident to give it a second go.

I found that the delete didn’t actually delete. I had to log in to shell and delete the directory from plugins. Now functionality is back.

I’m sure this plugin has worked successfully on previous WordPress installations and users, but for some reason it will not work either with this version or this setup, and my point stands that it needs to be very careful when playing with the admin pathway in.