Visit Options->Permalinks and click “Update Permalink Structure” to get the fixed rewrite rules.
Thread Starter
fo3nix
(@fo3nix)
sorry no my problem was obviously unclear.
I have following page structure:
a
-css
–b
–c
-css
–d
–e
when I click on either of the two ‘css’ pages, content from both pages shows at the same time. This isn’t a permalink problem.
I am aware that it is a recorded bug, just wondering if it’s been fixed in 1.5.1 or not. I have updated, but it doesn’t seem like its been fixed. And it is kinda major…
I don’t get it. Are you saying you have posts with the same name that contain different associated comments? Your page structure (above) seems to show a heirarchy of like-titled subdivisions (‘css’). Plus, though I’m certainly no expert, I haven’t heard of this ‘bug’. In fact, I’m having trouble imagining how, or why, you have things the way they are.
Curious to see how this thread evolves…
Cheers!
If both pages have the slug css, Then of course only 1 would show. Try changing the slug to css-1 and leave the name css on both. So one slug is css and the other css-1.
Yes, if two posts/pages have the same name, the second of the two posts to be created will have a number appended to the slug to distinguish it. There was a problem where page slugs that are different only by a trailing number would sometimes collide in the rewrite rules. That was fixed by updated rewrite rules. If both of them have the exact same slug, change the slug on one of them.
Thread Starter
fo3nix
(@fo3nix)
I do apologise. I got the structure wrong. It’s more like this:
a
b
-css
c
d
-css
e
This is the problem. clicking either of the css pages results in content from both pages being displayed. Both pages have a different URL (first is /b/css, second will be /d/css). However they both obviously share the same slug; this is the problem. If I change the slug, I don’t get the problem. But I want them to have the same slug… if this were a standard file structure then they would be uniquely identifiable.
So I suppose its not really a bug. But I do think it would be a significant improvement..
Thread Starter
fo3nix
(@fo3nix)
is there any possibility that this could be done with 1.5.1… or is there any way to be able to do it in later versions?
