WordPress.org

Ready to get started?Download WordPress

Forums

Game Schedules
[resolved] Errors after upgrade (6 posts)

  1. bevineau101
    Member
    Posted 8 months ago #

    Hello Mark-
    The plugins work but I get these errors. Any suggestions? Please advise...

    Warning: array_merge() [function.array-merge]: Argument #1 is not an array in /home/content/25/9298325/html/wp-content/plugins/game-schedules/mstw-game-schedule.php on line 2001

    Warning: Invalid argument supplied for foreach() in /home/content/25/9298325/html/wp-content/plugins/game-schedules/mstw-game-schedule.php on line 2005

    http://wordpress.org/plugins/game-schedules/

  2. Mark O'Donnell
    Member
    Plugin Author

    Posted 8 months ago #

    Hi benvineau101-
    Thanks for pointing this out. These are WARNINGS not ERRORS, and they won't hurt anything. I'm working to eradicate them all. There are a couple of things you can do:

    (a) First, are you running version 4.0.1? That's where I've made the fixes. Plus a couple of real bugs were fixed. See the plugin's Changelog for more details.

    (b) TURN DEBUG OFF. It should always be off on production servers. You can read more about this issue in this blog post.

    (c) Or if you are developing a theme or plugin and need debug on either live with the warnings on the screen, or if that bugs you, send them to a log file for later review.

    (c) Please keep sending them two me and I'll weed out the ones I know about as time allows.

    Thanks. Let me know how it goes.

    -Mark

  3. websparks
    Member
    Posted 8 months ago #

    For your info I get similar errors on frontend

    Warning: array_merge() [function.array-merge]: Argument #1 is not an array in /home/b00kie/public_html/wp-content/plugins/game-schedules/mstw-game-schedule.php on line 428

    Warning: Invalid argument supplied for foreach() in /home/b00kie/public_html/wp-content/plugins/game-schedules/mstw-game-schedule.php on line 431

    In my config file DEBUGGING is off (define('WP_DEBUG', false);)

  4. Mark O'Donnell
    Member
    Plugin Author

    Posted 8 months ago #

    Thanks websparks. Yes, you will get the same errors on the front end. It's because some display settings/(options) are empty. I will weed these two out in the next release.

    I'm not sure why debug messages are being written to the secreen if DEBUG is off. But let me assure you the plugin is not turning DEBUG on in your WordPress configuration. Really. Something else is. You might want to check out this Codex article http://codex.wordpress.org/Debugging_in_WordPress and/or try sending debug output to a log rather than the screen. The link to the blog post above also shows a way to turn the display off within the plugin by adding a line to the code.

    Let me know how it works out. Thanks.

    -Mark

  5. websparks
    Member
    Posted 7 months ago #

    Thanks Mark, hope you had a good xmas and New Year. I am pretty well stuck now with moving further with the Schedule plugin because of the errors. I realise that its a freebee so I cannot expect much. I was going to build a world cup schedule on my site, it is still a while away, I am hoping that you can iron out the bugs in the coming weeks, but if not I appreciate your contribution to the wordpress community. Cheers, Adrian

  6. Mark O'Donnell
    Member
    Plugin Author

    Posted 7 months ago #

    Hi websparks,
    Happy New Year. Sorry that you are stuck.

    First, to the best of my knowledge there are NO ERRORS in the Game Schedules plugin. ERRORS stop program execution. So if that's happening, please send me a screenshot of the ERROR message and I will do my best to fix it.

    I believe what you are seeing are NOTICES and WARNINGS. They do not stop, or even significantly impact, the program's execution. They are certainly NOT BUGS. You can witness the plugin working pretty well on my development site.

    I believe your frustration is coming from these notices and warnings being printed on the front and back end (admin) displays. Understandable. So again, you can fix that by stopping the debug messages from printing to the screen. There are several ways define('WP_DEBUG', false); might be changed or ignored but I can't debug every user's WP install or theme. If you follow the directions in the references I gave you above, you should be able to redirect the annoying messages from the screen to a file. It seems that will fix your problem. (If you would like some help doing that, please contact me at shoalsummitsolutions.com.)

    Regards,
    -Mark

Reply

You must log in to post.

About this Plugin

About this Topic

Tags

No tags yet.