URL Routing for Admin Area
Posted: Fri Nov 16, 2012 6:07 pm
Hey All!
I'm developing a site for a client and he would prefer to have "pretty urls" for the admin area and remove the token string.
I'm working to create a separate version of the seo_url controller to use in the admin area but I'd like to pick the brains of any other devs to see what might be the best way to make it work without a bunch of user intervention.
In other words, we can't add all these pages to the url_alias table, the router needs to be able to route and rewrite urls based on what already exists as opposed to entering keywords as we do with products, information etc. Obviously some dynamic routing would be best as opposed to adding each possible call to the seo_url controller.
And then there's the token ... maybe I'm not getting it completely, but the token is already set in the session, it seems redundant to me to have to pass the token in the request. In the current schema we're testing to see if the user is logged in, we're testing if the token is passed in the request, and then we're testing the request token against the session token.
Is there some reason I'm missing that the token can't be linked to the $user->login so that we can simply test the logged in token with the session token?
Anyway, I'd appreciate an thoughts and advice on knocking this out, then of course I'll be happy to share it with the community.
Thanks guys!
-V
I'm developing a site for a client and he would prefer to have "pretty urls" for the admin area and remove the token string.
I'm working to create a separate version of the seo_url controller to use in the admin area but I'd like to pick the brains of any other devs to see what might be the best way to make it work without a bunch of user intervention.
In other words, we can't add all these pages to the url_alias table, the router needs to be able to route and rewrite urls based on what already exists as opposed to entering keywords as we do with products, information etc. Obviously some dynamic routing would be best as opposed to adding each possible call to the seo_url controller.
And then there's the token ... maybe I'm not getting it completely, but the token is already set in the session, it seems redundant to me to have to pass the token in the request. In the current schema we're testing to see if the user is logged in, we're testing if the token is passed in the request, and then we're testing the request token against the session token.
Is there some reason I'm missing that the token can't be linked to the $user->login so that we can simply test the logged in token with the session token?
Anyway, I'd appreciate an thoughts and advice on knocking this out, then of course I'll be happy to share it with the community.
Thanks guys!
-V