Scripts and styles should not be registered or enqueued

  • Resolved muyika1

    (@muyika1)


    10 years, 11 months ago

    can someone please help me out …..my multisite installation keeps showing Scripts and styles should not be registered or enqueued ….

    Notice: load_plugin_textdomain was called with an argument that is deprecated since version 2.7 with no alternative available. in /home/hypecent/public_html/wp-includes/functions.php on line 2939

    Notice: load_plugin_textdomain was called with an argument that is deprecated since version 2.7 with no alternative available. in /home/hypecent/public_html/wp-includes/functions.php on line 2939

    Notice: Use of undefined constant picon_action – assumed ‘picon_action’ in /home/hypecent/public_html/files-in/plugins/personal-favicon/personal-favicon.php on line 116

    Notice: wp_register_style 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 /home/hypecent/public_html/wp-includes/functions.php on line 2973

    Notice: Constant PLUGINDIR already defined in /home/hypecent/public_html/files-in/plugins/pricing-table/pricing-table.php on line 22

    Notice: Undefined index: HTTP_CF_CONNECTING_IP in /home/hypecent/public_html/files-in/plugins/cloudflare/cloudflare.php on line 44

    Notice: Undefined variable: _SESSION in /home/hypecent/public_html/files-in/themes/OneTouch/inc/widgets/widget-contact.php on line 7

    Warning: session_start() [function.session-start]: Cannot send session cache limiter – headers already sent (output started at /home/hypecent/public_html/wp-includes/functions.php:2939) in /home/hypecent/public_html/files-in/themes/OneTouch/inc/widgets/widget-contact.php on line 8

    i have tried to chek out forums online but i can locate the function

Viewing 7 replies - 1 through 7 (of 7 total)
  • David Sader

    (@dsader)

    10 years, 11 months ago

    Turn off plugins and themes(switch to default twentytwelve)) until all the errors go away, turn each back on one at a time to isolate the errors possible, then look for support in the appropriate plugin/theme support page (go to the plugin/theme download page and look for the Support link there).

    The plugins you have activated appear to need some tinkering from the plugin/theme creators.

    Thread Starter muyika1

    (@muyika1)

    10 years, 11 months ago

    i could not even be able to access the backend in order to deactivate the plugins and themes….the error was still displayed………..

    but i tried something that worked….am not sure if it is a temporary solution or i will keep getting the same error after sometime

    i turned on worpress debug mode and and inserted this plugin (http://wordpress.org/extend/plugins/simple-error-handler/) on my mu-plugins folder……

    when i turned off wp debug mode the error was gone……

    was this just temporary??? or its ok already

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    10 years, 11 months ago

    i could not even be able to access the backend in order to deactivate the plugins and themes….the error was still displayed………..

    In that case, you delete the plugin via FTP.

    Turning off debug mode hides the error, it does not fix it. You may still have problems.

    Thread Starter muyika1

    (@muyika1)

    10 years, 11 months ago

    where exactly is the location of the stylesheet enque script….within a wordpress multisite that can enable me locate and change…it…i tried to deactivate all plugins and reactivated….them….it works fine when i turn debug mode off….but as you say i may still have the problem….so if i can locate the script then i can probably change it

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    10 years, 11 months ago

    where exactly is the location of the stylesheet enque script

    Depends on the script/sheet being enqueued.

    David Sader

    (@dsader)

    10 years, 11 months ago

    PHP notices may in fact not be a big deal…yet. Warnings about deprecated code in a plugin or theme should be addressed by the author of the theme/plugin.

    Look first at the support forum for the plugins you listed in your errors.

    Personal Favicon, if it is the same plugin as you are using looks bad from the get go. Old support, dire warnings from other users. Don’t use it is what some have said there.
    http://wordpress.org/support/plugin/personal-favicon

    CloudFlare’s support forum appears to have threads started already listing possible solutions for the php notice you pasted above. Have a look:
    http://wordpress.org/support/plugin/cloudflare

    Pricing Table, again look through the threads there for the same kinds of warnings/notices you see (or any other red flags – wringing of hands and gnashing of teeth).
    http://wordpress.org/support/plugin/pricing-table

    Similarly with your OneTouch theme, look for a link to the support site for the theme in the theme activation description. If there is no support from your theme author consider dropping the theme and activating a theme with a more active support group.

    Thread Starter muyika1

    (@muyika1)

    10 years, 11 months ago

    thankyou for the help…….

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Scripts and styles should not be registered or enqueued’ is closed to new replies.