Getting errors after host server upgrade to PHP 7.2
Quote from Deleted user on September 29, 2018, 11:01 pmGoing to https://agsgerbils.org/forums/ shows these errors: Warning: Cannot modify header information - headers already sent by (output started at /home/agsgerbi/public_html/index.php:1) in /home/agsgerbi/public_html/wp-content/plugins/asgaros-forum/includes/forum-unread.php on line 36 Warning: Cannot modify header information - headers already sent by (output started at /home/agsgerbi/public_html/index.php:1) in /home/agsgerbi/public_html/wp-content/plugins/asgaros-forum/includes/forum-online.php on line 78
Going to https://agsgerbils.org/forums/ shows these errors: Warning: Cannot modify header information - headers already sent by (output started at /home/agsgerbi/public_html/index.php:1) in /home/agsgerbi/public_html/wp-content/plugins/asgaros-forum/includes/forum-unread.php on line 36 Warning: Cannot modify header information - headers already sent by (output started at /home/agsgerbi/public_html/index.php:1) in /home/agsgerbi/public_html/wp-content/plugins/asgaros-forum/includes/forum-online.php on line 78
Quote from Asgaros on September 30, 2018, 5:19 amHello @savaena
It seems that the forum has problems setting the cookies so it throws the “Headers already sent” error. Because the forum does not throw any other errors before this means that another plugin or your theme is throwing an error which prevents other plugins (in this case Asgaros Forum) from continue working normally.
Please try first to disable other plugins one by one to find the plugin which is causing this error so you can inform the developer about this problem.
Hello @savaena
It seems that the forum has problems setting the cookies so it throws the “Headers already sent” error. Because the forum does not throw any other errors before this means that another plugin or your theme is throwing an error which prevents other plugins (in this case Asgaros Forum) from continue working normally.
Please try first to disable other plugins one by one to find the plugin which is causing this error so you can inform the developer about this problem.