404 page does not view on next level down child pages.

Can you replicate this using Twenty Eleven with all plugins deactivated?

Hi Esmi. I don’t use Twenty Eleven. And I just tried deactivating the plugins to see if that changed anything. Nope.

Can you replicate this when you use Twenty Eleven?

I just tried it in Twenty Eleven. The problem does not exist in this template.

Then it would seem to be a problem within your current theme.

Yup, that would appear so.

Maybe there’s a theme expert out there who knows a work-around? Anybody?

So far, you haven’t even given us the url of your site so we can see your current theme. We’re good but we’re not psychic. ??

Yes, you’ve located the solution — when you suggested that I select “default” in the permalinks settings. I found that if I select anything other than “post name” in Permalinks, the problem stops. So, play around with the permalinks options and the problem goes away.

Thanks again for your help Esmi.

How can i change my admin log-in url setting by ftp for My site?

@hasnat: It is considered impolite to interrupt another poster’s thread. Please stick to your own topic.

@laptophobo: That’s still a little weird. The post name permalink option was only added in 3.3. I wonder if you’ve hit a server config issue? Going to see if I can get some more eyes on this.

I sent the author of the theme an email about the issue. Hopefully he can shed some light on the subject. Thanks for taking an interest in this though.

Are you using any custom page templates? Does the theme use any custom queries – either in page.php or functions.php? If the theme author is doing something funky with queries, this could be having a knock on effect on your 404s.

The pages, per example at the top of this thread, were all part of a custom page. And the original Theme was created before the version 3.3 option for “post name.” So, this might be why. Anyway, as long as I stay away from choosing “post name” for permalinks, it’s working.

The pages, per example at the top of this thread, were all part of a custom page.

What happens if you just use the default page.php template? I’m really curious as to why that specific permalink structure isn’t working, Nornmally it’s either all of the present custom structures work or none of them do (because mod_rewrite isn’t running or the .htaccess isn’t being updated). I’ve not seen just 1 preset fail before and the fact that it’s the newest makes it worthy of a bit more digging.

Added to which, the precise permalink structure should not affect Pages – only Posts. Which makes this even weirder.

The same problem occurs even on default page.php template.
As for why this problem affects pages and not posts is indeed weird.