Does the plugin allow having A/B testing to see which one of the plugins works for my case or is it just admin and user difference?
]]>The following error occurs when activating Plugin Test Drive on WordPress version 4.7.3
Fatal error: Cannot redeclare plugin_sandbox_scrape() (previously declared in /home/xxxxxx/public_html/wp-admin/includes/plugin.php:1880) in /home/xxxxxx/public_html/wp-content/plugins/plugin-test-drive/admin/options.php on line 256
Current Source Code in options.php
function plugin_sandbox_scrape( $ptd_plugin ) {
echo '<div style="font-size:14px">';include( WP_PLUGIN_DIR . '/' . $ptd_plugin );echo '</div>';
}
plugin_sandbox_scrape( $ptd_plugin );Suggested Change
function ptd_plugin_sandbox_scrape( $ptd_plugin ) {
echo '<div style="font-size:14px">';include( WP_PLUGIN_DIR . '/' . $ptd_plugin );echo '</div>';
}
ptd_plugin_sandbox_scrape( $ptd_plugin );PHP ERROR NOTICE
[14-Nov-2016 06:07:43 UTC] PHP Notice: Undefined index: tester_key_method in /home/mysite/public_html/wp-content/plugins/plugin-test-drive/plugin_test_drive.php on line 93
generated on
Multisite install w/ subdomains
using WP-multi-networks plugin
Running BuddyPress 2.7?
with BP-Multi-Network (the other one), no multiblog mode enabled
Main Theme is Kleo 4.1.6.2
FYI!
]]>Hello. Thank you for developing this plugin.
Note: I’ve changed the default WP directories on my installation.
Was running default version of PHP, now 7.
At this time I am unable to utilize this plugin as the following warning is generated upon install/activation:
PHP Warning: require_once(/home/wp-user/public_html/wp-content/plugins/plugin-test-drive/admin/main.php): failed to open stream: No such file or directory in /home/wp-user/public_html/my-dir/plugins/plugin-test-drive/plugin_test_drive.php on line 80
[25-Jul-2016 23:12:04 UTC]
PHP Fatal error: require_once(): Failed opening required ‘/home/wp-user/public_html/wp-content/plugins/plugin-test-drive/admin/main.php’ (include_path=’.:/opt/php54/lib/php’) in /home/wp-user/public_html/my-dir/plugins/plugin-test-drive/plugin_test_drive.php on line 80
curt
]]>It was working fine with 4.4.x, but once I upgraded to 4.5, I get the following error when loading my site:
Fatal error: Call to undefined function get_currentuserinfo() in /home/jrfs_admin/jamesriverfilm.org/wp-content/plugins/plugin-test-drive/plugin_test_drive.php on line 65
I guess this plugin is no longer actively developed given the fact that it’s only officially compatible with 3.9.x and below.
]]>LOCKS YOU DOWN
]]>We need a version compatible with 4.1.1
]]>Hye !
I’ve succeeded in saving options in the admin panel after a modification of the source code file script.js.
I’ve added this line at the very start of the file script.js:
Alert ("ok") ;
(with the A in capital, yes, syntax error, yes ! )
before the first one :
jQuery(document).ready(function() {
I don’t understand why, but it works (In fact, I was looking for a solution when I made this syntax error… )
I think it relies with a syntax error before this line (missing semi-column or something like that), or perhaps a bad script enqueueing.
I Don’t know how to re-open the topic “Can’t save altered options”
Hope it serves!
Xavier Giorgi.
]]>I have plug in test drive installed and it’s defaulted to testing by IP address. By whatever criteria it’s chosen the default it’s chosen one which is not mine. I wished to change it to username but the save button on the options page appears to do nothing. I’ve noticed that even check and unchecking plug ins to test on that page also doesn’t make any difference to this problem. I cannot make any changes on the option page (but adding plug ins to the testing list from say the wordpress plug in list for example works).
It’s a great idea to be able to test plug ins like this, I hope this issue can be resolved. Thanks for any help.
]]>When I try to fully activate a plugin without telling Plugin Test Drive to stop testing it first, activation fails with a “caused a fatal error” message.
If a plugin that PTD wants to test can’t be tested because it is activated in WordPress, that plugin should be silently removed from the testing list, so WP can go through with activating the plugin.
I hope I’ve made sense. I’m rushing to write this before I have to go; let me know if clarification is needed and I’ll get back to it in the next day or two.
]]>