PHP7 Compatibility?

  • Resolved kranzoky

    (@kranzoky)


    8 years, 1 month ago

    Since WordPress will start requiring PHP7 as the minimum this year, I was wondering when the plugin will be updated to support PHP7?

    Below is what was found when a PHP7 compatibility check was performed:

    895 | WARNING | Method name “WordPressPopularPosts::__activate” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
    951 | WARNING | Method name “WordPressPopularPosts::__deactivate” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
    983 | WARNING | Method name “WordPressPopularPosts::__upgrade” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
    1048 | WARNING | Method name “WordPressPopularPosts::__do_db_tables” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
    1095 | WARNING | Method name “WordPressPopularPosts::__check_requirements” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
    1404 | WARNING | Method name “WordPressPopularPosts::__flush_transients” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
    1425 | WARNING | Method name “WordPressPopularPosts::__update_views” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
    1783 | WARNING | Method name “WordPressPopularPosts::__get_popular_posts” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
    1901 | WARNING | Method name “WordPressPopularPosts::__render_popular_post” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
    1982 | WARNING | Method name “WordPressPopularPosts::__cache” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
    2461 | WARNING | Method name “WordPressPopularPosts::__get_img” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
    2523 | WARNING | Method name “WordPressPopularPosts::__image_resize” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
    2555 | WARNING | Method name “WordPressPopularPosts::__get_image_file_paths” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
    2666 | WARNING | Method name “WordPressPopularPosts::__get_attachment_id” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
    2702 | WARNING | Method name “WordPressPopularPosts::__fetch_external_image” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
    2993 | WARNING | Method name “WordPressPopularPosts::__format_content” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
    3114 | WARNING | Method name “WordPressPopularPosts::__get_image_sizes” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
    3186 | WARNING | Method name “WordPressPopularPosts::__is_numeric” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
    3196 | WARNING | Method name “WordPressPopularPosts::__curdate” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
    3206 | WARNING | Method name “WordPressPopularPosts::__now” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
    3216 | WARNING | Method name “WordPressPopularPosts::__microtime_float” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
    3234 | WARNING | Method name “WordPressPopularPosts::__merge_array_r” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
    3257 | WARNING | Method name “WordPressPopularPosts::__is_bot” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
    3281 | WARNING | Method name “WordPressPopularPosts::__debug” is discouraged; PHP has reserved all method names with a double underscore prefix for future use

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Hector Cabrera

    (@hcabrera)

    Hi there!

    I’ve been a bit out of the loop due to work and life in general in the past few months so I hadn’t heard/read anything related to WP bumping minimun PHP version to 7.0. Did a quick search just now and found this which basically says that it’s the recommended version that’s getting a bump by mid 2017. I guess that the minimum version will get a bump too but it won’t be PHP 7 for sure (that would break most WP sites out there!)

    Worry not, my friend. Fortunately someone else posted about these warnings not too long ago and yesterday I created an issue on Github so I don’t forget looking into it ??

    Thread Starter kranzoky

    (@kranzoky)

    Okay, great.

    Thanks!

    Excellent news, good to know it will soon be PHP7 ready ?? .

    Plugin Author Hector Cabrera

    (@hcabrera)

    Since it was an easy fix I went ahead and renamed all conflicting methods already. I’ll push a new update (WPP 4.0) as soon as I can ??

    davidleininger

    (@davidleininger)

    Any idea on when we can expect this update? I’m needing to migrate my site.

    Plugin Author Hector Cabrera

    (@hcabrera)

    Honestly, no idea. Freelance, my day job and life in general have been keeping me really busy lately. I did update version 4 to add support for PHP 7.x, it’s just not ready for general use yet because there are a few existing features that haven’t been migrated to 4.0 / properly tested yet.

    Thread Starter kranzoky

    (@kranzoky)

    I am assuming the warnings are just recommended to be changed and these won’t break anything if I was to upgrade to PHP 7, correct?

    Plugin Author Hector Cabrera

    (@hcabrera)

    Correct, plugins/themes getting this warning message will still work fine under PHP7. The notice is there to tell us developer “hey, we’re doing this sometime in the future so you prepare for it.”

    Of course it’s nicer to have code that doesn’t trigger any warning / error messages at all, which is why I implemented the requested change already ??

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘PHP7 Compatibility?’ is closed to new replies.