Uncaught TypeError: $id(...).hide(...).farbtastic is not a function

[jedrzejchalubek]

Getting error form js file: Uncaught TypeError: $id(...).hide(...).farbtastic is not a function and of course all js based repeatable UI elements dont work.

Wordpress: 4.2.2
CMB: dev-trunk

[jtsternberg]

The only reason that would happen is if this condition: (typeof jQuery.wp === 'object' && typeof jQuery.wp.wpColorPicker === 'function') is false. This means the colorpicker is not enqueued or some other script is causing that script to not work. There is nothing in CMB2 that would cause this to occur.

[jedrzejchalubek]

But on version CMB2 2.0.6 this error not appears. I replacing worpdress jquery with cdn, need to test this out. Thanks.

[jtsternberg]

If you're replacing default WordPress scripts, there's not much I can do to help.

[michaeljpowell]

I get this same error when I'm on a custom options page (specifically with the file upload field). When it's within a page it appears to be working fine.

I am using the WP plugin version.

[EvanHerman]

I too was getting the same error using the version up here on GitHub and the version found in the WordPress plugin repo. Whenever I included a color picker field I was getting the same error as the OP.

This was on a fresh TwentyFifteen install with no other plugins installed/active.

Adding the following, just below colorpicker field definition, did the trick for me:

wp_enqueue_style( 'wp-color-picker' );
wp_enqueue_script( 'wp-color-picker' );

Example in the example-functions.php file:

/**
* Options fields ids only need
* to be unique within this option group.
* Prefix is not needed.
*/
$cmb_options->add_field( array(
    'name'    => __( 'Site Background Color', 'cmb2' ),
    'desc'    => __( 'field description (optional)', 'cmb2' ),
    'id'      => 'bg_color',
    'type'    => 'colorpicker',
    'default' => '#ffffff',
) );

wp_enqueue_style( 'wp-color-picker' );
wp_enqueue_script( 'wp-color-picker' );

It seems to only be the color picker field that's causing this issue.

Evan

[jtsternberg]

Thanks for reporting. The issue should be addressed in 244d39f