The WordPress Rabbit Hole
There is a particular kind of afternoon that WordPress users know well. It begins with a minor irritation — an option that does not behave, a setting that appears to have no effect, a folder structure that persists despite being told not to. It ends, some hours later, in the same place it started, except now there are seventeen browser tabs open and a vague sense that the problem was never really the problem.
The setting in question barely matters. It could be the checkbox that is supposed to stop WordPress from organizing uploaded media into year and month subfolders. It could be a permalink that refuses to flush. It could be a widget that reappears after deletion, or a plugin conflict that only surfaces on Tuesdays, or a caching layer that insists on serving a version of your site that has not existed since last quarter. The specific issue is almost beside the point.
What matters is the structure of the experience, which is always the same. You change a setting. The setting does not change. You verify the setting has changed. It has. The behavior has not. You search for an explanation. You find seventeen explanations, none of which quite match your situation, all of which were written for a version of WordPress that predates your current installation by two major releases. You begin to wonder whether the problem is the theme, the plugin, the database, the host, the browser cache, the server cache, the object cache, or some spectral fourth thing that exists between all of them.
This is the rabbit hole. It is not a failure of documentation, exactly, though the documentation is often poor. It is a failure of architecture — a system that has accumulated twenty years of decisions, each individually reasonable, into a whole that is not quite coherent. WordPress was not designed so much as it grew. Settings interact with filters interact with hooks interact with options stored in a database table that any plugin can read and overwrite without announcement. When something does not work, the cause could be anywhere. When you fix it, you are often not entirely sure why.
The honest response to this situation is to decide, before you begin, whether the problem is worth solving. Most of the time it is not. A media library organized by year and month is not a meaningful obstacle to publishing. A permalink that works is a permalink that works, regardless of how it came to work. The rabbit hole is not a place where important problems get resolved. It is a place where time goes to become something other than work.
Publishers who operate at scale learn this threshold early. The platform is a means, not an end, and the hours spent coaxing it into compliance are hours not spent on the thing the platform exists to deliver. WordPress is a very good tool for publishing words on the internet. It is a very poor subject for extended contemplation.
Close the tab. Leave the year-month folders where they are. The readers do not see them.