Title: DEBUG: cURL response
Last modified: December 21, 2018

---

# DEBUG: cURL response

 *  Resolved [Amibe Websites](https://wordpress.org/support/users/amibe/)
 * (@amibe)
 * [7 years, 4 months ago](https://wordpress.org/support/topic/debug-curl-response/)
 * Hi, is there a way to turn off debugging messages?
 * I write errors to a log file but don’t necessarily want debugging information
   there unless I’m explicitly wanting to debug something.
 * Thanks.

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

 *  Plugin Contributor [Dimitris – WPMU DEV Support](https://wordpress.org/support/users/wpmudev-support6/)
 * (@wpmudev-support6)
 * [7 years, 4 months ago](https://wordpress.org/support/topic/debug-curl-response/#post-11027748)
 * Hello there [@amibe](https://wordpress.org/support/users/amibe/),
 * hope you’re doing good today! 🙂
 * There isn’t any specific debugger with Appointments plugin, you should be able
   to log only in file by using the following snippet just above the _/* That’s 
   all, stop editing! Happy blogging. */_ comment in **wp-config.php** file:
 *     ```
       // Enable WP_DEBUG mode
       define('WP_DEBUG', true);
       // Enable Debug logging to the /wp-content/debug.log file
       define('WP_DEBUG_LOG', true);
       @ini_set( 'log_errors', 1 );
       // Disable display of errors and warnings
       define('WP_DEBUG_DISPLAY', false);
       @ini_set('display_errors', 0);
       ```
   
 * Let me know how that goes!
    Warm regards, Dimitris
 *  Plugin Contributor [Dimitris – WPMU DEV Support](https://wordpress.org/support/users/wpmudev-support6/)
 * (@wpmudev-support6)
 * [7 years, 4 months ago](https://wordpress.org/support/topic/debug-curl-response/#post-11051429)
 * Hello there [@amibe](https://wordpress.org/support/users/amibe/),
 * we haven’t heard back from you for a while, so I’m marking this topic as resolved.
   Feel free to post back here any update and we can re-open it and carry on troubleshooting.
   🙂
 * Take care,
    Dimitris
 *  Thread Starter [Amibe Websites](https://wordpress.org/support/users/amibe/)
 * (@amibe)
 * [7 years, 4 months ago](https://wordpress.org/support/topic/debug-curl-response/#post-11051628)
 * Hi Dimitris, it’s not really resolved for me but I understand what you are saying.
 * The settings you gave are the settings I use as I constantly review the log files
   for PHP errors and warnings across the whole installation so I can address them.
 * But I don’t always want debugging information in there – especially when its 
   large outputs such as are generated by Appointments. Only if there’s a problem
   and I need to debug something specific.
 * Perhaps this is a bigger issue with WordPress? How to distinguish between PHP
   errors and debugging output?
 * What I could imagine (perhaps it is too much work?) is a hook (or setting) for
   Appointments where I can add some code in my functions.php that would disable
   debug output for Appointments. This is how it is done in some other plugins I
   make use of.
 * Thank you.

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

The topic ‘DEBUG: cURL response’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/appointments_eaf36c.svg)
 * [Appointments](https://wordpress.org/plugins/appointments/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/appointments/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/appointments/)
 * [Active Topics](https://wordpress.org/support/plugin/appointments/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/appointments/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/appointments/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [Amibe Websites](https://wordpress.org/support/users/amibe/)
 * Last activity: [7 years, 4 months ago](https://wordpress.org/support/topic/debug-curl-response/#post-11051628)
 * Status: resolved