Plugin conflicts and troubleshooting in Wordpress - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to deactivate a plugin in WordPress.

Wordpress

deactivate_plugins('[1]');

Drag options to blanks, or click blank then click option'

Aplugin-slug/plugin-file.php

Bwp-config.php

Cfunctions.php

Dindex.php

Attempts:

3 left

💡 Hint

Common Mistakes

Using theme files like functions.php instead of plugin file path.

Using configuration files like wp-config.php.

To deactivate a plugin, you need to specify its main plugin file path relative to the plugins folder.

2fill in blank

medium

Complete the code to check if a plugin is active.

Wordpress

if (is_plugin_active('[1]')) {
  // Plugin is active
}

Drag options to blanks, or click blank then click option'

Awp-settings.php

Bakismet/akismet.php

Cstyle.css

Dindex.php

Attempts:

3 left

💡 Hint

Common Mistakes

Using theme files or WordPress core files instead of plugin file path.

Using only the plugin folder name without the main file.

The is_plugin_active function requires the plugin's main file path relative to the plugins folder.

3fill in blank

hard

Fix the error in the code to properly deactivate all plugins.

Wordpress

foreach ($plugins as $plugin) {
  [1]($plugin);
}

Drag options to blanks, or click blank then click option'

Aactivate_plugins

Bdelete_plugins

Cinstall_plugins

Ddeactivate_plugins

Attempts:

3 left

💡 Hint

Common Mistakes

Using activate_plugins instead of deactivate_plugins.

Trying to delete plugins instead of deactivating.

The function deactivate_plugins is used to deactivate plugins, not activate or delete them.

4fill in blank

hard

Fill both blanks to create a list of active plugins and check if a specific plugin is active.

Wordpress

$active_plugins = [1]('active_plugins');
if (in_array('[2]', $active_plugins)) {
  // Plugin is active
}

Drag options to blanks, or click blank then click option'

Aget_option

Bget_plugins

Cakismet/akismet.php

Dhello-dolly/hello.php

Attempts:

3 left

💡 Hint

Common Mistakes

Using get_plugins() which returns all plugins, not active ones.

Using wrong plugin file names.

get_option('active_plugins') returns the list of active plugins. Then in_array checks if a plugin is active.

5fill in blank

hard

Fill all three blanks to properly log plugin conflicts by hooking into WordPress.

Wordpress

add_action('[1]', function() {
  $conflicts = get_option('[2]');
  error_log('Plugin conflicts: ' . [3]);
});

Drag options to blanks, or click blank then click option'

Aadmin_init

Bplugin_conflicts

Cprint_r($conflicts, true)

Dwp_loaded

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong hook names like wp_loaded which runs too early.

Logging array directly without converting to string.

Hook into admin_init to run code in admin area. Use get_option('plugin_conflicts') to get conflicts. Use print_r with true to convert array to string for logging.

Practice

1. What is the most common cause of plugin conflicts in WordPress?

easy

A. Two plugins trying to use the same function or resource

B. Using too many plugins at once

C. Installing plugins from different developers

D. Not updating WordPress core

Solution

1. Step 1: Understand plugin conflict basics

   Plugin conflicts usually happen when two plugins try to use the same function, resource, or hook, causing interference.

2. Step 2: Analyze options

   Using many plugins or different developers does not always cause conflicts. Not updating core can cause issues but not specifically plugin conflicts.

3. Final Answer:

   Two plugins trying to use the same function or resource -> Option A

4. Quick Check:

   Plugin conflicts = same function/resource [OK]

Hint: Conflicts happen when plugins share functions or resources [OK]

Common Mistakes:

• Thinking too many plugins always cause conflicts
• Assuming different developers cause conflicts
• Believing WordPress core updates cause plugin conflicts

2. Which of the following is the correct way to deactivate a plugin in WordPress via code?

easy

A. wp_deactivate_plugin('plugin-folder/plugin-file.php');

B. plugin_deactivate('plugin-folder/plugin-file.php');

C. wp_plugin_deactivate('plugin-folder/plugin-file.php');

D. deactivate_plugins('plugin-folder/plugin-file.php');

Solution

1. Step 1: Recall WordPress plugin functions

   The correct function to deactivate a plugin programmatically is deactivate_plugins().

2. Step 2: Check function names

   Functions starting with wp_ like wp_deactivate_plugin() do not exist. The correct function is deactivate_plugins().

3. Final Answer:

   deactivate_plugins('plugin-folder/plugin-file.php'); -> Option D

4. Quick Check:

   Deactivate plugin function = deactivate_plugins() [OK]

Hint: Use deactivate_plugins() to disable plugins by code [OK]

Common Mistakes:

• Adding wp_ prefix incorrectly
• Using non-existent function names
• Confusing activation and deactivation functions

3. Given this code snippet in a WordPress plugin:

add_action('init', function() {
  if (function_exists('some_plugin_function')) {
    some_plugin_function();
  } else {
    error_log('Function missing');
  }
});

What will happen if some_plugin_function is removed by another plugin?

medium

A. An error will be logged saying 'Function missing'

B. WordPress will crash with a fatal error

C. The function will run normally without errors

D. The plugin will deactivate automatically

Solution

1. Step 1: Understand the code logic

   The code checks if some_plugin_function exists before calling it. If it does not exist, it logs 'Function missing'.

2. Step 2: Analyze the effect of removal

   If another plugin removes or disables some_plugin_function, the condition fails and error_log is called.

3. Final Answer:

   An error will be logged saying 'Function missing' -> Option A

4. Quick Check:

   Missing function triggers error_log [OK]

Hint: Check function_exists before calling to avoid fatal errors [OK]

Common Mistakes:

• Assuming WordPress crashes without check
• Thinking function runs even if missing
• Believing plugin auto-deactivates on error

4. You deactivate a plugin to fix a conflict but the site still shows errors. What is the best next step to troubleshoot?

medium

A. Reinstall WordPress core files immediately

B. Clear the site cache and browser cache

C. Delete all plugins and reinstall them

D. Ignore errors and continue working

Solution

1. Step 1: Understand caching effects

   Sometimes errors persist because cached files still serve old code or data.

2. Step 2: Clear caches to refresh site state

   Clearing both site cache (like plugin or server cache) and browser cache ensures fresh content loads.

3. Final Answer:

   Clear the site cache and browser cache -> Option B

4. Quick Check:

   Clearing cache fixes stale error display [OK]

Hint: Clear caches after changes to see updated site state [OK]

Common Mistakes:

• Reinstalling core too soon
• Deleting all plugins unnecessarily
• Ignoring errors hoping they go away

5. You suspect two plugins conflict because they both enqueue the same JavaScript file. How should you safely resolve this conflict?

hard

A. Edit both plugins to rename the script file

B. Delete the JavaScript file from the server manually

C. Use wp_dequeue_script to remove the script from one plugin and keep the other

D. Deactivate both plugins and find alternatives

Solution

1. Step 1: Identify script conflict cause

   Both plugins loading the same script can cause duplicate loading and errors.

2. Step 2: Use wp_dequeue_script to fix conflict

   WordPress allows removing a script from one plugin using wp_dequeue_script safely without deleting files or editing plugins.

3. Final Answer:

   Use wp_dequeue_script to remove the script from one plugin and keep the other -> Option C

4. Quick Check:

   wp_dequeue_script resolves script conflicts safely [OK]

Hint: Remove duplicate scripts with wp_dequeue_script [OK]

Common Mistakes:

• Deleting files manually causing errors
• Editing plugin files risking updates loss
• Deactivating both plugins unnecessarily