Please consider that PHP 5.6 is now on its end of life, the support has been extended more than usual but it is going to be over by the end of this year.
https://php.net/supported-versions.php

There are so many benefits to migrate to PHP 7 and your great plugin should also benefit from it. Thank you!

Just run same compatibility check and got errors. Are these relevant? Does WP Help work on PHP7?

Thx

ERROR REPORT
Name: WP Help

FILE: /wp-content/plugins/wp-help/lib/requirements-check.php
——————————————————————————————————————————————————————————
FOUND 0 ERRORS AND 2 WARNINGS AFFECTING 2 LINES
——————————————————————————————————————————————————————————
40 | WARNING | Method name “CWS_WP_Help_Requirements_Check::__php_at_least” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
59 | WARNING | Method name “CWS_WP_Help_Requirements_Check::__wp_at_least” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
——————————————————————————————————————————————————————————

FILE: /wp-content/plugins/seo-ultimate/modules/404s/fofs-log.php
———————————————————————————————————–
FOUND 1 ERROR AFFECTING 1 LINE
———————————————————————————————————–
60 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
———————————————————————————————————–

Figured you may want to know so this can get fixed before an increasing amount of people become affected. There’s a few other plugins I work on that had the same issue, and the fix is really simple…depending on how far you want to dig.

( ! ) Fatal error: Uncaught Error: [] operator not supported for strings in C:\wamp64\www\NCWA\wp-content\plugins\badgeos-community-add-on\includes\bp-members.php on line 222
( ! ) Error: [] operator not supported for strings in C:\wamp64\www\NCWA\wp-content\plugins\badgeos-community-add-on\includes\bp-members.php on line 222
Call Stack
#	Time	Memory	Function	Location
1	0.0000	375808	{main}( )	...\index.php:0
2	0.0010	377824	require( 'C:\wamp64\www\NCWA\wp-blog-header.php' )	...\index.php:17
3	0.0010	393256	require_once( 'C:\wamp64\www\NCWA\wp-load.php' )	...\wp-blog-header.php:13
4	0.0010	405944	require_once( 'C:\wamp64\www\NCWA\wp-config.php' )	...\wp-load.php:37
5	0.0020	507736	require_once( 'C:\wamp64\www\NCWA\wp-settings.php' )	...\wp-config.php:94
6	1.1821	99940392	do_action( )	...\wp-settings.php:448
7	1.1821	99940768	WP_Hook->do_action( )	...\plugin.php:453
8	1.1821	99940768	WP_Hook->apply_filters( )	...\class-wp-hook.php:323
9	1.4311	107496624	bp_init( )	...\class-wp-hook.php:298
10	1.4311	107496624	do_action( )	...\bp-core-dependency.php:235
11	1.4311	107497000	WP_Hook->do_action( )	...\plugin.php:453
12	1.4311	107497000	WP_Hook->apply_filters( )	...\class-wp-hook.php:323
13	1.4471	107660920	bp_setup_nav( )	...\class-wp-hook.php:298
14	1.4471	107660920	do_action( )	...\bp-core-dependency.php:123
15	1.4471	107661296	WP_Hook->do_action( )	...\plugin.php:453
16	1.4471	107661296	WP_Hook->apply_filters( )	...\class-wp-hook.php:323
17	1.4611	107705528	BadgeOS_Community_Members->setup_nav( )	...\class-wp-hook.php:298

I’m wanting to know if there are any significant reasons or concerns why I should not upgrade my site to PHP7, after reading this article:

https://wpengine.com/support/php-7-faq/

… and running this PHP 7 test plugin:

https://www.ads-software.com/plugins/php-compatibility-checker/

… and seeing these warnings:

FILE: /nas/content/staging/fipweb/wp-content/plugins/addthis/addthis_social_widget.php
————————————————————————————————————————————————–
FOUND 0 ERRORS AND 2 WARNINGS AFFECTING 2 LINES
————————————————————————————————————————————————–
1986 | WARNING | Function name “__return_false” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
1994 | WARNING | Function name “__return_true” is discouraged; PHP has reserved all method names with a double underscore prefix for future use
—————————————————————————————————————————————————————————————————————————

