@KK, I have studied all the advanced concepts by now, as our community project required, and now going through Advanced Tutorial. This Custom Routes addon is very nice and easy to implement.
What is the main difference between pushing url with gpc or custom route, in essense? Something, that can not be achieved the usual way, made possible only by routes?
What if a url would be like:
What do I miss here?
What is the main difference between pushing url with gpc or custom route, in essense? Something, that can not be achieved the usual way, made possible only by routes?
KK wrote: For example, following could be a prettyURL that edits invoice no. 190 that resides in a folder of id 11 - Quote: http://www.yoursite.com/invoice/190/edit/11/folder/
Clearly, the default views of Couch won't be of much help in this situation.
What if a url would be like:
With such url, after easy parsing with gpc we have usual k_is_home and data-bound-form stores input to page.http://www.yoursite.com/invoice.php?folder=11&id=190&edit=1
What do I miss here?