First, thanks to everyone who has sent in great feedback on a couple of bugs in version 4.0. Here’s the status:
1. There were two “one word” bugs that caused important parts of the plug-in to fail. They have been repaired and their description in what will be the version 4.0.1 readme.txt file follows:
- Problem with Schedule DB entries, Team selection from Teams DB being ignored
- Problem with Game entries, Location selection from Locations Plugin DB being ignored
They have both been repaired. In fact, the patch has been tested by a couple of you guys that reported the problem. (Thanks again.)
2. Okay, so how do you get the patch, or if you want to wait for a clean release, how to you go back to the previous version of the plugin? Well, you can get any version of the plugin you want from WordPress.org’s plugin repository at http://wordpress.org/plugins/game-schedules/developers/. In fact, you can even get the current development version (whatever I’ve checked-in)! And it just so happens I’ve checked in the patch. Only one file has been changed /includes/mstw-game-schedules-admin.php so that’s all you really need to load.
3. Finally, there has been a lot of complaining about PHP Warnings being generated. In some cases, users have not been able to silence the warnings by turning off WP debugging in their wp-config.php file. First, okay, uncle, I promise to work on getting rid of all the warnings generated by all my plugins starting with this one. It’s ‘best practice’ coding, and someone finally convinced me of some benefits by hitting me over the head. Ok, got it. Mea culpa!
In the meantime, I can’t fix everyone’s PHP/WP configuration, but I’m pretty sure you CAN silence all warnings in any PHP/WP configuration. Here’s what I would suggest:
First, I suggest reading Debugging in WordPress from the Codex
Next, as the above article explains, you have more than WP_DEBUG at your disposal. For example, if you can replace the line
define('WP_DEBUG', false); or define('WP_DEBUG', false);
in your wp-config.php with some combination of the following lines, you should remove error reporting from the screen and log errors in the /wp-content/debug.log file.
// Turn WordPress debugging on
define('WP_DEBUG', true);
// Log everything to the /wp-content/debug.log file
define('WP_DEBUG_LOG', true);
// Doesn't force the PHP 'display_errors' variable to be on
define('WP_DEBUG_DISPLAY', false);
// Hides errors from being displayed on-screen
@ini_set('display_errors', 0);
NOTE that I’m not recommending logging all “errors” to a file because that file will get VERY large quickly. But some simple modifications of the above lines will remove the logging to a file and the screen.
Finally, you can add (un-remark) this line at the top of the mstw-game-schedules-admin.php file:
error_reporting(0);
I just finished testing the lines above in the wp-config.php file on my plugin dev site and they worked. Then I add this line to mstw-game-schedules-admin.php and it stopped the log file from growing. But again, your mileage my vary because the simple WP_DEBUG variable in the wp-config.php disables all reporting in my environment.
Good luck. Please let me know how it goes. There’s always something new to learn about WordPress, which keeps me interested.