Incompatible Plug-ins: how to keep functionality from both?

  • katianjchs

    (@katianjchs)


    5 years ago

    Hello there,

    At the start of the week, I updated a few plug-ins on my WordPress site, including the following two:

    1. Gravity Forms Version 2.5 (Easily create web forms and manage form entries within the WordPress admin.)
    2. WordPress Meta Data & Taxonomies Filter (MDTF) Version 2.2.4 (Powerful and Flexible Filter Tools. Let your clients find all things they are want with the ease on your site.)

    When activated, MDTF prevents me from accessing the Forms dashboard in my admin account such that I cannot view entries or make any changes to the forms and their settings (The forms are still available on the website for visitors.) This is the message that I receive when trying to access my Forms dashboard: There has been a critical error on this website. Please check your site admin email inbox for instructions.

    When I deactivate the MDTF plug-in, I am able to access the Forms dashboard.

    However, deactivating the MDTF plug-in leads to an error at the following records collection: https://www.njchs.org/records/.

    (Note: at the moment, the plug-in is activated as my team needs access to this collection. When deactivated, this is the message that appears: [mdf_results_by_ajax shortcode=”mdf_custom template=any/my_posts post_type=oral_history_records orderby=title order=asc page=1 per_page=12″ pagination=b])

    Additionally, whether MDTF is activated or deactivated, when searching for and selecting an individual record through the search feature, I am redirected to an error page (e.g. https://www.njchs.org/oral_history_records/schroeder-mary-murphy/)

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

    (@eulerarthur)

    5 years ago

    Hey there,

    Have you already tried to enable debug mode? Check these links to read more about debugging with WordPress:

    https://codex.ww.wp.xz.cn/Debugging_in_WordPress
    https://codex.ww.wp.xz.cn/Debugging_in_WordPress#Example_wp-config.php_for_Debugging

    Thread Starter katianjchs

    (@katianjchs)

    5 years ago

    Hi @eulerarthur,

    Thank you for your prompt reply!
    I have not, and I am not familiar with it at all.

    Both links you kindly provided redirect me to the following link: https://ww.wp.xz.cn/support/article/debugging-in-wordpress/

    Would there be step by step instructions I could follow to enable debug mode?

    Thanks so much!

    oiler

    (@eulerarthur)

    5 years ago

    Hi @katianjchs,

    Sure! When we enable debug mode, it can show us more detailed information about the errors on WordPress. So, what you have to do is add the following code in your wp-config.php file:

    // Enable WP_DEBUG mode
define( 'WP_DEBUG', true );

// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );

// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

// Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
define( 'SCRIPT_DEBUG', true );

    Copy and paste it before this line:

    
/* That's all, stop editing! Happy publishing. */

    I recommend that you backup your site and database before (always a good practice). Also, if you find it difficult to locate/edit the wp-config file, you can read this article: https://www.wpbeginner.com/beginners-guide/how-to-edit-wp-config-php-file-in-wordpress

    Moreover, when you add the code above, reproduce the issues again and verify for a “debug.log” file inside the wp-content folder. If you locate it there, send the last lines here in the ticket, so that we can check it more thoroughly.

    Let me know. Regards,
    Euler.

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

The topic ‘Incompatible Plug-ins: how to keep functionality from both?’ is closed to new replies.