Due to the current ongoing events surrounding two major players in the WordPress ecosystem, the author of this plugin is not comfortable signing in to www.remarpro.com under the current requirements provided on the login screen to offer support.
They have, for the time being, chosen to provide help via https://github.com/kevinohashi/WPPerformanceTester/issues to their users until these matters are resolved.
Please note that the 2.0.1 release may show the version number 2.0.0 in your WordPress admin dashboard, if you do not have any update notifications for the plugin you should already be on the 2.0.1 release with the latest fixes, as this is a display error.
]]>plugin version does not match
View post on imgur.com
]]>
Hi, not sure if you are familiar with BuddyBoss plugin but apparently they just added a tab with a performance test. This test is a benchmark test that looks exacly like your plugin: style, layout and even the perfomance benchmarks that are tested are identical.
So I am simply wondering if this is a blatant copy and paste or if you are co-operating or even in an affiliation with BuddyBoss?
]]>PHP Warning: Undefined array key “SERVER_ADDR” in …\wp-content\plugins\wpperformancetester\benchmark.php on line 42
This causes a 500 error in the browser.
]]>Hi,
I’d like to know if your plugin works with PHP 8.1.
I have a weired result that I’ve never got before :
Mysql Query Benchmark 4.686
Usually I’m getting 0.2 with your plugin. How can I replicate this test please directly on my server?
Thank you for your assistance.
]]>Does not seem to work correctly with MYSQL 8, as Mysql Query Benchmark is 0.001?
]]>Hi, after starting test
(yes on my own testdomain https://domaincontrol.at/ , not abusing) i got:
secret did not match , tested aborted.
a:1:{s:11:”secretmatch”;s:55353:”secret DOES NOT match secret:e41cd01aa60c3c04d20bfb04200ca725
Tried with AU and US servers, no chance.
When viewing the tester page under tools in WP Admin, a number of PHP warnings and notices crop up:
Notice: wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /srv/www/wordpress-default/public_html/wp-includes/functions.php on line 4204
Notice: wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /srv/www/wordpress-default/public_html/wp-includes/functions.php on line 4204
Notice: wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /srv/www/wordpress-default/public_html/wp-includes/functions.php on line 4204
Notice: wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /srv/www/wordpress-default/public_html/wp-includes/functions.php on line 4204
Notice: Undefined index: performTest in /srv/www/wordpress-default/public_html/wp-content/plugins/wpperformancetester/WPPerformanceTester_Plugin.php on line 15
]]>
Got this on trying to activate:
—–
Plugin could not be activated because it triggered a fatal error.
Fatal error: Cannot redeclare test_math() (previously declared in /public_html/wp-content/plugins/mywebtonet-performancestats/mywebtonet-performancestats.php:619) in /public_html/wp-content/plugins/wpperformancetester/benchmark.php on line 74
]]>On two of the three hosts I tested, the chart didn’t display – just a big gap where it was on later runs.
Don’t have more details than that ?? Next time it happens I’ll check the console for trouble.
]]>