Different pages are not accessible having second level children same slugs.

google-code-export / django-page-cms

Automatically exported from code.google.com/p/django-page-cms

BSD 3-Clause "New" or "Revised" License

0 stars 0 forks source link

Different pages are not accessible having second level children same slugs. #203

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Create 2 pages at the topmost level. Slugs, say, "foo" and "bar"
2. Create a child for "foo", name the slug "test"
3. Create a child for "bar", name the slug "test"
4. Check that "/foo/" and "/bar/" are accessible. "/foo/test/" and "/bar/test/" 
are not.

What is the expected output? What do you see instead?
Expected to be different pages: aren't "/foo/test/" and "/bar/test/" different 
pages?

Original issue reported on code.google.com by tezro...@gmail.com on 21 Jun 2010 at 9:34

GoogleCodeExporter commented 9 years ago

Have you properly published the child pages?

I try what you describe but it works for me.

Original comment by batiste....@gmail.com on 21 Jun 2010 at 10:16

GoogleCodeExporter commented 9 years ago

Well, I'm not really sure if I do it right, but look at this.

http://gyazo.com/e542d003a0cbe156172eb9b731bc71b5.png

I've changed admin templates to make it humane - show title in default language 
and slug. Have I published all right? I can see foo and bar pages, but nothing 
inside them.

Original comment by tezro...@gmail.com on 21 Jun 2010 at 3:10

GoogleCodeExporter commented 9 years ago

"I can see foo and bar pages, but nothing inside them."

What so you mean by that? Try to be a bit more precise I can't see where is the 
issue. Are you speaking about the frontend or the admin version of the page?

Original comment by batiste....@gmail.com on 24 Jun 2010 at 6:31

GoogleCodeExporter commented 9 years ago

I'm speaking about frontend, yes. In admin everything is beung get by id, but 
at frontend of course by slugs.

When I access these pages I see:
/foo/ - foo's content
/bar/ - bar's content
/foo/test/ - 404
/bar/test/ - 404

If I change the foo/test slug to "test1" so that it is /foo/test1/ then 
everything works right.

You can always chat me at Google Talk.

Original comment by tezro...@gmail.com on 24 Jun 2010 at 7:28

GoogleCodeExporter commented 9 years ago

Do you use the last master revision from github?

I recreated exactly what you describe and I don't see the bug. Could try to 
dump the data so I can try to reproduce?

./manage.py dumpdata pages > pages_bug.json

Original comment by batiste....@gmail.com on 28 Jun 2010 at 9:11

GoogleCodeExporter commented 9 years ago

Yes, I have the master.
Here's the JSON dump.

Thanks for help, really.

Original comment by tezro...@gmail.com on 29 Jun 2010 at 10:40

Attachments:

pages_bug.json

GoogleCodeExporter commented 9 years ago

Hi there, any test results?

Original comment by tezro...@gmail.com on 5 Jul 2010 at 4:31

GoogleCodeExporter commented 9 years ago

Sorry didn't have the time yet. Will have a look when possible.

Original comment by batiste....@gmail.com on 5 Jul 2010 at 4:33

GoogleCodeExporter commented 9 years ago

I installed the data, I used "ru" as the default and only language in my 
settings. Then I copied the example templates from the package so I have an 
"index.html" and a "base.html" template.

The 2 pages "test" and "tests2" display as intended. I suspect an issue with 
your templates. I can't reproduce what you get.

You should try to install from the source of the CMS and try to debug with some 
print statement to know where this 404 is coming from.

http://github.com/batiste/django-page-cms/blob/master/pages/views.py#L10

Original comment by batiste....@gmail.com on 6 Jul 2010 at 7:21