It’s hard to troubleshoot the problem without knowing what all your rewrite rules are. For rewrite debugging I use the Rewrite rules Inspector plugin. Install and activate the plugin then go to the inspector under the tools menu. In the search box paste in on of the /%year%/%monthnum%/%postname%/ urls you mentioned and it will give you the rule that this is matching.
You can also deactivate all your plugins and switch to the default theme, twentytwelve then flush your rules and see if the problem exists then go through and activate your plugins one by one to find out the culprit.
What’s in your .htaccess? Any weird httpd.conf rules?
@ Ipstenu
Nothing weird in .httaccess or htttpd.conf.
For the development/testing site, it’s the default network rules:
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]
# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ – [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]
@ Chris Olbekson
Okay, I 1) switched to TwentyTwelve,
2) flushed rules using the Rewrite Rules plugin — posts begin working fine with year/monthnum/postname permalinks.
3) Switch back to my custom themee, posts continue to work as expected.
Hurray!
BUT
Then custom post types, like /person/ are 404s.
Normally, I just go reset the permalinks (make sure that /blog/ isn’t in network permalink settings. That typically fixes that, and it does, but then the original post permalink problem reappears.
When I give the Rewrite Rules plugin a post, this is what it’s telling me:
Example:
http://engineering-redesign.missouri.edu/2013/01/new-study-rooms-allow-quiet-group-gatherings/
Rule
([0-9]{4})/([0-9]{1,2})/([^/]+)/?$
Rewrite
index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]
Source
date
Rule
([0-9]{4})/([0-9]{1,2})/([^/]+)(/[0-9]+)?/?$
Rewrite
index.php?year=$matches[1]&monthnum=$matches[2]&name=$matches[3]&page=$matches[4]
Source
post
Rule
(.?.+?)(/[0-9]+)?/?$
Rewrite
index.php?pagename=$matches[1]&page=$matches[2]
Source
page
This looks like a lead:
Using this script:
http://www.dev4press.com/2012/tutorials/wordpress/practical/debug-wordpress-rewrite-rules-matching/
I see this:
<!– Request: 2013/03/hard-work-pays-off-with-great-job-offer –>
<!– Matched Rewrite Rule: ([0-9]{4})/([0-9]{1,2})/([^/]+)/?$ –>
<!– Matched Rewrite Query: year=2013&monthnum=03&day=hard-work-pays-off-with-great-job-offer –>
<!– Loaded Template: archive.php –>
day instead of postname.
Do CPTs work on the default theme? It sounds like they’re set up wrong in the code.
No, the custom posts types don’t work with the default theme. They’re written into the functions.php file — not plugins.
Yes! I found the problem.
I had a conflict with a taxonomy slug.
I am kicking myself right now — I named a taxonomy “day”.
Thank you for the help everyone.
