WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] Odd "Warning: explode()" message from functions.wp-scripts.php (4 posts)

  1. alturnwall
    Member
    Posted 1 year ago #

    Hi all,

    I'm getting this message on top of all of the pages on my testing site even though wp_debug is turned off:

    Warning: explode() expects parameter 2 to be string, array given in /webserver/scenicbyways/www/test/wp-includes/functions.wp-scripts.php on line 135

    This is a duplicate issue to this thread, but I'm adding here since it's not "requests and feedback."

    As suggested by Ipsentu, I manually re-installed wordpress core files from a clean download to no avail. I also disabled all plugins with no luck.

    The site isn't "public" yet, but here's a link to the test:
    http://www.bywayswestmass.com/test/

    Can anyone point me in the right direction?

  2. alturnwall
    Member
    Posted 1 year ago #

    I should also note that this message is not appearing on my local version, and not on a test installation on another server, leading me to believe this may have something to do with the server config.

    But, I'm not sure where to start debugging that. Any general thoughts on where to start?

  3. esmi
    Forum Moderator
    Posted 1 year ago #

    Try re-uploading all files & folders - except the wp-content folder - from a fresh download of WordPress again. This time, make sure that you delete the old copies of files & folder before uploading the new ones.

    And do please indicate which version of WordPress you are using when opening a new topic. I've edited this topic to indicate your WP version based on your response in the previous thread.

  4. alturnwall
    Member
    Posted 1 year ago #

    Emsi, sorry about that. Yes, I'm on 3.5.1. That's what I tried previously, but I just tried again for good measure. Same problem.

    I then installed the stock Twenty Twelve theme and activated it and don't get the error message there, so guessed this has something to do with my theme, which is a customization of the underscores starter theme.

    Did some more digging and found this line in my functions.php:

    wp_enqueue_script( array( 'jquery' ), '20120206', true );

    That was an incorrect usage of wp_enqueue_script that I forgot to comment out. I guess the issue didn't pop up for a few days because the rest of the site had been cached. For reference, this is the correct way to include the WordPress-bundled jQuery:

    wp_enqueue_script('jquery');

    Still interested to know why the warning only popped up on this particular server and not on localhost or another test server though.

Topic Closed

This topic has been closed to new replies.

About this Topic