Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter astroben85

    (@astroben85)

    Ok so Ive fixed my problem by following this:

    http://wordpress.stackexchange.com/questions/128864/getting-a-warning-call-user-func-array-error-whenever-i-install-update-a-pl

    When using the starkers theme I noticed the author had commented out a core line and replaced it with something else. This ammendment was causing issues when migrating my custom theme from MAMP to a different environment. Reverting it back to the core code has solved my issue yet im unsure of future side effects.

    Thread Starter astroben85

    (@astroben85)

    So I built a custom theme locally on MAMP, everything worked fine. I migrated the theme to WP using Starkers blank theme as the parent. Was getting a warnig related to enqueueing scripts as I had changed the function name. Reverting the function name back to the starkers standard fixed that warning but then revealed this new warning in the dashboard (not on the top of my website). I should mention the website works well with all style sheets and scripts working as they should. This warning messege is only showing in the dashboard.

    How do I post a screen shot?

    Thread Starter astroben85

    (@astroben85)

    Tried all these things to no avail. Ive tried registering my scripts and styles hoping this would fill in the missing arguement as per the warning messege so now my funcions.php looks like this:

    /**
        * Enqueue scripts and styles.
        */
        function script_enqueuer() {
            wp_register_style( 'bootstrap', 'http://netdna.bootstrapcdn.com/bootstrap/3.3.4/css/bootstrap.min.css' );
            wp_enqueue_style( 'bootstrap' );
    
            wp_register_style( 'fopp-style', get_template_directory_uri() . '/css/stylesheet.css' );
    	    wp_enqueue_style( 'fopp-style' );
    
            wp_register_script( 'fopp-jquery', get_template_directory_uri() . '/js/jquery.js', array(), '', true );
        	wp_enqueue_script( 'fopp-jquery' );
    
            wp_register_script( 'jquery-easing', get_template_directory_uri() . '/js/jquery.easing.min.js', array(), '', true );
        	wp_enqueue_script( 'jquery-easing' );
    
        	wp_register_script( 'jquery-scroll', get_template_directory_uri() . '/js/scrolling-nav.js', array(), '', true );
        	wp_enqueue_script( 'jquery-scroll' );
    
            wp_register_script( 'jquery', 'https://ajax.googleapis.com/ajax/libs/jquery/2.1.3/jquery.min.js', array('jquery'), '1.9.1', true);
            wp_enqueue_script( 'jquery' );
    
            wp_register_script( 'bootstrap-js', 'http://netdna.bootstrapcdn.com/bootstrap/3.3.4/js/bootstrap.min.js', array('jquery'), '', true);
            wp_enqueue_script( 'bootstrap-js' );
    
            /* Custom JS */
            wp_register_script( 'fopp-custom', get_template_directory_uri() . '/js/custom.js', array(), '', true );
            wp_enqueue_script( 'fopp-custom' );
    
        	if ( is_singular() && comments_open() && get_option( 'thread_comments' ) ) {
    		    wp_enqueue_script( 'comment-reply' );
    	    }
        }
        add_action( 'wp_enqueue_scripts', 'script_enqueuer' );

    Still the warning just sits there…. So strange.

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