1) Turn ON "Infinite scrolling for activity streams (Desktop only)" option in backend
1.1) also turn ON "Bump" function (I'm not sure does something depend of it).
2) Click on hashtag #Бразилия crimson-land.ru/community?filter=hashtag&value=Бразилия
Result 1: In some reason Stream display "More" button at the bottom. Is it normal?
3) Press "More button"
Result 2: Stream will load 10+ random items, but without hashtag #Бразилия (random items).
we will inspect this and create new bug list for it.
I am sorry, not yet.. but we will let you know then :)
I forgot to update this topic.. this issue only happens on your site.. we already inspected this on another site and everything is working fine..
Anyway, have you updated to version 4.4.2? does it work? if still dont i need addtional information phpmyadmin.
Problem is in ...\components\com_community\libraries\activities.php
when loading new activities (More button) is pressed it sends:
second arg2 is keyword ($filter) and (controler/activities.php ajaxGetOlderActivities passes filters to libraries/activities.php to getOlderStream) on function getOlderStream there is no "case" for "keyword" so $filters is not passed to $activitiesModel->getActivities.
There is "case" for hastag.
Maybe this is problem?
Error is present on demo:
this loads one activity (which is correct), but when More button is pressed it loads the rest without looking for "2017" as keyword so presents unfiltered activities.
Also, looks like loading more activities with hashtags does not use same mechanism as keywords but relies on url values so those are not passed to functions.
On my local site (JS 4.4.5.) More button option does not appear when only one activity is displayed when using hastags like on demo (JS 4.4.4.) site.
On the other hand, on same local test site posting activity with hashtag displays "More" button without loading new activity with old ones, but that is my local problem :)
Thank you for the pointer, our developer still busy on chat feature.. will check after the main jobs are done ;)
The issue is fixed on your site. Please check and verify.
We will add this fix in the upcoming update of Jomsocial, that is coming soon :)