How Do You Resolve A WordPress Plugin Conflict?

One of the scariest things that can occur with WordPress user is to install a additionAnd after activation you get a white screen of death.

This screen, where your beautifully made website once lived, is now ordinary white or produces a line or two unprecedented text.

The conflict of accessories is when you have two accessories installed, and while both work in line, starting them together breaks the site.

Usually it happens when supplements run in tandem and both are packaged with the same or similar bibliote functions. There is a conflict for appointment, and PHP creates a mistake.

This article will discuss how to fix them.

Conflicts with an addition becomes rare

First of all, the conflict of supplements: where someone installs an addition that claims with another addition becomes rare.

WordPress has introduced protection in the last few years, which means that if a mistake occurs, instead of fully activating the supplement, it will automatically withdraw, give an error and leave an addition to deactivated.

For most users, they see it.

At this point, the investigation should be done in an environment for setting up with this addition, but unless it is a unique addition, it may need to find an alternative that does not conflict with your setting.

Conflicts with accessories usually occur when you install an accessory for use (MU) through service like FTP, a one or more accessories are updated or you have a custom supplement and the changes are pushed to the server.

I will spend you through my process of resolving conflict of supplements.

Do you have access to WordPress?

For starters, the first question you should ask is if you have access to WordPress.

If you do, conventional wisdom dictates that the course of action to be taken is to deactivate all accessories and switch to the default topictry and solve problems where the problem is happening.

If you do it in a live place, this is not ideal, because the site still has a lot of functionality.

A different approach to install Health checks and solving problems addition. Installing this supplement would allow you to launch a website version with a given topic, not installed accessories.

Simply activate each addition in return until you identify the one that causes the problem and then leave the deactivated one.

Make sure the topic is the last thing activated because custom topics could use functionality in accessories that could overthrow the site.

If you do not have access to WordPress

If you do not have access to WordPress, then there may be a little procedure to diagnose and solve the problem.

This approach is what I consider to be the best I can when diagnosing conflict of supplements. This can be done in any order, depending on your knowledge and what you have access to.

Do you have access to the administrative e -Ap? You might get an e -a -hasty

If you have access to the administrator E -stio with WordPress (Set up in Settings> General), you may get e -hast.

This will allow you to put a place in Recovery mode. From there you can sign up and it will identify an addition that has a problem and you can deactivate it.

Check the host log file

The first step would be to check the host log file.

Depending on the host, it can be easily visible on your host or CPanel control panel, but if you only have a file browser, they will be placed outside / public_html / or / www / (which are publicly available). Usually one level is in a file called / diaries / usually located where it is.

If you find a file (you need to have a name like Error_log), download it and look for any fatal mistake within the document, perhaps toward the bottom.

Inside the error message you should have several sites of files that will dictate where the file problems occur.

No logs? You may need to activate them

If you have a FTP/SFTP access to the site, but without a diary, you may need to activate them.

Add the following lines to the WP-CONFIG.php file inside the root directory of WordPress.

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

This will create a Debug.log file inside WP-Conntent/ folders. From there you can see mistakes in this file.

Safety Tip: Debug.log will be publicly visible, so after solving the problem, remove these lines with WP-CONFIG.php and delete the Debug.logog file.

Resolving these conflicts of supplements

Whatever method you use, your records should produce lines like this one below:-

Fatal error: Cannot redeclare hello_dolly_get_lyric() (previously declared in/wp-content/plugins/broken-plugin/index.php:17) in /wp-content/plugins/hello-dolly/hello.php on line 46

Each element means:

• “Fatal Error” determines the error. Fatal error in PHP means that the site stops working immediately. You can get other mistakes or warnings.
• “I can’t redeclare hello_dolly_get_lyric ()” is a fatal mistake. In this case, there are two PHP functions with the same name (hello_dolly_get_lyric ()). This is the basis of a conflict with the addition.
• “/Wp-content/plugins/hello-dolly/hello.php on the line 46 “ tells you where this mistake is happening. Although the number of lines is not important (unless you have coded), it tells you an accessory where an error appears to this case, “Hello-Dolly”.

The next step is handmade to change the supplement.

In your selected FTP program or file manager, go to the accessory folder within WordPress-/WP-Conntent/accessories/in this case and rename the accessory folder (in this case “Hello-Dolly” to “Broken-Hell-Dolly”). This will deactivate the supplement when you sign up for WordPress next time.

It’s good not to delete WordPress supplement if you can prevent it. This will stimulate the deactivation of the supplement in question.

From there you can explore two accessories and determine why two functions are called twice.

For developers: Good practice can prevent conflicts with addition

If you are a programmer who builds a WordPress site, following good practice can prevent conflicts with accessories.

Here are some tips to prevent your supplement or WordPress that there are conflicts with other accessories outside:

1. If you do not use PHP names for names, then I would recommend the name of class or a prefix function. Something like an addition_name_function_name can prevent similar functionality has the same function name. Try to make them unique (so don’t use WP_ as a prefix).
2. Use function_exists Around your functions to prevent your functioning if they already exist.
3. If you import functionality, using Class_exists You can check that the class has already been loaded.
4. Inserting your functionality late, so the use of the folder is a late alphabetic letter. Not every developer follows the same approach as you!
5. If you build on one website, make sure the setting of your server is the same (or what is close to the same) as a live environment.

You will never fully guarantee that your addition or topic is not in conflict with millions of supplements that exist in WordPress space.

However, the following steps mentioned above, you can reduce the conflict as much as possible, and simple changes in writing codes can later prevent the world of removal of errors.

More resources:

---

Sepaled picture: Whiskerz/Shutterstock