Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-33243

Chat portlet continually updates the user's status thus flooding the chat with "User is online" messages

    Details

    • Branch Version/s:
      6.1.x
    • Backported to Branch:
      Committed
    • Story Points:
      8

      Description

      Steps to Reproduce
      Steps to reproduce / testing done:
      Set up was done referencing this wiki: http://www.liferay.com/documentation/liferay-portal/6.1/user-guide/-/ai/ch-4

      1. Download ejabberd http://www.process-one.net/en/ejabberd/downloads , use the default settings
      1a. Make sure to start your ejabberd server. The installer should create a Start and Stop icon on your Desktop.
      2. Download the Chat Portlet (attached)
      3. Create a portlet-ext.properties (yes that's right, portlet) as such

      ## Jabber ##
      
      jabber.enabled=true
      jabber.import.user.enabled=true
      jabber.host=liferay-xdc49dh
      jabber.port=5222
      jabber.service.name=liferay-xdc49dh
      jabber.resource=Liferay
      jabber.sock5.proxy.enabled=false
      jabber.sock5.proxy.port=-1
      

      4. Place this properties file inside the Chat portlet in WEB-INF/classes
      5. Deploy your chat portlet and startup Liferay
      6. Within Liferay, create another user and sign in with him in another browser
      7. Chat with each other.

      Here is the issue:

      1. Every time you click on Liferay's chat tabs, the Spark user sees a message that the Liferay user is online (see attached screen shot).

        Attachments

          Activity

            People

            • Assignee:
              sharry.shi Sharry Shi
              Reporter:
              jonathan.mccann Jonathan McCann
              Participants of an Issue:
              Recent user:
              Esther Sanz
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since last comment:
                4 years, 10 weeks, 5 days ago