Catch 404 errors in nested installations
Catch 404 errors in nested installations
Catch 404 errors in nested installations
If you register new custom post types and get weird 404s, you just need to change your permalink settings. This happens to me pretty much every time. You can change the, right back to where they were before. It’s just the act of changing them that does the trick.
These Jetpack settings are stored on WordPress.com. You can refresh them by refreshing permalinks as @GhostToast suggested. You can also force an update of your Jetpack settings by going to the Jetpack menu in your dashboard, and disconnecting then reconnecting to WordPress.com.
Now that it’s working without permalinks enabled, try resetting your permalinks back to the way you want them. That full reset should work. Edit: Are you be doing anything funky with the rewrite argument?
How can I prevent non-existing wordpress pages from getting redirected to home page
Using a custom 410 page
I was having this same issue. I found that the issue was caused because I had set the front page to display a static page for the front page and another for the posts page. (Set in Reading Settings) However, my posts page had been deleted. In this case because we decided not to have … Read more
Hierarchical permalinks for custom post type and taxonomy
Media attachment pages giving 404’s
Multisite sub-directories IIS 7.5 change media/uploads location