Title: PHP Notice
Last modified: August 30, 2016

---

# PHP Notice

 *  Resolved [The Three](https://wordpress.org/support/users/3wwwgr/)
 * (@3wwwgr)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/php-notice-53/)
 * Hello there!
    I am getting this notice… any idea?
 * [28-Jun-2015 17:33:28 UTC] PHP Notice: Undefined variable: wp_scheduled_missed
   in /httpdocs/wp-content/plugins/wp-missed-schedule/wp-missed-schedule.php on 
   line 244
 * [https://wordpress.org/plugins/wp-missed-schedule/](https://wordpress.org/plugins/wp-missed-schedule/)

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Contributor [slangji](https://wordpress.org/support/users/slangji/)
 * (@slangji)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/php-notice-53/#post-6276984)
 * Disable Debug! !!
 * Thanks for using my plugin.
 *  [Pratham](https://wordpress.org/support/users/pratham2003/)
 * (@pratham2003)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/php-notice-53/#post-6277124)
 * Edited: Oh nevermind.
 *  Plugin Contributor [slangji](https://wordpress.org/support/users/slangji/)
 * (@slangji)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/php-notice-53/#post-6277128)
 * I know very well this construct.
 * I do not understand one thing: why this topic was opened by a user, and then,
   immediately afterwards, the answers are different to another user?
 * This will be the case of a person using different nik?
    This will be the case
   of a person who has already written a few days ago in the review?
 * Frankly I do not understand … or rather, I fully understand the desire to deliberately
   destroy a plugin, just for the pleasure of it, although I do not understand why,
   since mine is the only plug in the world, to repair the wordpress missed schedule
   bug! !!
 * Or maybe try at all costs to a defect in the code to show that the plugin is 
   harmful?
 * Thanks for using my plugin …
 *  Thread Starter [The Three](https://wordpress.org/support/users/3wwwgr/)
 * (@3wwwgr)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/php-notice-53/#post-6277168)
 * Hello sLa NGjl’s,
 * I don’t have anything to do with “pratham2003”!
 * I am just getting this notice in debug.log. I am **NOT** worried about this, 
   because it is just a NOTICE and not an ERROR!
    Furthermore, this plugin is working**
   PERFECT** on my site (20.000+ visitor and 40+ scheduled post per day).
 * I will post one more time the notice… if you say that i should just deactivate
   debug ok, but if you may have any idea what this notice may be, please let me
   know… Thank you!
 * [04-Jul-2015 18:14:43 UTC] PHP Notice: Undefined variable: wp_scheduled_missed
   in /httpdocs/wp-content/plugins/wp-missed-schedule/wp-missed-schedule.php on 
   line 244
 * line 244: set_transient( ‘wp_scheduled_missed’, $wp_scheduled_missed, 600 )
 * [04-Jul-2015 18:14:43 UTC] PHP Notice: Use of undefined constant wp_scheduled_missed–
   assumed ‘wp_scheduled_missed’ in /httpdocs/wp-content/plugins/wp-missed-schedule/
   wp-missed-schedule.php on line 246
 * line 246: $wp_scheduled_missed = get_transient( wp_scheduled_missed, false )

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘PHP Notice’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wp-missed-schedule_8d8370.svg)
 * [Missed Schedule Fix WP Failed Future Posts](https://wordpress.org/plugins/wp-missed-schedule/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-missed-schedule/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-missed-schedule/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-missed-schedule/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-missed-schedule/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-missed-schedule/reviews/)

 * 4 replies
 * 3 participants
 * Last reply from: [The Three](https://wordpress.org/support/users/3wwwgr/)
 * Last activity: [11 years, 2 months ago](https://wordpress.org/support/topic/php-notice-53/#post-6277168)
 * Status: resolved