Page 1 of 1

Issues with navigation

Posted: Wed Apr 30, 2008 7:39 pm
by forevernomad
hi,

I'm using cmsms 1.2.3

I've got pretty urls switched, and I've just noticed that the navigation seems a little out.

example

'base/parent/child' is the correct path, but 'base/parents/child' takes me to the same page, anyone know why that is?

thanks.

Re: Issues with navigation

Posted: Thu May 01, 2008 9:57 am
by forevernomad
Nobody?

Isn't this a serious security issue?

Re: Issues with navigation

Posted: Thu May 01, 2008 1:44 pm
by calguy1000
No, it's not a serious security issue..... because the page alias is always enforced to be unique...

therefore:  base/parent1/parent2/parent3/page-alias is largely just for display purposes.    just using the page-alias is just as good.

Re: Issues with navigation

Posted: Thu May 01, 2008 4:43 pm
by forevernomad
but the page alias here for example is 'parent' not 'parents' they should be two completely different sections shouldn't they?

Re: Issues with navigation

Posted: Thu May 01, 2008 5:34 pm
by RonnyK
forevernomad,

the page you are calling, independant of where it is, has a unique alias, so no matter what parents are above, the called page (in your example the child) has an unique alias.....

Ronny

Re: Issues with navigation

Posted: Thu May 01, 2008 9:48 pm
by forevernomad
I was playing around to see how far it went and I realised that's how it works.

I tried base/sdfhsdfhs kfdhs/dsfh shfhj fjsfhssjddfjh/sdjdfjfh hsjdfhj hsjfhksdf/dfsjfjk fsddfjk hs/page (literally)

It still went to page.

It's just that I've been to a lot of sites that have pretty urls and if I mistype the path I get a 404, I was expecting the same here, I thought that was how it worked. Sorry if I was out of line.

Re: Issues with navigation

Posted: Tue May 06, 2008 12:04 pm
by Pierre M.
Hello,

any authorization test you put in a tag at the begining of the page is enforced whatever the/parent/urlpath/to/page. Hence this is not a security issue.

It may be a "duplicate content" issue with bugy bots. It should be fixed in 2.0 with /clean/hierarchy/parent/page.html.

Pierre M.