Moderator
t-p
(@t-p)
Try deleting the old wp-includes folder and replace it with a fresh copy. Download a fresh copy of the WordPress .zip file to your computer, unzip it, and use that to copy up wp-includes folder.
And I was so hopeful… Before making any change to production I did a file compare between the class.wp-styles.php installed and the one I extracted from a downloaded zip file. They are identical. Other ideas?
We are getting pummeled by this problem, hundreds and hundreds of errors are raised each day. This was never an issue before we moved from 4.5 to 4.5.2.
Can I get some help with this or not? If not, how do I back up to version 4.5?
Here is a good youtube video on how to go back to a previous version. I would recommend backing everything up before making changes.
How to downgrade WordPress…
Or, if you hosting provider makes nightly backups, you could ask them to restore to a previous backup when the version was still 4.5.
Thanks. Will check it out.
So, apparently version 4.5.2 introducing problems is of no concern. I mean, really, we’re supposed to never update again?
We have had our own session management for ages
And that is probably the problem. Going back to a previous version may work but it is not a solution.
You can also check here, https://codex.wordpress.org/FAQ_Troubleshooting#How_do_I_solve_the_Headers_already_sent_warning_problem.3F
There is a built-in WP session manager? I didn’t see anything in the WP functions. Should I schedule an optometrist appointment?
I looked at the suggested link, and am already familiar with what can lead to the error. In this case, though, the error began to occur with the install of 4.5.2, and the echo statement at /var/www/html/wp-includes/class.wp-styles.php:237 is where the first output character is emitted. Then I come along later with a session_start() command in a theme functions file, which leads to the error.
With my fingers crossed… I *think* I may have successfully addressed the problem. I took a look here and moved my session_start upstream, into an init action. In the 45 minutes that have elapsed since this change, none of the aforecited errors have occurred. More importantly, the objective for the sessions to being used to begin with seems to have not been compromised.