W3 Total Cache broke a plug in

  • Resolved alexjust

    (@alexjust)


    6 years, 6 months ago

    So yesterday I had a huge influx of traffic due to a contest I was running with contest friend (https://wordpress.org/plugins/contestfriend/) and it kept causing my website to go down. Hostgator support suggested I install a caching plugin so I installed W3 Total cache. Immediately I had this warning message come up at the top of my wordpress back end (see copy paste below). I didn’t worry too much as I figured this would fix itself as soon as I disabled the W3 Total cache plugin but I now cannot get the contestfriend plugin to work at all without this warning message coming up. The weird thing is that the pathway it’s mentioning hasn’t been active in years (ie the /home4/alexjust/public_html (this is the directory I initially set the website up in about 4 years ago)

    Does anybody have any ideas as to what’s causing this and how to fix it? Any help huuuuuuugely appreciated!

    Alex

    Warning: Declaration of cf_Table_Participants::extra_tablenav() should be compatible with WP_List_Table::extra_tablenav($which) in /home4/alexjust/public_html/wp-content/plugins/contestfriend/tables/table-participants.php on line 446

    Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /home4/alexjust/public_html/wp-content/plugins/contestfriend/tables/table-participants.php:446) in /home4/alexjust/public_html/wp-content/plugins/arscode-ninja-popups/arscode-ninja-popups.php on line 1706

    Warning: Cannot modify header information – headers already sent by (output started at /home4/alexjust/public_html/wp-content/plugins/contestfriend/tables/table-participants.php:446) in /home4/alexjust/public_html/wp-admin/includes/misc.php on line 1126

Viewing 1 replies (of 1 total)
  • Plugin Contributor gidomanders

    (@gidomanders)

    6 years, 6 months ago

    The messages you see are warnings, so you could change the PHP configuration to not display warnings (or any messages at all). The second and third warning are caused by the first warning, as there is something sent to the output buffer before a session could be started or headers could be set.

    You could try to change WP_DEBUG to false define( 'WP_DEBUG', false ); in your wp-config.php. If that doesn’t work, add error_reporting( E_ERROR ^ E_WARNING ); directly below the WP_DEBUG definition. You could also disable all reporting by adding error_reporting(0); instead.

    If none of the above works, please ask your host to help you by changing the core PHP settings. They’ll know what I mean.

    If you’re still having issues after this was fixed, please don’t hesitate to ask. I’m happy to help!

Viewing 1 replies (of 1 total)
  • The topic ‘W3 Total Cache broke a plug in’ is closed to new replies.