Ya, that's what I'm doing now, but it just seems like a pain to keep
track of it and make sure the menus are consistent based on the group
parameter. The other option was keeping it in a session, but that
creates a problem with not having direct access to a resource through
a url itself.
On Jun 16, 3:23 pm, Andreas andreasderk...@arcor.de wrote:
Hi Steve,
why dont you just pass the group_id as a parameter to the index action?
Like:www.mydomain.com/videos/index/groupname2
greets
Andreas
Steve schrieb:
I'm trying to determine the best way to have dynamic actions but
hopefully the community can help.
What I mean by dynamic actions is that many actions like /posts/
index/, /videos/index/, are all dependent on the variable group_id.
In other words, those actions are only supposed to list all posts,
videos, etc belonging to a specific group.
What's the best way to do this so the URLs are consistent?
I would think that doing something like this is a good approach. :
www.mydomain.com/group/groupname1/posts/index/
www.mydomain.com/group/groupname1/videos/index/
www.mydomain.com/group/groupname2/posts/index/
www.mydomain.com/group/groupname3/posts/index/
This would require some modication of routes.php ... it would also be
great if the following link would act as a dashboard for the
particular group:www.mydomain.com/group/groupname1/posts/index/
Any other suggestions?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
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?hl=en
-~--~~~~--~~--~--~---
