Slugs in WordPress cannot be all numeric.
This is because of the ruleset WordPress uses for paging of posts. A post can be broken into multiple pages, and have URLs like this:
http://example.com/postname
http://example.com/postname/2
http://example.com/postname/3
And so on. The numbers are pages. If it allowed numeric slugs, then there would be cases where it couldn’t determine if a url segment was a page number or a post slug.
Thanks for the response! Could I add an exception in my .htaccess to point /101 to the ?id= for that page?
You know, I have not looked at this in some time, and so I am actually not certain my information is correct.
I do know that this was a problem around 4 years ago. It may still be a problem, and after a quick search, I found a plugin from around that time which would allow it at the expensive of pagination:
https://wordpress.org/plugins/allow-numeric-stubs/
I do not know if that plugin will work anymore, or is necessary. You can give it a shot though.
I think the only problem that I would run into is with the paging on the blog section of the site, at least according to the description of that plugin.
I’m looking into an .htaccess solution for the time being, or worst case I suppose I could just add a /101 folder to the root of my site and go from there.
paging on the blog section
No, the paging on the blog section would be unaffected. The paging on individual multi-page posts would be what is affected here. In other words, you wouldn’t be able to use the <!--nextpage--> tag in posts anymore.
