The WordPressDBclass is stuffed with warnings, looks like a pretty easy task to clean most of them up and get it looking cleaner.
We should even do the extra step and split WordPressDB, but the migration step is a bit scary :fearful:.
WordPressDB will be dropped with the initial FluxC integration.
Most of WordPressDB has been moved to FluxC. We're still keeping it around for:
Eventually we can drop the migration code, and we'll move themes to a ThemeStore in FluxC, and we'll be able to drop WordPressDB and all references to it.
On that day, @maxme will cackle maniacally as he closes this ticket using a comically oversized bright red button.
On that day, @maxme will cackle maniacally as he closes this ticket using a comically oversized bright red button.

This issue has been marked as stale and will be automatically closed. This happened because:
However, discussion is still welcome! If the issue is still valid, please leave a comment with a brief explanation so the issue can be reopened.
Most helpful comment