aseanmp

We had outside tech support help us resolve the problem, so unfortunately, I can’t tell you exactly which file it was. But from what I understand, it was the entire theme that was the issue. We basically just replaced the corrupted theme with a version from a previous backup via the cpanel–as if we just changed the theme entirely. I hope that helps!

Thanks again for your helpful suggestions! In the end, it was a theme issue–the theme itself was corrupted. The website worked fine when we tested it on a different theme, so that’s how we knew for sure. We were able to resolve the issue (with the help of outside support) by replacing the theme with a copy from a previous backup. Still no idea what caused the errors to begin with (since, as I said, I hadn’t made any new changes to the theme), but very glad to have it resolved at least!

Thanks for your suggestions! I tried deactivating all plugins via the cpanel (changing the name of the folder to “plugins.deactivate”) but the problem didn’t go away on the main site or the admin side.

The wp-config.php file didn’t have define( ‘WP_DEBUG_LOG’, true OR false , so that’s not the issue either, I guess.

I’m hesitant to fiddle with the wp-config.php file or any other php files under wp-content since they haven’t been modified in a long time–since our website was redesigned a year and a half ago.

Also, as an update, the website issues seem to have gotten worse. The main content of the website now no longer displays properly. Instead, it displays things like this:

[/vc_column_text][vc_column_text][chimpmate][/vc_column_text]

This happened before I deactivated all plugins (before I made any real changes, in fact), so I’m not sure what’s going on.

Since the ‘cannot modify header’ problem seems to have started at a specific error log, would it be okay for me to try deleting the error log referenced? Or will that mess things up more?

Thanks for your response! I checked the wp-config.php file, and it looks like it already says ‘define(‘WP_DEBUG’, false)’, so unfortunately that’s not the solution to the ‘headers already sent’ error.

Regarding the troubleshooting page you linked to, I’m a little confused because it says: output started at /home3/aseanmp/public_html/wp-content/themes/aseanmp/fw/core/error_log:12 – which references the error log, rather than a specific line in a .php file (which the troubleshooting page discusses). Any idea what I should do in that case?

Thanks!