Forums

mouse over of user name with spaces, causes error

This question is answered

TC5 SP1

 

Hi, I have user names with spaces and get the following on mouseover. I read that  the  fix was going to be included in SP1 - but that doesn't appear to be the case.

Is there a fix for this? It's a really ugly (literally) problem and I'd rather not get all my users to change their user names.

 

Verified Answer
  • I don't know why it take so long for Telligent to fix this bug as well as why it wasn't fixed in SP1.

    But anyway, we made a quick fix for it 

    Technical details:

    There are 2 reasons for this bug or actually 2 bugs with cumulative effect :)

    1. Incorrect processing of user names with spaces (like "c r i s", which system translate to "c-r-i-s")  and dashes (like "c-r-i-s", which system translate to "c_2D00_r_2D00_i_2D00_s"). This need to be addressed in Web\Utility\FooterFragments\Core\UserInfoPopup.ascx. An example how it should be treated see in hot fix.

    2. Incorrect Ajax method in web service CommunityServer.Web.Utility.FooterFragments.Core.UserInfoPopupAjax, which get user details based on userProfileUrlPattern (see 1'st reason). When we call Users.GetUser(Globals.UrlDecodePathComponent(username)) we actually ignore the fact, that user name might have space characters. In a fix we created UserInfoPopuAjax inherited from CommunityServer.Web.Utility.FooterFragments.Core.UserInfoPopupAjax with GetUserInfoByUsername method which takes care about spaces in username directly.

     

     

All Replies
  • Unfortunately the problem appears to still be occurring.  The product team is aware of this, however I unfortunately do not have specific information regarding how they will fix this.  Hopefully someone from the product team will reply to this thread once they know more information.

  • Thanks Brian - here's hoping there is a fix. Can't go live with something so blatant.

  • Can Telligent please let us know when this is going to be fixed - it's a very ugly problem...

    Brian Skok

    Unfortunately the problem appears to still be occurring.  The product team is aware of this, however I unfortunately do not have specific information regarding how they will fix this.  Hopefully someone from the product team will reply to this thread once they know more information.

     

  • Yes It's an ugly bug and should be fix, I though I was the only who noticed it.

  • I don't know why it take so long for Telligent to fix this bug as well as why it wasn't fixed in SP1.

    But anyway, we made a quick fix for it 

    Technical details:

    There are 2 reasons for this bug or actually 2 bugs with cumulative effect :)

    1. Incorrect processing of user names with spaces (like "c r i s", which system translate to "c-r-i-s")  and dashes (like "c-r-i-s", which system translate to "c_2D00_r_2D00_i_2D00_s"). This need to be addressed in Web\Utility\FooterFragments\Core\UserInfoPopup.ascx. An example how it should be treated see in hot fix.

    2. Incorrect Ajax method in web service CommunityServer.Web.Utility.FooterFragments.Core.UserInfoPopupAjax, which get user details based on userProfileUrlPattern (see 1'st reason). When we call Users.GetUser(Globals.UrlDecodePathComponent(username)) we actually ignore the fact, that user name might have space characters. In a fix we created UserInfoPopuAjax inherited from CommunityServer.Web.Utility.FooterFragments.Core.UserInfoPopupAjax with GetUserInfoByUsername method which takes care about spaces in username directly.

     

     

  • Brilliant Dmitry -

    Installed and fixed!

    Thank you

    Chris

  • You're welcome Chris!

    Hope Telligent will fix it eventually since personally I'm against hot fixes in core CS from 3rd parties.

  • FYI, there were (at least) three similar bugs around user names with spaces in.  One was fixed in SP1 but the other two have only come to light after SP1's release.

  • I reported this one before SP1 was released. Although only in the forum.