I’ve experienced an anomaly on my random blog; the database shut comments after just a week, instead of on the 22 day rule I’d set.<\/p>\n\n\n\n
The first thing I did was look at every plugin and parent\/child theme for anything that could cause a conflict. That was an afternoon I’m never going to get back. But the long and short is there were no conflict-causes.<\/p>\n\n\n\n
I wondered if any of the largescale work I’d recently completed on the main website and shop might have impacted the blog, but the way I’ve set up the subdomain and separate databases for the core and the sub, threw that idea out.<\/p>\n\n\n\n
So than I cracked open the blog database and looked for a gash character or some other bad field and I found… Nothing. Not a sausage.<\/p>\n\n\n\n
Bizarre.<\/p>\n\n\n\n
So I flushed the database and ran a healthcheck on what the flushed database looked like compared to the unflushed version. A field-by-field comparison gave up no data issues, nothing looked out of order. But the flushed database was 2.3Mb smaller.<\/p>\n\n\n\n
Then I set a realtime comments test and the reaction to that was perfectly normal.<\/p>\n\n\n\n
So something in the DB which got flushed out? A gash character, a random value somewhere?<\/p>\n\n\n\n
I have no idea, and that’s *very* annoying.<\/p>\n\n\n\n I’ve experienced an anomaly on my random blog; the database shut comments after just a week, instead of on the 22 day rule I’d set. The first thing I did was look at every plugin and parent\/child theme for anything that could cause a conflict. That was an afternoon I’m \u2026 Continue reading ![\"\"](\"https:\/\/ahorseforonebin.co.uk\/wp-content\/uploads\/2024\/07\/Flushed.png\")
<\/a><\/figure>\n","protected":false},"excerpt":{"rendered":"