I am using custom slugs that the user creates when they sign up. 
 
USER:
id
slug
.........
 
When a User makes an entry / post or other actions on the site everything is
tied to the slug in the URL and in the controller get the Auth->ID of the
user for that slug.... as that's the foreign key ID, the slug is pretty much
for URL routes.
 
I am trying to avoid exposing any primary keys on the site and pretty much
have it all covered except for the forms. Everything comes up
action="posts/edit/5" or 
something along those lines letting a smart user know they are User.id => 5
 
How can I go about using he slug rather than the ID? At this point I do not
want to have to mess with tables and relationships based on foreign keys.
 
the site has the user slug before the controller name so everything looks
like :
joesmith/posts/
joesith/profile
so on...
 
Suggestions?
 
Dave 

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to