Title: Function wp_enqueue_style was called incorrectly.
Last modified: April 3, 2023

---

# Function wp_enqueue_style was called incorrectly.

 *  Resolved [SimpleRick](https://wordpress.org/support/users/keramikoch/)
 * (@keramikoch)
 * [3 years, 2 months ago](https://wordpress.org/support/topic/function-wp_enqueue_style-was-called-incorrectly/)
 * Hi dear support, 
   thank you for your usefull plug-in. But I get the following
   error since installing your plugin.
 * PHP Notice
 * | Apr 3, 2023, 12:12:58
 * 
   Function wp_enqueue_style was called **incorrectly**. Scripts and styles should
   not be registered or enqueued until the `wp_enqueue_scripts`, `admin_enqueue_scripts`,
   or `login_enqueue_scripts` hooks. This notice was triggered by the `woocommerce_de_admin`
   handle. Please see [Debugging in WordPress](https://wordpress.org/support/article/debugging-in-wordpress/)
   for more information. (This message was added in version 3.3.0.)Function wp_enqueue_style
   was called **incorrectly**. Scripts and styles should not be registered or enqueued
   until the `wp_enqueue_scripts`, `admin_enqueue_scripts`, or `login_enqueue_scripts`
   hooks. This notice was triggered by the `woocommerce_de_admin` handle. Please
   see [Debugging in WordPress](https://wordpress.org/support/article/debugging-in-wordpress/)
   for more information. (This message was added in version 3.3.0.)I know it is “
   only” a “notice” but it appears over 300 times in the last weeks.Could you help?
 * Thanks in advance.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ffunction-wp_enqueue_style-was-called-incorrectly%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

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

 *  Plugin Author [Optimocha](https://wordpress.org/support/users/optimocha/)
 * (@optimocha)
 * [3 years, 2 months ago](https://wordpress.org/support/topic/function-wp_enqueue_style-was-called-incorrectly/#post-16620994)
 * Hi [@keramikoch](https://wordpress.org/support/users/keramikoch/),
 * We don’t have a handle named woocommerce_de_admin, are you sure Disable Cart 
   Fragments is responsible for this notice? Can you try clearing your error log/
   debug log, then deactivate our plugin, then wait a few days to see if the notice
   still comes up?
 *  Thread Starter [SimpleRick](https://wordpress.org/support/users/keramikoch/)
 * (@keramikoch)
 * [3 years, 2 months ago](https://wordpress.org/support/topic/function-wp_enqueue_style-was-called-incorrectly/#post-16621043)
 * [@optimocha](https://wordpress.org/support/users/optimocha/)
 * Thanks for the fast response 🙂 No, I am not sure – just the time the error occured
   and installing the plug-in was the same. I will try what you proposed. Thanks.
 *  Plugin Author [Optimocha](https://wordpress.org/support/users/optimocha/)
 * (@optimocha)
 * [3 years, 2 months ago](https://wordpress.org/support/topic/function-wp_enqueue_style-was-called-incorrectly/#post-16622966)
 * [@keramikoch](https://wordpress.org/support/users/keramikoch/) great! Let me 
   know if you need me for anything else.

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

The topic ‘Function wp_enqueue_style was called incorrectly.’ is closed to new replies.

 * ![](https://ps.w.org/disable-cart-fragments/assets/icon-256x256.png?rev=2098872)
 * [Disable Cart Fragments by Optimocha](https://wordpress.org/plugins/disable-cart-fragments/)
 * [Support Threads](https://wordpress.org/support/plugin/disable-cart-fragments/)
 * [Active Topics](https://wordpress.org/support/plugin/disable-cart-fragments/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/disable-cart-fragments/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/disable-cart-fragments/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [Optimocha](https://wordpress.org/support/users/optimocha/)
 * Last activity: [3 years, 2 months ago](https://wordpress.org/support/topic/function-wp_enqueue_style-was-called-incorrectly/#post-16622966)
 * Status: resolved