Title: Plugin conflict
Last modified: September 2, 2020

---

# Plugin conflict

 *  Resolved [fiberlyone](https://wordpress.org/support/users/fiberlyone/)
 * (@fiberlyone)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/plugin-conflict-297/)
 * I have a mystery.
 * Print My Blog was working fine and then it wasn’t—on my working site. Clicking
   on either print or pdf button in Safari just returns a blank page. Chrome returns
 * > This page isn’t working
   >  [http://www.columbiariversewing.org](http://www.columbiariversewing.org)
   > is currently unable to handle this request. HTTP ERROR 500
 * After deactivating and activating plugins one at a time, I found the conflict
   to be with ProfileGrid 4.1.3. It’s repeatable.
    [https://www.columbiariversewing.org/community-service-update-july-2020/](https://www.columbiariversewing.org/community-service-update-july-2020/)
 * The mystery is that on my testing site, with the same version of ProfileGrid,
   it works just fine
    [https://columbiariversewing.org/testing/community-service-update-july-2020/](https://columbiariversewing.org/testing/community-service-update-july-2020/)

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

 *  Plugin Author [Michael Nelson](https://wordpress.org/support/users/mnelson4/)
 * (@mnelson4)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/plugin-conflict-297/#post-13352344)
 * Hmmm yes I see the blank page, probably from a PHP error. You could add these
   settings temporarily to your live site’s `wp-config.php` to help gather more 
   information on the error:
 *     ```
       define('WP_DEBUG',true); // if you already defined WP_DEBUG elsewhere, just change it there to true, same with all these other definitions
       define('WP_DEBUG_LOG',true);
       define('WP_DEBUG_DISPLAY',false);
       ```
   
 * That will log any PHP error to a file called `debug.log` in your `wp-content`
   directory.
 * I’d suggest making those changes to your `wp-config.php`, then go to Print My
   Blog’s page where you’re getting the whitescreen, and then check if `wp-content/
   debug.log` has anything in it. If it does, please share here. Either way, you
   should then undo the changes to `wp-config.php` so hackers can’t see the debug
   info.
 *  Thread Starter [fiberlyone](https://wordpress.org/support/users/fiberlyone/)
 * (@fiberlyone)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/plugin-conflict-297/#post-13361231)
 * I did make the debug changes to wp-config.php, there was no debug.log. So I added
   a blank page wp-content/debug.log, but it showed no errors.
 * I spent an hour on a chat with my service provider trying to find a specific 
   error. Since he couldn’t figure it out, he escalated the case. I have not heard
   back from them. I’ll report when the error reporting is sorted out.
    -  This reply was modified 5 years, 9 months ago by [fiberlyone](https://wordpress.org/support/users/fiberlyone/).
 *  Plugin Author [Michael Nelson](https://wordpress.org/support/users/mnelson4/)
 * (@mnelson4)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/plugin-conflict-297/#post-13363226)
 * Hmmm ya strange. The point is we want to make sure you’re able to see PHP warnings
   and errors for now, because without that it’s very hard to know what needs to
   be fixed.
    What I do in your situation: I purposefully add some PHP code that
   I know will produce a warning (eg `$foo=null; $foo[0]`) to the theme’s `functions.
   php` file and make sure I can somehow see those warnings (eg in the debug.log
   file, or at least on the webpage when `DEBUG_DISPLAY` is set to `true`. Once 
   I know that’s working, I’d visit the problematic page and look for warnings and
   errors.
 * If you never see any warnings and errors, it’s possible another plugin or your
   hosting provider is hiding them. So you’d need to try deactivating plugins and
   talking to the host until you’re able to know what warnings and errors are happening.
 * Good luck!
 *  Thread Starter [fiberlyone](https://wordpress.org/support/users/fiberlyone/)
 * (@fiberlyone)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/plugin-conflict-297/#post-13378935)
 * With the last update, the problem seems to have resolved.
 * Still no resolution on why the debug didn’t work, but that’s not your problem.
 * Thanks.
 *  Plugin Author [Michael Nelson](https://wordpress.org/support/users/mnelson4/)
 * (@mnelson4)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/plugin-conflict-297/#post-13379146)
 * Good to hear the issue was resolved. I’m not certain what the problem was or 
   what in the latest release solved it, but oh well. Please report another issue
   if you have the problem again!

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

The topic ‘Plugin conflict’ is closed to new replies.

 * ![](https://ps.w.org/print-my-blog/assets/icon-256x256.png?rev=3020803)
 * [Print My Blog - Print, PDF, & eBook Converter WordPress Plugin](https://wordpress.org/plugins/print-my-blog/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/print-my-blog/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/print-my-blog/)
 * [Active Topics](https://wordpress.org/support/plugin/print-my-blog/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/print-my-blog/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/print-my-blog/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [Michael Nelson](https://wordpress.org/support/users/mnelson4/)
 * Last activity: [5 years, 9 months ago](https://wordpress.org/support/topic/plugin-conflict-297/#post-13379146)
 * Status: resolved