Conversation
supportI’m seeing hundreds of copies of this message in my wordpress error log [10-Nov-2022 04:10:51 UTC] PHP Warning: Cannot modify header information - headers already sent in /home/mesmer17/public_html/wp-content/plugins/gridlist-view-for-woocommerce/includes/functions.php on line 26
Looks like the same error I’m getting (see my report 3 days ago), except for me it takes down my whole website.
Hello, Plugin uses cookie to store current list state and it must be set before header send. Plugin set it before WordPress sens any data, but maybe you have some plugin that place some data before our plugin set cookie, that cause this issue, or some plugin has issue that cause this. First of all please try to disable other plugins and change theme to WordPress default to check that it is not compatibility issue. Regards, Oleg
Hello, I have try to disable other plugins and change theme to WordPress default still same PHP warning. Thanks This reply was modified 3 years, 1 month ago by LogicRays Technologies .
Still not resolved. I tried adding `SetEnv SERVER_NAME mydomain’ in my htaccess file. No effect. Could this be caused by forcing HTTPS or by setting strict HTTPS headers?
Looks like the same error I’m getting (see my report 3 days ago), except for me it takes down my whole website.
Hello, Plugin uses cookie to store current list state and it must be set before header send. Plugin set it before WordPress sens any data, but maybe you have some plugin that place some data before our plugin set cookie, that cause this issue, or some plugin has issue that cause this. First of all please try to disable other plugins and change theme to WordPress default to check that it is not compatibility issue. Regards, Oleg
Hello, I have try to disable other plugins and change theme to WordPress default still same PHP warning. Thanks This reply was modified 3 years, 1 month ago by LogicRays Technologies .
Still not resolved. I tried adding `SetEnv SERVER_NAME mydomain’ in my htaccess file. No effect. Could this be caused by forcing HTTPS or by setting strict HTTPS headers?