Finding a bug in Textpattern’s URL resolution logic

I’ve been migrating WordPress blogs I host for people over to Textpattern. It’s a quality of life thing for all parties involved. In the process of replicating how people had their WordPress sites configured, I uncovered a subtle bug in the way Textpattern resolves URLs. tl;dr: If your article links 404, define an empty section with something other than the side default URL pattern, and your links will work again. This will be addressed in 4.9.2. How Textpattern defines pretty URLs By default, Textpattern’s article URL pattern (what WordPress calls a permalink structure) uses your standard GET request scheme: http://example.com/?=messy If you want pretty URLs, Textpattern supports the following schemes: /id/title /section/id/title /section/category/title /year/month/day/title /breadcrumb/title /section/title /title Textpattern will write the appropriate Apache configuration for you if you select one. nginx can also be configured to do this with similar config to what you’d use for…