Ack, that is no good. I’ll need some time to try to reproduce this one but will look into this today.
Hi Ronald.
Let me know if you need further information or need access to any of our sites.
Best regards.
It’s weird it’s happening on different hosting providers.
I narrowed it down to PHP sockets not being enabled by the PHP install. For example, socket_create is a PHP function, but since it couldn’t be accessed, it tried to find it in the namespace instead, which doesn’t exist, hence the fatal error.
http://php.net/manual/en/function.socket-create.php
http://php.net/manual/en/book.sockets.php
Hi Ronald
That is the same conclusion we arrived at, but the hosting provider tells us, that PHP Sockets never was installed on the server, so we can’t figure out why this fails now?
Did the plugin “always” use PHP Sockets? Do we need PHP Sockets to be able to use the plugin?
Thanks
With the current library, yes.
It looks like I introduced the error in 1.7.0. Very sorry about that. I updated the library Nathan originally used to make better use of Google’s measurement protocol, which uses the sockets.
I suggest in the short-term to revert back to 1.6.5 and I’ll ditch the library for a more WordPress-friendly approach.
I’ll get to this this weekend.
Very sorry for the inconvenience.
Just reverted to the 1.6.5 library in 1.7.3 while keeping the 1.7.0 features in.
Marking as resolved, but please let me know if you have any additional issues.
Awesomeness!!!
Updated the plugin on two sites and tested on both – Works like a charm again.
So now we can update all our sites and get back to business :o)
Yayness! Sorry for the issues!
