-
Type:
Regression Bug
-
Status: Closed
-
Resolution: No Longer Reproducible
-
Affects Version/s: 6.2.0 CE M5
-
Fix Version/s: 6.2.0 CE M5
-
Component/s: Activities widget, ~ [Archived] Social Networking
-
Labels:
-
Caused by:Another improvement
-
Where was the bug?:Java
-
Git Pull Request:
issue description
SocialActivityInterpreterLocalServiceImpl.addActivityInterpreter method uses StringPool.BLANK as a selector when putting interpreters into _activityInterpreters. Every subsequent calls rewrite the previously put interpreter, so only one interpreter will be stored in the hash.
portal-web/docroot/html/taglib/ui/social_activities/page.jsp also uses StringPool.BLANK as a selector when calling SocialActivityInterpreterLocalServiceUtil.interpret (see /html/taglib/ui/social_activities/init.jsp).
This caused, that only one type of social activity will be displayed in Activities portlets.
cause
The cause is probably in LPS-33320 which provided the new method : getSelector() in BaseSocialActivityInterpreter.
Steps to reproduce
put Activities portlet on a page
create a blog message
create a webcontent
expected behaviour
Activities portlet should show 2 messages
Experienced behaviour
Activities portlet shows only 1 or none message
- is caused by
-
LPS-33320 Allow interpreters to register different contexts
-
- Closed
-