Cannot modify header information

Support has been upgraded!



The Support Forum is closed. Not to worry!  Providing the top quality support you expect and we're known for will continue! We're not ending support, just changing where you submit requests. This will provide you with the best experience possible.

Premium Support

Have you purchased an addon for Connections such as one of our premium templates or extensions with a valid license and you need help?

Please open a Support Ticket in your user account.

Click here to open a support ticket.

Free Support

Are you using the free Connections plugin? Don't worry, you are still very important to us! We are still providing you with the same high quality support that we're known for.

Please open a new support topic in the WordPress support forums for Connections.

Click here to open a support topic.

This topic is: resolved

Tagged: , , , , , ,

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • 10/25/2014 at 9:53 am #308089
    Bob Oliver
    Participant

    can anyone id this error. i get it every time i try to add and entry in connections… or is this a WP thing?

    Notice: like_escape is deprecated since version 4.0! Use wpdb::esc_like() instead. in /home/wytheren/public_html/mycbcsurry.com/wp-includes/functions.php on line 3201

    Notice: like_escape is deprecated since version 4.0! Use wpdb::esc_like() instead. in /home/wytheren/public_html/mycbcsurry.com/wp-includes/functions.php on line 3201

    Warning: Cannot modify header information – headers already sent by (output started at /home/wytheren/public_html/mycbcsurry.com/wp-includes/functions.php:3201) in /home/wytheren/public_html/mycbcsurry.com/wp-includes/pluggable.php on line 1173

    10/25/2014 at 10:30 am #308090
    Steven Zahm
    Keymaster

    @ Bob

    Seems you or web host has the server setup to show PHP notices. This is not a good practice for production servers. Errors and notices should be logged to a file outside of the public_html directory so it is not publically browsable.

    In this instance it is showing a harmless notice for devs so they know a function has been deprecated so they can plan on removing its use at a later date.

    This WordPress doc page explains more about PHP warning and notices:
    http://codex.wordpress.org/Debugging_in_WordPress#PHP_Errors.2C_Warnings_and_Notices

    What you need to do is add the following to the wp-config.php file:

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

    That should fix it up.

    10/25/2014 at 10:41 am #308091
    Bob Oliver
    Participant

    Ok. Thanks. As long it is harmless to the operation of connections or other plugins. I set to ‘true’ during a debug after a crash and will correct.
    Thanks again.

    10/25/2014 at 11:18 am #308094
    Steven Zahm
    Keymaster

    @ Bob

    Yes, it is harmless. It is simply a notice for devs. The warning is only being shown because the notices are being shown.

  • Author
    Posts
Viewing 4 posts - 1 through 4 (of 4 total)

You cannot reply to this support topic. Please open your own support topic.