Forum Replies Created

Viewing 15 replies - 1 through 15 (of 22 total)
  • Ok. Thanks.

    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.

    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 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: “http://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: “http://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: “http://www.chestnutridgemc.org/”

    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 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.

    I’m having same problem with no hits recorded. Our php version is at php7. Is this also a problem?

    Thread Starter Ziggy43

    (@ziggy43)

    Thanks Hal.
    Looks like a simple and elegant solution.
    In the process, I learned something about WP filters! Win, win!

    I’m noticing that it seems the the wind speed changes when settings are changed from F to C but the wind speed units remain m/s.
    I corrected that with:
    add_filter( ‘awesome_weather_wind_speed’, ‘tweak’, 10, 1);

    function tweak($sym) {
    if($sym[‘units’] == ‘imperial’) {
    $sym[‘text’] = ‘ mph ‘;
    }
    return $sym;
    }
    and when the apply_filters is called I added units to the array as:
    $wind_speed_obj = apply_filters(‘awesome_weather_wind_speed’, array( ‘text’ => __(‘m/s’, ‘awesome-weather’),’speed’=> $today->wind->speed, ‘direction’ => $wind_direction, ‘units’ => $units), $today->wind->speed, $wind_direction );

    Would this be correct? thanks I appreciate your work.
    Ziggy

    I just upgraded and tried 4.0.2 both on “sandbox” and now online. It has removed the \’s in the “meta” field and is editing again. Thanks guys!

    I have sent a copy to the address you specified. One more observation: it seems that repeatedly hitting the save button will fill the meta datafield with the \’s and then at some point you can enter data and find that it no longer actually saves. Since \ is the escape character could there be some scenario that the data is being escaped to death? I think there may be some automajical escaping done maybe in WP or even Mysql? Not sure but may need worked around.

    I did some experimenting. I noticed that the field “meta” in the entry in the table wp_maxbuttonsv3 for the button in question seemed to be an account of edits:who, when and such, and was full of \’s. Other buttons that I can edit do not have those and buttons that I have not edited in this version have NULL. I simply deleted the “meta” entry for my “bad” button from the database (using phpmyadmin) and VOILA! I was again able to edit my “bad” button. I’m noticing that several \’s are added to the meta entry each time an edit takes place. Could this entry have been filled up with the \’s to overflow causing the server to refuse the update?
    Ziggy

    I am experiencing a similar problem. I have been using Maxbuttons for at least a year with no problems with several upgrades from older version 3. Yesterday afternoon I was “tweaking” a previously designed button and after several changes it ceased to save – the button appears to be working and the page comes back with the unedited (reverted) information. It seemed like something “timed out”. This morning I again tried to edit the same button and again no changes were saved. HOWEVER, I was able to edit a different button. I was working for several hours yesterday and I just did a few changes to the other button this morning. I was able to make changes to the “bad” button using Phpmyadmin directly on the database. I have about 6 buttons and I would be glad to provide a copy of that table from my database. Thanks for your work. Ziggy

    —- Begin System Info —– (my offline “sandbox” test system)
    WordPress Version:4.3.1
    PHP Version:5.5.9-1ubuntu4.13
    MySQL Version:5.5.44
    Web Server:Apache/2.4.7 (Ubuntu)
    WordPress URL:http://172.16.0.109
    Home URL:http://172.16.0.109
    PHP cURL Support:No
    PHP GD Support:Yes
    PHP Memory Limit:256M
    PHP Post Max Size:400M
    PHP Upload Max Size:400M
    WP_DEBUG:Disabled
    Multi-Site Active:No
    Operating System:Linux
    Browser:Mozilla Firefox 41.0
    User Agent:Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:41.0) Gecko/20100101 Firefox/41.0
    Active Theme:
    -Twenty Fourteen Child 1.0.0
    http://minicrwp/twenty-fourteen-child/
    Active Plugins:
    -Awesome Weather Widget 1.5.3.1
    https://halgatewood.com/awesome-weather
    -CR-Bulletins 3.3.1
    http://chestnutridgemc.org
    -CR-Calendar 1.4.0.jgz
    http://www.kieranoshea.com
    -cr-prayer 0.1
    http://wordpress.org/extend/plugins/cr-prayer/
    -CR-Sermons 4.2.0
    http://chestnutridgemc.org
    -Display Posts Shortcode 2.5.1
    http://www.billerickson.net/shortcode-to-display-posts/
    -Easy Pie Maintenance Mode 0.6.7
    http://easypiewp.com/easy-pie-maintenance-mode-faq/
    -Fourteen Colors 1.2
    http://celloexpressions.com/plugins/fourteen-colors
    -MaxButtons 4.0.1
    http://maxbuttons.com
    -Media File Manager Advanced 1.1.5
    -Simple Session Support 1.1
    http://devondev.com/simple-session-support/
    -SSH SFTP Updater Support 0.7.1
    http://phpseclib.sourceforge.net/wordpress.htm
    -WP Statistics 9.6.5
    http://wp-statistics.com/
    —– End System Info —–

    I was able to do a “re-install” of 4.2.2 on “sandbox” using version 0.6.1. Not sure if that totally proves it but again looks good. Thanks

    Looking good now. I have installed 0.6.1 on “sandbox” and was able to delete “Hello Dolly” plugin. I was also able to upgrade another plugin that offered an upgrade today.

    FYI I was upgrading WP from 4.2.1 to 4.2.2 when I discovered the original “retry – are you sure you want to do this” error. I have not been offered any additional WP upgrades to try it on. Thanks a big bunch for your quick response. Jim

Viewing 15 replies - 1 through 15 (of 22 total)