Looks like this issue has already been resolved internally. I have applied the fix for you in the file /administrator/components/com_easysocial/models/search.php and it works fine now

Oh, I am afraid this thing opened a can of problems. Now the sorting for latest login hack from Arlex is not working any longer: https://stackideas.com/forums/make-search-results-for-people-last-login-sort-option-to-default. This is mandatory for me because members use my global filter for radius search and new members get to see very old accounts first which leads them to delete their account because of thinking the site is not visited any longer.

Additionally clicking on city or zip on the profile for searching is not working. You can see on Julia's profile city: "Osnabrück" and zip 49078. When clicking on any of them, the search goes for "staat" (state) instead of "stadt" (city) or "PLZ" (zip).

To make it worse, I just recognized that clicking on the age makes the birthday visible, but due to privacy the birthdate should not be visible. I thought anyone with that age would be searched but the search goes for the birthdate. Can you please give me a hint to unlink the age on profile since there is already the datefinder module for age search.

Looks like the hack that was used is causing this error because of the duplicated ordering.

Looks like the hack that was used is causing this error because of the duplicated ordering.

I am not so sure how to handle that answer Mark. On the one hand you are right but on the other hand you ignored 90% of my text. Should I wait for more or did you just not read my whole text? There is no rush for me and I did not expect an answer during the weekend but I have no idea what to do now.

To reply to your answer, yes you are right, but only about the age link. City and zip are not working, no matter if with or without hack. Additionally the new extended search results at distance search do no longer show the distance as they did at ES1.4. The global filters from ES1.4 can not be sorted, but the ES2 results can. Example (assuming being logged in as Julia):

OLD GLOBAL FILTER: /community/benutzer/Filter/1-umgebungssuche
Distance is shown for each member found but sorted with oldest members.




NEW GLOBAL FILTER: /community/suche/erweitert/28-umgebungssuche-1?type=user
Sorted by latest login but no distance shown for each member.



The problem is, that it is necessary to have the sorting for latest login AND the distance. The distance is necessary because you need to set the global filter according to the amount of users on the site. Do you have several xx thousands member, the distance can be set smaller to still show acceptable amount of results. But still being at x thousands the radius must be bigger and so there distance must be shown for each members.


Could you please tell me which file I need to edit to unlink the age on the profile?

Hacks that are provided are not supported and this is exactly why we cannot and should not provide hacks because it alters the default behavior of the software. The hacks which Arlex provided in the other post causes this error on your site as it is generating duplicated ORDER BY in your query clause.

We provide the software as is and if you think that certain features should be included, please by all means post under the feature requests area.

Also, let me discuss with Arlex about the hacks which he provided tomorrow as today is a public holiday here. Once he gets to the office, I will check what was the hack about and if we could include this as a configurable option in the future.

We provide the software as is and if you think that certain features should be included, please by all means post under the feature requests area.

Hi Mark,

I totally understand the policy about customisations and I can hardly imagine how frustrating it must be gettings support requests about this kind of things all the time. But to be honest this is no customisation or feature request. You just removed something that once was "as it is". There were the distance shown for each member at the search results. And the new ordering of ES2 finally supports sorting these results for last login so I would like to combine these two things, which is obviously not possible, because you removed the distance shown. It just feels wrong requesting a feature that you have removed for no reason. I do not want to exclude the possibility that I just make something wrong but I want to achieve a distance search with last login ordering and distance shown. So the features that were there plus the feature that is there.


The search when clicking the age is a problem, because having an age clickable suggests the user that he can search for all members with that age. But in reality this is just a search for users with the same birthdate. I know the technical part in the background would be huge when asking for a search for age within this link and to prevent asking for such a customisation I try the easiest way by unlinking the age.

Also, let me discuss with Arlex about the hacks which he provided tomorrow as today is a public holiday here.

I am in no rush. I rarely add a priority to my threads because in most cases there is no deadline.

But to be honest this is no customisation or feature request. You just removed something that once was "as it is". There were the distance shown for each member at the search results. And the new ordering of ES2 finally supports sorting these results for last login so I would like to combine these two things, which is obviously not possible, because you removed the distance shown

What you are saying here has nothing to do with https://stackideas.com/forums/make-search-results-for-people-last-login-sort-option-to-default ? I am very lost here to be honest because based on the other thread, you were requesting for something that isn't in the core?

Nevertheless, I will check with Arlex again tomorrow.

Indeed this is confusing. Totally me working on too many things at once. My apologize, I will try to take tomorrow some free time to take a more clear look at it.

Thanks, please let me know on this but I will also check with Arlex again tomorrow regarding the other thread.

To prevent this getting even more confusing, I will create a new thread for each problem. Thank you very much for your understanding and your help.

Thanks for understand Sabih.

As a gentle reminder, kindly start a new thread if you have any other issue in the future so it will be easier for us to manage your inquiry. I will lock and mark this thread as resolved.