Custom Field Template seriously messed up in WP 3.1.1

1 Views

I’m having a serious problem with the plugin Custom Field Template in which applying a CFT based on the template name is not working (it’s as if the Ajax used to load the template is breaking). I’ve tried getting help in the forums but no response – seems to be browser independent (tried it in FF4, Safari 5 and Chrome).

I need to find out why this is happening and I’m running out of time as my client needs to go live with this site by the end of the week they say.

Read More

http://www.youtube.com/watch?v=RIfDToXm5IU

Can someone take a look at the video above and let me know what I could do to try and solve the issue? It’s a great plugin, but this kind of issue reaffirms why it’s always best to not use plugins if possible 🙁

Any help massively appreciated,

Osu

Post Views: 1

Related posts

Leave a Reply

3 comments

  1. This Plugin is loading quite a lot of scripts:

    wp_enqueue_script( 'jquery' );
wp_enqueue_script( 'jquery-form' );
wp_enqueue_script( 'date', '/' . PLUGINDIR . '/' . $plugin_dir . '/js/date.js', array('jquery') );
wp_enqueue_script( 'bgiframe', '/' . PLUGINDIR . '/' . $plugin_dir . '/js/jquery.bgiframe.js', array('jquery') ) ;
wp_enqueue_script( 'datePicker', '/' . PLUGINDIR . '/' . $plugin_dir . '/js/jquery.datePicker.js', array('jquery') );
wp_enqueue_script( 'textarearesizer', '/' . PLUGINDIR . '/' . $plugin_dir . '/js/jquery.textarearesizer.js', array('jquery') );
if( strstr($_SERVER['REQUEST_URI'], 'wp-admin/post-new.php') || strstr($_SERVER['REQUEST_URI'], 'wp-admin/post.php') || strstr($_SERVER['REQUEST_URI'], 'wp-admin/page-new.php') || strstr($_SERVER['REQUEST_URI'], 'wp-admin/page.php') || $post->post_type=='page' ) :
    wp_enqueue_script( 'editor' );
endif;

    It’s possible that there’s a conflict.

    Are you sure the issue began with WordPress 3.1.1, rather than with 3.1? The jQuery version in 3.1 was bumped up; I’m unaware of any script version changes in 3.1.1, but I could be wrong.

  2. I know it’s more than a year later, but it seems the conflict between Custom Field Template v2.02 and Ajax Event Calendar v1.02 continues to exist.

    The solution recommended on many blogs/forums is to delete the date.js file from the /wp-content/plugins/custom-field-template/ folder – However, this leaves “Custom Field Template” unable to use the date-picker on any fields.

    I’ve posted an alternative solution here which allows both plug-ins co-exist and function without an hindrances:

    http://wordpress.org/support/topic/solution-conflict-work-around-for-ajax-event-calendar-custom-field-template?replies=1