WordPress.org

Support

Support » Plugins and Hacks » [Resolved] Conflict with Types and Views front-end filters

[Resolved] Conflict with Types and Views front-end filters

Viewing 6 replies - 1 through 6 (of 6 total)
  • Somehow the “if(!function_exists(‘wp_terms_checklist’))” test that Types and Views uses fails once Vimeography is enabled. How is this possible, seeing that Vimeography doesn’t seem to define it’s own ‘wp_terms_checklist’ function?

    The problem appears to be related to the

    add_action( ‘init’, array(&$this, ‘vimeography_move_folders’) );

    line in vimeography.php. When this line is commented out, “if(!function_exists(‘wp_terms_checklist’))” suddenly starts returning “true”.

    Digging a little deeper, the problem appears to be related to the “$this->_move_folder” function calls on lines 135 and 136 of vimeography.php in the vimeography_move_folders() function.

    OK! The problem appears to be that the

    require_once(ABSPATH . ‘wp-admin/includes/upgrade.php’)

    command on line 481 of vimeography.php causes the

    if(!function_exists(‘wp_terms_checklist’))

    command in Types and Views to return false instead of true.

    Why does the “wp-admin/includes/upgrade.php” file need to be required on every page load?

    This seems rather inefficient to me and prone to cause problems like the one created with Types and Views.

    Plugin Author Dave Kiss

    @iamdavekiss

    Thanks for the detailed report. I’ll update this in the next release!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘[Resolved] Conflict with Types and Views front-end filters’ is closed to new replies.