Databases
StackOverflow2013
Postsdbo
POCreate "pretty" user profile URLs in Grails application
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCreate "pretty" user profile URLs in Grails application
    primarykey
    data
    text
    <p>Anybody who already have implemented something similar using Grails could tell me please which are the good pratices (if there are any) to create user profile URLs with the format "<a href="http://www.myservice.com/username" rel="nofollow">http://www.myservice.com/username</a>", as in Facebook, Twitter, Linkedin?</p> <p>I'm trying to implement it through the UrlMappings and appears to me I'll need to break with the code conventions, at least for the Controllers.</p> <p>So, any suggestions are welcome, thanks.</p> <p><strong>UPDATE 1</strong></p> <p>When I mentioned my concern about breaking the code conventions, what I'm saying is that I want to show the user profile using this mapping, but I do have other objects in my application which I would like to access using the default mapping:</p> <pre><code>"/$controller/$action?/$id?"() </code></pre> <hr> <p><strong>SOLUTION</strong></p> <p>Thanks to the great contributions I've received here, I've camed up with this solution, which solves <em>my problem</em>.</p> <p>As was pointed out, to do this kind of mapping, I'll need to control more closely how my requests are handled. That means I'll need to tell to Grails which controllers I don't want to be mapped to the "username" rule.</p> <p>Since that will be a very tedious task (because I have several controllers), I did this to automate it:</p> <p><strong>UrlMappings.groovy</strong></p> <pre><code>static mappings = { getGrailsApplication().controllerClasses.each{ controllerClass -&gt; "/${controllerClass.logicalPropertyName}/$action?/$id?"(controller: controllerClass.logicalPropertyName) } "/$username/$action?"(controller: "user", action: "profile") } ... } </code></pre> <p>And of course, I'll need to do something similar in my user registration process to avoid usernames to be equal to some controller name. </p> <p>That's it, thank you all.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USUilian
    1. USUilian
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCreate "pretty" user profile URLs in Grails application
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCreate "pretty" user profile URLs in Grails application
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POCreate "pretty" user profile URLs in Grails application
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO[this tutorial](http://www.ibm.com/developerworks/library/j-grails03109/) does something very similar, I guess you can get some directions from it. (Section `Displaying entries by author`)
      singulars
      1. POCreate "pretty" user profile URLs in Grails application
      1. USmoeTi
    2. COThanks, but that isn't quite what I need. This tutorial deals with the mapping problem, but avoids the multiple possible matches to an URL by preffixing it with "/blog/".
      singulars
      1. POCreate "pretty" user profile URLs in Grails application
      1. USUilian
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload