> Am working on a project on which I require your advice. > I am thinking to split a row data to couple of pages. For example: > > Main landing page for row data: > www.example.com/datas/data-title (currently this page displays full > data from particular row) > > What I want looking for is: > www.example.com/datas/data-title (would contain intro texts) > www.example.com/datas/data-title/about-this (some more data from same > row.) > > So, would invite your advice and input on this.
Why not use the Tree behaviour to create the parent/child records? www.example.com/page/about <- top level page www.example.com/page/about/clients <- page that is a child of 'about' You can test this working without any extra routing by going to: www.example.com/pages/view/about/clients - provided your model is Page and your display method is view - have a look at the stop pages controller, it uses func_get_args, you could just look for the final item. Cheers, J -- jon bennett - www.jben.net - blog.jben.net -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
