Forum has been created to help all our customers in properly working our theme. We offer complete help with configuration theme and make default look, just like on our Tisson demo. We don`t offer theme customization.

Before creating a new discussion, please:
1. Check on forum if discussion hasn`t been created before. Use the forum Search on the right.
2. Read carefully the documentation included to package.
If you didn`t find what you need and would like to post a new question click the "Start a New Discussion" button on the right.
4. You can post on forum only after registration (you need purchase code to register) .

NOTE!!! If you are starting a new topic and have got problems with your site and you want us to check what`s wrong please always give url to your site because without that we can`t check what`s wrong. Each case may be different because of your installed plugins, servers or other things.

PHP Fatal error: Cannot redeclare mfn_sortable() / Conflict with plugin
  • Hi
    I use Tisson 1.3.1 and it work fine except when i activate the extension "FirstFlipBook"

    In this case :
    - All pages partially lose their css 
    - In the browser inspector, this error is displayed
    Failed to load resource: the server responded with a status of 500 (Internal Server Error)
    - In the Apache logs :
    PHP Fatal error: Cannot redeclare mfn_sortable() (previously declared in /srv/srv01/www/wordpress/wp-content/themes/tisson/functions.php:35) in /srv/srv01/www/wordpress/wp-content/themes/tisson/functions.php on line 36, referer:

    I have searched in .php files, the possible origin of this conflict :
    Tisson theme /functions.php
    function mfn_sortable() {
    wp_enqueue_script( 'jquery-ui-sortable' );
    add_action( 'wp_enqueue_scripts', 'mfn_sortable' );
    add_action( 'admin_enqueue_scripts', 'mfn_sortable' );

    and in FirstFlipBook plugin / firstflipbook.php
    add_action( 'wp_enqueue_scripts', array($this, 'enqueue_script') );
    add_action( 'admin_enqueue_scripts', array($this, 'enqueue_admin_script') );

    I have read other cases with the same error on this forum.
    It is obvious that the origin here is a conflict between this theme and this extension.
    Solve this problem solves perhaps other.

    And with this message, I am not saying that the theme is responsible for the error. The extension editor have received the same message...
    I look forward to your reply


    Francis LEBOURQ

  • 1 Comment sorted by