Title: Too many debug errors
Last modified: August 21, 2016

---

# Too many debug errors

 *  Resolved [Mayeenul Islam](https://wordpress.org/support/users/wzislam/)
 * (@wzislam)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/too-many-debug-errors-1/)
 * I’s developing a site unaware about WP_DEBUG.
    In the way I became aware about
   it and enabled WP_DEBUG and found many undefined variable error in the widget
   of Subscribe2.
 * I added a full screen image of the errors, uploaded to my dropbox:
    [https://www.dropbox.com/s/rybg0khdm148zn3/subscribe2.jpg](https://www.dropbox.com/s/rybg0khdm148zn3/subscribe2.jpg)
 * I’m using Subscribe2 Version 9.0 and Version Subscribe2 Widget Pro 1.2.5.3
 * [http://wordpress.org/plugins/subscribe2-widget-pro/](http://wordpress.org/plugins/subscribe2-widget-pro/)

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

 *  Plugin Author [Devin Walker](https://wordpress.org/support/users/dlocc/)
 * (@dlocc)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/too-many-debug-errors-1/#post-4442783)
 * Thanks for the screenshot Mayeenul – I’ll be sure to take care of those notices
   in the next version. Look for that in a few days…
 *  Plugin Author [Devin Walker](https://wordpress.org/support/users/dlocc/)
 * (@dlocc)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/too-many-debug-errors-1/#post-4442796)
 * I’ve had a hard time reproducing those errors you see on the frontend. Which 
   version of PHP are you using?
 *  Thread Starter [Mayeenul Islam](https://wordpress.org/support/users/wzislam/)
 * (@wzislam)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/too-many-debug-errors-1/#post-4442797)
 * PHP 5.3.5, localserver, WAMP 2.1.
 * In `widget-output.php`, is that correct saying:
    `if (!empty($postto) && $postto!
   == 'home') {` on line 32 I’m thinking about `!==`, isn’t it should be `!=`? I
   actually am not a PHP dev., I may be wrong. 🙂
 * I `var_dump($postto)`, it’s returning `string '' (length=0)`.
 * Where is the $postto variable declared?
 * Thanks for your interest in fixing bugs. If you want more details, we can chat
   in gTalk: `wz.islam`. But using the forum is also fine for me. 🙂
 *  Plugin Author [Devin Walker](https://wordpress.org/support/users/dlocc/)
 * (@dlocc)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/too-many-debug-errors-1/#post-4442844)
 * Hey Mayeenul – I’m pushing out version 2.0 this weekend and would love for you
   to check it out! I’ve paid attention to fixing various bugs and it should be 
   running clean with WP_DEBUG set to true.
 *  Plugin Author [Devin Walker](https://wordpress.org/support/users/dlocc/)
 * (@dlocc)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/too-many-debug-errors-1/#post-4442845)
 * I’m going to mark this as resolved. If you notice any debug errors in version
   2.0+ please open a new topic. Thanks for checking out the plugin!

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

The topic ‘Too many debug errors’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/subscribe2-widget-pro_e8f0f9.svg)
 * [Subscribe2 Widget Pro](https://wordpress.org/plugins/subscribe2-widget-pro/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/subscribe2-widget-pro/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/subscribe2-widget-pro/)
 * [Active Topics](https://wordpress.org/support/plugin/subscribe2-widget-pro/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/subscribe2-widget-pro/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/subscribe2-widget-pro/reviews/)

## Tags

 * [errors](https://wordpress.org/support/topic-tag/errors/)
 * [Undefined Variables](https://wordpress.org/support/topic-tag/undefined-variables/)
 * [widget](https://wordpress.org/support/topic-tag/widget/)

 * 5 replies
 * 2 participants
 * Last reply from: [Devin Walker](https://wordpress.org/support/users/dlocc/)
 * Last activity: [12 years, 2 months ago](https://wordpress.org/support/topic/too-many-debug-errors-1/#post-4442845)
 * Status: resolved