Title: WP_Debug Errors
Last modified: August 22, 2016

---

# WP_Debug Errors

 *  Resolved [Alex Mansfield](https://wordpress.org/support/users/alexmansfield/)
 * (@alexmansfield)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/wp_debug-errors-3/)
 * Hey UpThemes, I really love this plugin. I haven’t used it in a while, but I 
   just installed it again today and it’s generating some errors with WP_Debug turned
   on. I just thought I would let you know, in case you were developing it with 
   WP_Debug turned off. If you think that it’s somethign about my setup that’s causing
   the errors, please let me know. Here are the errors I’m getting.
 * On the backend:
 *     ```
       Strict Standards: Redefining already defined constructor for class Typecase in /var/www/html/wordpress-buildsome/wp-content/plugins/typecase/typecase.php on line 75
   
       Strict Standards: Non-static method Typecase_Pro::init() should not be called statically in /var/www/html/wordpress-buildsome/wp-content/plugins/typecase/pro.php on line 227
       ```
   
 * On the front end:
 * `Strict Standards: Non-static method Typecase_Pro::init() should not be called
   statically in /var/www/html/wordpress-buildsome/wp-content/plugins/typecase/pro.
   php on line 227`
 * …also, it gave me this notice in the WP admin area when I activated the plugin:
 * “The plugin generated 410 characters of unexpected output during activation. 
   If you notice “headers already sent” messages, problems with syndication feeds
   or other issues, try deactivating or removing this plugin.”
 * Like I said, I really like this plugin. Thanks for all the work you’ve put into
   it already!
 * [https://wordpress.org/plugins/typecase/](https://wordpress.org/plugins/typecase/)

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

 *  Plugin Author [Chris Wallace](https://wordpress.org/support/users/chriswallace/)
 * (@chriswallace)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/wp_debug-errors-3/#post-5599688)
 * Hey Alex,
 * We use Github for development and it looks like this issue has been noted there
   already:
 * [https://github.com/UpThemes/Typecase/issues/61](https://github.com/UpThemes/Typecase/issues/61)
 * We’ll get that fixed immediately and let you know once it’s been updated.
 * Thanks for using Typecase!
 * Chris
 *  Thread Starter [Alex Mansfield](https://wordpress.org/support/users/alexmansfield/)
 * (@alexmansfield)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/wp_debug-errors-3/#post-5599691)
 * Awesome! Thanks Chris.

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

The topic ‘WP_Debug Errors’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/typecase_e6cbb5.svg)
 * [Typecase Web Fonts](https://wordpress.org/plugins/typecase/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/typecase/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/typecase/)
 * [Active Topics](https://wordpress.org/support/plugin/typecase/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/typecase/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/typecase/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [Alex Mansfield](https://wordpress.org/support/users/alexmansfield/)
 * Last activity: [11 years, 5 months ago](https://wordpress.org/support/topic/wp_debug-errors-3/#post-5599691)
 * Status: resolved