• Resolved rsps

    (@rsps)


    hi
    When I updated to the new version of the plugin. Statistics plugin does not work

    web-site:bmccu.ir

    Thanks

Viewing 10 replies - 16 through 25 (of 25 total)
  • I don’t have access to those logs. I get the email messages but no hits have been recorded since the last upgrade. Running version 10.3 of the plugin.

    Plugin Contributor Greg Ross

    (@gregross)

    If your running 10.3, double check your exclusions settings.

    You should be able to contact your hosting provider to get access to your PHP logs.

    I’m sorry, I was too busy “multitasking” yesterday and didn’t notice that I was observing the version number running on my local test system and NOT the one on the ISP live site which was 11.0. This morning I caught that and uploaded the 10.3 version and it appears to be working and counting visitors. My ISP appears to have PHP ver 7.0.8-4. I will see if they can provide logs for the time 11.0 was running. Thanks.

    I was able to get a log from my ISP. The tech there said that while running 10.3 there were no errors but on the dates running 11.0 there were errors.
    We are “chestnutridgemc” aka “www.chestnutridgemc.org”

    Here is what he sent:
    2016/11/04 11:47:08 [error] 12889#12889: *4995096 FastCGI sent in stderr: “PHP message: PHP Fatal error: Uncaught Exception: Invalid prefix length in /chroot/home/chestnutridgemc/public_html/wp-content/plugins/wp-statistics/vendor/s1lentium/iptools/src/Network.php:85
    #0 /chroot/home/chestnutridgemc/public_html/wp-content/plugins/wp-statistics/vendor/s1lentium/iptools/src/Network.php(53): IPTools\Network::prefix2netmask(255, ‘IPv4’)
    #1 /chroot/home/chestnutridgemc/public_ht” while reading upstream, client: 198.51.243.14, server: chestnutridgemc.org, request: “GET / HTTP/1.1”, upstream: “fastcgi://unix:/var/run/php/php7.0-fpm.sock:”, host: “www.chestnutridgemc.org”, referrer: “https://www.chestnutridgemc.org/axis-youth-activities/”
    #2 /chroot/home/chestnutridgemc/public_html/wp-content/plugins/wp-statistics/includes/classes/hits.class.php(159): IPTools\Range::parse(‘24.101.203.94/2…’)
    #3 /chroot/home/chestnutridgemc/public_html/wp-content/plugins/wp-statistics/includes/classes/hits.geoip.class.php(13): Hits->__construct()
    #4 /chroot/home/chestnutridgemc/public_html/wp-content/plugins/wp-statistics/wp-statistics.php(258): GeoIPHits->__construct()
    #5 /chroot/home/chestnutridgemc/public_html/wp-includes” while reading upstream, client: 198.51.243.14, server: chestnutridgemc.org, request: “GET / HTTP/1.1”, upstream: “fastcgi://unix:/var/run/php/php7.0-fpm.sock:”, host: “www.chestnutridgemc.org”, referrer: “https://www.chestnutridgemc.org/axis-youth-activities/”
    2016/11/04 11:47:09 [error] 12889#12889: *4995190 FastCGI sent in stderr: “PHP message: PHP Fatal error: Uncaught Exception: Invalid prefix length in /chroot/home/chestnutridgemc/public_html/wp-content/plugins/wp-statistics/vendor/s1lentium/iptools/src/Network.php:85
    #0 /chroot/home/chestnutridgemc/public_html/wp-content/plugins/wp-statistics/vendor/s1lentium/iptools/src/Network.php(53): IPTools\Network::prefix2netmask(255, ‘IPv4’)
    #1 /chroot/home/chestnutridgemc/public_html/wp-content/plugins/wp-statistics/vendor/s1lentium/iptools/src/Range.php(43): IPTools\Network::parse(‘24.101.203.94/2…’)
    #2 /chroot/home/chestnutridgemc/public_html/wp-content/plugins/wp-statistics/includes/classes/hits.class.php(159): IPTools\Range::parse(‘24.101.203.94/2…’)
    #3 /chroot/home/chestnutridgemc/public_html/wp-content/plugins/wp-statistics/includes/classes/hits.geoip.class.php(13): Hits->__construct()
    #4 /chroot/home/chestnutridgemc/public_html/wp-content/plugins/wp-statistics/wp-statistics.php(258): GeoIPHits->__construct()
    #5 /chroot/home/chestnutridgemc/public_html/wp-includes” while reading response header from upstream, client: 198.51.243.14, server: chestnutridgemc.org, request: “GET /?wordfence_logHuman=1&hid=19D2452E22595879A960982D781CA7C0&r=0.34412139066464276 HTTP/1.1”, upstream: “fastcgi://unix:/var/run/php/php7.0-fpm.sock:”, host: “www.chestnutridgemc.org”, referrer: “https://www.chestnutridgemc.org/”

    Karimi Gonabadi

    (@amirkariminooghabi)

    Hi ,
    I have this issue too .
    I said to my web hosting and he said “We can upgrade your php to 5.6 !”
    Is this OK ?
    Is my plugin after update my php to 5.6 work well ?
    Thanks …

    Plugin Contributor Greg Ross

    (@gregross)

    @amirkariminooghabi: 5.6 is fully supported.

    @ziggy43: That seems like a strange fatal error, I’ve tested with PHP 7.0.10 but I did find some issues with previous versions so this may be a PHP issue.

    Googling “PHP Fatal error: uncaught exception” it looks like there was an exception and it was not “caught” and dealt with in the code. In this case it should be somewhere in the “Network.php” written by Safarov Alisher when the $prefixlength variable is not a numeric. It is looking like there is some error that the author wishes to flag in the data being processed?

    I also found this re PHP 7 at php.net:

    PHP 7 changes how most errors are reported by PHP. Instead of reporting errors through the traditional error reporting mechanism used by PHP 5, most errors are now reported by throwing Error exceptions.

    As with normal exceptions, these Error exceptions will bubble up until they reach the first matching catch block. If there are no matching blocks, then any default exception handler installed with set_exception_handler() will be called, and if there is no default exception handler, then the exception will be converted to a fatal error and will be handled like a traditional error.

    As the Error hierarchy does not inherit from Exception, code that uses catch (Exception $e) { … } blocks to handle uncaught exceptions in PHP 5 will find that these Errors are not caught by these blocks. Either a catch (Error $e) { … } block or a set_exception_handler() handler is required.

    Plugin Contributor Greg Ross

    (@gregross)

    @ziggy43 The exception is because of an invalid range, I’ll have to add some error trapping code to handle it properly.

    Ok. Thanks.

Viewing 10 replies - 16 through 25 (of 25 total)
  • The topic ‘problem after update Plugin’ is closed to new replies.