… associated with the plugin:

https://www.ads-software.com/plugins/addthis/

Please advise if these warnings can be safely ignored before updating to PHP7.

THANKS!

I’m wanting to know if there are any significant reasons or concerns why I should not upgrade my site to PHP7, after reading this article:

https://wpengine.com/support/php-7-faq/

… and running this PHP 7 test plugin:

https://www.ads-software.com/plugins/php-compatibility-checker/

… and seeing these warnings:

FILE: /nas/content/staging/fipweb/wp-content/plugins/better-search-replace/includes/class-bsr-compatibility.php
—————————————————————————————————————
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
—————————————————————————————————————
54 | WARNING | INI directive ‘safe_mode’ is deprecated since PHP 5.3 and removed since PHP 5.4
———————————————————————————————————————————————————————

… associated with the plugin:

https://www.ads-software.com/support/plugin/better-search-replace

Please advise if these warnings can be safely ignored before updating to PHP7.

THANKS!

—-
Warning: A non-numeric value encountered in /home/eflowers/public_html/wp-content/plugins/duracelltomi-google-tag-manager/integration/woocommerce.php on line 1043
—-

I have wordpress 4.8, WooCommerce 3.1.1 and PHP 7.1

Anything I can do so I can take out this warning?

I’m looking to upgrade my php in my host to PHP7.

I’ve downloaded PHP Compatibility Checker and it seems that of all my plugins, Super Socializer is the only one with a problem.

There’s a warning saying :

—————————–
FILE: /home/[hidden]/public_html/wp-content/plugins/super-socializer/library/LiveJournalLogin/class.openid.v3.php

FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE 20 | WARNING | Use of deprecated PHP4 style class constructor is not supported since PHP 7.
————————

I’m worried Super Socializer will break my site if I switch to PHP7 =(

Chris.

Do you have plans to fix that and when will it be done?

File: /apps/CareerSite/careersite/wp-admin/includes/class-pclzip.php
> Line 292: Function argument(s) returned by “func_get_args” might have been modified

func_get_args();
> Line 475: Function argument(s) returned by “func_get_args” might have been modified
func_get_args();
> Line 732: Function argument(s) returned by “func_get_args” might have been modified
func_get_args();
> Line 889: Function argument(s) returned by “func_get_args” might have been modified
func_get_args();
> Line 1031: Function argument(s) returned by “func_get_args” might have been modified
func_get_args();
> Line 5345: Removed function “set_magic_quotes_runtime” called
set_magic_quotes_runtime(0);
> Line 5376: Removed function “set_magic_quotes_runtime” called
set_magic_quotes_runtime($this->magic_quotes_status);

File: /apps/CareerSite/careersite/wp-admin/includes/class-wp-ajax-upgrader-skin.php
> Line 94: Function argument(s) returned by “func_get_args” might have been modified
func_get_args();
> Line 110: Function argument(s) returned by “func_get_args” might have been modified
func_get_args();
> Line 129: Function argument(s) returned by “func_get_args” might have been modified
func_get_args();

File: /apps/CareerSite/careersite/wp-admin/includes/dashboard.php
> Line 996: Function argument(s) returned by “func_get_args” might have been modified
func_get_args();

File: /apps/CareerSite/careersite/wp-admin/includes/class-wp-upgrader-skin.php
> Line 149: Function argument(s) returned by “func_get_args” might have been modified
func_get_args();

File: /apps/CareerSite/careersite/wp-admin/includes/class-bulk-upgrader-skin.php
> Line 58: Function argument(s) returned by “func_get_args” might have been modified
func_get_args();

File: /apps/CareerSite/careersite/wp-admin/includes/media.php
> Line 534: Function argument(s) returned by “func_get_args” might have been modified
func_get_args();

File: /apps/CareerSite/careersite/wp-admin/includes/class-automatic-upgrader-skin.php
> Line 76: Function argument(s) returned by “func_get_args” might have been modified
func_get_args();