[jira] Commented: (ESME-327) URL path problems

["Dick Hirsch (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ESME-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986974#action_12986974 ] 

Dick Hirsch commented on ESME-327:
----------------------------------

As Ethan suggested, the change isn't as easy as I thought:

Here is my current effort - which isn't finished yet

      var pathArray = top.location.pathname.split( '/' ); 
          
      // Dealing with tomcat
      if (top.location.pathName == "/") 
      	  newMsg.find('#author').attr('href',"/user/" + msgAuthor.nickname );
     else { 
     	 if (pathArray.length==3)
     	    newMsg.find('#author').attr('href', pathArray[1] + "/user/" + msgAuthor.nickname ); 
     	 else  	 
      	   newMsg.find('#author').attr('href', "../user/" + msgAuthor.nickname ); 
     }
     
     
     
           // Dealing with users with no avatars
      if (!msgAuthor.imageUrl) {
        if (top.location.pathName == "/") 
      	   msgAuthor.imageUrl= "/images/avatar.jpg"
      	else
      	  msgAuthor.imageUrl= "../images/avatar.jpg" 
     }

> URL path problems
> -----------------
>
>                 Key: ESME-327
>                 URL: https://issues.apache.org/jira/browse/ESME-327
>             Project: ESME
>          Issue Type: Bug
>          Components: UI
>    Affects Versions: 1.2
>            Reporter: Dick Hirsch
>             Fix For: 1.2
>
>
> I have noticed this several places, but this is a concrete example.
> webapp/scripts/display_messages_top.js:198, sets a link to message
> author like so:
> newMsg.find('#author').attr('href', "/user/" + msgAuthor.nickname );
> this causes problems when running with a non / context on tomcat
> For example, if esme in running here:
> http://foo.bar.com/esme/
> the above will create this link:
> http://foo.bar.com/user/user1
> It appears that tomcat(? or lift?) does the right thing,
> snippet/UserSnip.scala:121 does this
> <a href={"/user/"+urlEncode(u.nickname.is)}>
> which gives the correct location:
> http://foo.bar.com/esme/user/user1
> My javascript foo isn't strong enough to know if there's a way to
> solve this in js.  Perhaps the best way is putting it in the template
> and just having the js fill in the username?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.