Get the Best WordPress Backup
& Migration Plugin Today
Get Duplicator Now

Duplicator Documentation

Documentation, Reference Materials, and Tutorials for Duplicator

How to handle popular plugin conflicts?

Overview

Plugins can cause issues with processes that access file system or modify web server configurations. Below is a list of common issues with other popular WordPressplugins andwork-arounds. Many companies work together to solve cross plugin issues. These issues can be easily resolved by having the most recent version of the plugin and WordPress.


Common Fixes

Solution 1Update the plugin, Duplicator, theme and WordPress to the latest versions. Also deactivate and reactivate the plugin, Duplicator and the theme.

Solution 2If the plugin/theme is a commercial product and requires a valid license key contact the plugin/theme authors to see if it can work on other domains. It might be as easy as extending thelicense to the new site you are migrating to.

Elementor

ProblemAfter an install you notice that your Elementor Pages/Posts are not working/looking correct.

Solution 1If corruption is observed go to Elementor > Tools > General and click “Regenerate Files” for the “Regenerate CSS” option

Ninja Firewall

ProblemYou are using NinjaFirewall and running into issues durning the install.

Solution 1Consider the steps in this wordpress.org thread.

Oxygen Builder

ProblemThe Oxygen Builder formatting on some pages is not working properly or is lost.

Solution 1After migrating a site you have to re-sign the oxygen shortcodes. To do this follow these steps:

  1. Goto: Oxygen > Settings > Security
  2. Check “Check Oxygen’s shortcodes for a valid signature before executing” option and save
  3. Click on the link “Sign All Shortcodes”, check and Save
  4. Next check the checkbox “I have made a complete backup of my site” & click button to save shortcodes.

WordFence

ProblemAn error shows as Fatal error: Unknown: Failed opening required ‘/some_path/wordfence-waf.php’ (include_path=’… in Unknown …

Solution 1Check your .htaccess and remove the following or anything with # Wordfence WAF:php_value auto_prepend_file "/path_to_file/wordfence-waf.php" Check your php.ini or user.ini and remove the following:auto_prepend_file = '/home/username/website.com/wordfence-waf.php
Solution 2Contact WordFence or Online Resources

Also See:
How to resolve 403/500/timeout issues on step 3?

Was this article helpful?

Related Articles