I just uninstalled and installed the latest 2.2.1 (210446)  and the bug is 
still 
there.  There is something incorrect with the commands "user_name" as I have 
combed through the working version and this one and every xml file is stil the 
same.




________________________________
From: Trilo Byte <trilobyte5...@gmail.com>
To: miss c <miss_c...@yahoo.com>
Cc: opensource-dev@lists.secondlife.com
Sent: Fri, September 24, 2010 6:13:58 PM
Subject: Re: [opensource-dev] major problem with beta 2.2 - link

I've seen the problem as well (and voted on the issue), but did not see it in 
the 2.2.0 beta (build 210127).  This only broke in a more recent build (one of 
the ones from yesterday, I believe).


On Sep 24, 2010, at 4:11 PM, miss c wrote:


>Here is a screen shot of the bug
>
>http://www.flickr.com/photos/toxiancity/5021728112/#/photos/toxiancity/5021728112/lightbox/
>
>
>
>
________________________________
From: Kent Quirk (Q Linden) <q...@lindenlab.com>
>To: Erin Mallory <angel_of_crim...@hotmail.com>
>Cc: opensource-dev@lists.secondlife.com
>Sent: Fri, September 24, 2010 4:39:37 PM
>Subject: Re: [opensource-dev] major problem with beta 2.2
>
>
>
>On Sep 24, 2010, at 2:36 PM, Erin Mallory wrote:
>
>As a User I expect and NEED usernames to be displayed in group chat and used 
>properly in group and conference chat logs.
>>Instead I am seeing in both chat and in logs, usernames replaced with the 
>>group 
>>or conference name!!!
>>
>>

>
>
>I see this in the development tip (210412) but NOT in the beta (210127). Is 
>anyone seeing it in the beta?
>
>_______________________________________________
>Policies and (un)subscribe information available here:
>http://wiki.secondlife.com/wiki/OpenSource-Dev
>Please read the policies before posting to keep unmoderated posting privileges



      
_______________________________________________
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges

Reply via email to