Title: Debug (!)Notice harm/delay cms/blogs ?
Last modified: August 20, 2016

---

# Debug (!)Notice harm/delay cms/blogs ?

 *  Resolved [another-webmaster](https://wordpress.org/support/users/another-webmaster/)
 * (@another-webmaster)
 * [14 years, 2 months ago](https://wordpress.org/support/topic/debug-notice-harmdelay-cmsblogs/)
 * Once a while I activate the debug option (wp-config.php)and see notices like:
   `(!)
   Notice: wp_enqueue_script was called incorrectly. Scripts and styles should not
   be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts,
   or init hooks. Please see Debugging in WordPress for more information. (This 
   message was added in version 3.3.) in \wordpress\wp-includes\functions.php on
   line 3587` My question, can it harm and/or does it create delays on a site or
   blog? The scripts/plugins seem to work okay so therefore my question. Or is it“
   just” because of not “100%” programming and more a msg which could be ignored?

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

 *  [esmi](https://wordpress.org/support/users/esmi/)
 * (@esmi)
 * [14 years, 2 months ago](https://wordpress.org/support/topic/debug-notice-harmdelay-cmsblogs/#post-2659538)
 * In this case, I’d suggest that you investigate the problem – otherwise your script(
   s) may break in future versions of WordPress.
 *  Thread Starter [another-webmaster](https://wordpress.org/support/users/another-webmaster/)
 * (@another-webmaster)
 * [14 years, 2 months ago](https://wordpress.org/support/topic/debug-notice-harmdelay-cmsblogs/#post-2659542)
 * Thank you for the fast respond Esmi.
 * Sadly enough it isn’t my script (I am not good enough for such lol) but one of
   the scripts is the “WordPress Admin Bar Improved” plugin which creates 2 msg,
   1 is for style and other for script. Reported them 2 month ago but seem not yet
   be solved. (The plugin I personally like and as mentioned seems to work correctly
   from the outside).
 *  [esmi](https://wordpress.org/support/users/esmi/)
 * (@esmi)
 * [14 years, 2 months ago](https://wordpress.org/support/topic/debug-notice-harmdelay-cmsblogs/#post-2659544)
 * In that case, all you can do is report the issue to the plugin’s developer & 
   hope that it is fixed in a future update. Right now, it’s not a deal breaker 
   but it might be worth keeping an eye on the site’s behaviour/performance as you
   upgrade WordPress.
 *  Thread Starter [another-webmaster](https://wordpress.org/support/users/another-webmaster/)
 * (@another-webmaster)
 * [14 years, 2 months ago](https://wordpress.org/support/topic/debug-notice-harmdelay-cmsblogs/#post-2659551)
 * Thank you Esmi.

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

The topic ‘Debug (!)Notice harm/delay cms/blogs ?’ is closed to new replies.

## Tags

 * [notice](https://wordpress.org/support/topic-tag/notice/)
 * [script](https://wordpress.org/support/topic-tag/script/)

 * In: [Everything else WordPress](https://wordpress.org/support/forum/miscellaneous/)
 * 4 replies
 * 2 participants
 * Last reply from: [another-webmaster](https://wordpress.org/support/users/another-webmaster/)
 * Last activity: [14 years, 2 months ago](https://wordpress.org/support/topic/debug-notice-harmdelay-cmsblogs/#post-2659551)
 * Status: resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics
