WordPress Plugin Support FAQ

Before You Open a Support Ticket: A Simple Checklist

When a plugin stops working, it can feel frustrating. The good news is that most plugin problems have simple causes you can fix yourself. This FAQ will walk you through the most common checks. Doing these first will save you time and help you get better support if you still need it.

First Steps to Try Right Away

Have you cleared your cache?

Cached files can make it look like a plugin is broken when it is actually working fine. Clear these three things:

1. Your browser cache. Press Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac. This forces your browser to load fresh files.
2. Your WordPress cache plugin. If you use a caching plugin like WP Rocket or LiteSpeed Cache, click the “Purge All” or “Clear Cache” button.
3. Your CDN cache. If you use a service like Cloudflare, log in there and clear the cache too.

After clearing all caches, check if your issue is resolved. Sometimes that is all it takes.

Have you tried a different browser or device?

Sometimes the problem is only on your computer or phone. Try opening your site in a different browser (like Chrome instead of Firefox) or on a different device. If the plugin works fine elsewhere, the issue is likely with your browser settings, not the plugin itself.

The Most Common Cause: Plugin Conflicts

Why do plugins conflict with each other?

WordPress plugins are made by thousands of different developers. Sometimes two plugins try to do the same thing at the same time, or one plugin’s code does not play nicely with another plugin’s code. When this happens, things break.

How do I check for a plugin conflict?

This is the single most useful troubleshooting step you can take. Here is how to do it safely:

1. Make a backup first. Use your hosting provider’s backup tool or a backup plugin. This way, if anything goes wrong, you can restore your site.
2. Deactivate all plugins. Go to your WordPress dashboard, click “Plugins,” check the box at the top to select all, choose “Deactivate” from the dropdown, and click Apply.
3. Check if the problem is gone. Visit your site and see if the issue still happens. If the problem disappears, you know a plugin was causing it.
4. Reactivate plugins one by one. Turn plugins back on one at a time. After each one, check your site. When the problem comes back, you have found the plugin causing the conflict.

Important tip: Activate your security and caching plugins last. They often interact with many other parts of your site.

What if deactivating all plugins does not fix it?

If the problem remains even with all plugins off, the issue is probably not a plugin conflict. It could be your theme, your PHP version, or something with your hosting server. Keep reading for more checks.

Theme Conflicts

How do I know if my theme is the problem?

Your theme and a plugin might not work well together. To test this:

1. Go to “Appearance” and then “Themes” in your dashboard.
2. Temporarily activate a default WordPress theme like Twenty Twenty-Four.
3. Check if the plugin issue is resolved.

If the plugin works with the default theme, your original theme is causing the conflict. Contact the theme developer for help, or consider switching themes.

Version and Compatibility Issues

Are WordPress, your plugins, and your theme all up to date?

Outdated software is one of the most common reasons plugins break. Plugin developers release updates to fix bugs and work with new versions of WordPress.

Go to your WordPress dashboard and check the “Updates” page. Install any available updates for WordPress itself, your plugins, and your theme.

Warning: Before updating, make a backup. And avoid updating everything at once. Update a few plugins at a time and check your site after each batch. If something breaks, you will know which update caused it.

Does your plugin work with your version of PHP?

PHP is the programming language WordPress runs on. If your hosting server uses an old version of PHP, newer plugins may not work.

WordPress recommends PHP 7.4 or higher. For best results and security, PHP 8.1 or 8.2 is better. Check your PHP version in your hosting control panel. Most hosts let you change it with one click.

Does your plugin require a newer WordPress version?

Some plugins need a specific minimum version of WordPress. If you are running an old version of WordPress, the plugin may not work.

Check the plugin’s description page to see what version of WordPress it requires. If needed, update WordPress first.

Common Error Symptoms and What They Mean

What is the “White Screen of Death”?

If your site shows a completely blank white page, this is called the White Screen of Death. It usually means a plugin or theme has caused a fatal error.

You can often fix this by renaming the plugin folder. Use your hosting file manager or FTP to go to wp-content/plugins/. Find the folder for the plugin you suspect and rename it. For example, change woocommerce to woocommerce-disabled. WordPress will automatically deactivate that plugin, and your site should come back. Then you can rename it back and delete it properly.

What if I am locked out of my WordPress admin area?

If you cannot access your dashboard at all, you can still disable plugins manually.

Use your hosting file manager or FTP to go to wp-content/plugins/. Rename the folder of the plugin you think is causing the problem. Adding “-disabled” to the end of the folder name works. WordPress will not find the plugin, so it will deactivate it automatically, and you should be able to log in again.

What if buttons do not work or sliders will not move?

This is usually a JavaScript error. JavaScript makes interactive parts of your site work. To see what is wrong, open your browser’s developer console by pressing F12 or Ctrl + Shift + I. Look for red error messages. They will often show which plugin file is causing the problem.

What if I see a “500 Internal Server Error” or a critical error message?

A 500 error is a general server error. Try these steps:

1. Go to Settings and then Permalinks. Click “Save Changes” without changing anything. This can fix some errors.
2. If that does not work, rename your entire plugins folder to plugins-old. If your site comes back, you know a plugin is causing the issue. Rename the folder back and deactivate plugins one by one to find the culprit.

When Nothing Else Works: Enabling Debug Mode

What is debug mode and how do I use it?

Debug mode makes WordPress create a log file that shows exactly what is going wrong. Here is how to turn it on:

1. Use your hosting file manager or FTP to open the file wp-config.php in your site’s main folder.
2. Find this line: define('WP_DEBUG', false);
3. Change it to true. If that line is not there, add these lines:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

4. Save the file.
5. Visit your site to trigger the error.
6. Look for a file called debug.log in the wp-content folder. Open it to see what errors occurred.

The log will often name the exact plugin or file causing the problem.

Important: Turn debug mode off when you are done. Detailed error logs on a live site can be a security risk.

Reinstalling the Plugin

Could the plugin files be corrupted?

Sometimes a plugin file gets corrupted during installation or an update. This can make the plugin behave strangely.

To fix this:

1. Deactivate the plugin (do not delete it yet).
2. Delete it.
3. Download a fresh copy from the official WordPress plugin directory or the developer’s website.
4. Install the fresh copy.

Never use “nulled” or pirated plugins. They often contain malware and are a major security risk.

Information to Include When Opening a Ticket

What should I include in my support request?

If you have tried everything above and still need help, you will get faster and better support by including:

• A clear subject line. “Plugin breaks when WooCommerce is active” is much better than “Help me!!!” or “Urgent problem”.
• Your site URL. A link is worth a thousand words.
• What you expected to happen and what actually happens. Describe the steps to reproduce the problem.
• What you have already tried. Mention the troubleshooting steps you completed, like disabling other plugins or switching themes.
• Screenshots if helpful. A picture of the error can explain things quickly.
• Your WordPress version, PHP version, and plugin version. This helps support staff understand your setup.

Where should I open a ticket?

Use the official support channel for the plugin. This is usually a support page on the developer’s website or the WordPress.org plugin support forum. Different developers have different support systems.

Quick Reference: Most Common Issues and First Fixes

A Final Note

Most plugin problems are caused by conflicts, outdated software, or caching issues. Working through the steps above will solve the majority of problems you encounter. If you do need to open a support ticket, the information you gather during these checks will help the support team help you much faster.

Remember to always make a backup before making changes to your site. It is your safety net.

Required Details for Your Support Ticket

Once you have worked through the checks above and are ready to open a support ticket, please include the following information so we can help you as quickly as possible:

• WordPress version
• PHP version
• Plugin version
• List of active plugins
• Any error logs from /wp-content/debug.log or your hosting panel

We aim to respond within 48 business hours.