Solved K 1.7.2: Userlist columns not sortable

I'm seeing the same issue as D4Real - I have a total of three sites, that all use the same template, and for the most part use the same extensions.

The two sites that have been migrated to 2.5.1 exhibit this issue, but the one still on 1.7.5 does not.

The site on 1.7.5 has the most extensions out of all three installed - I'll see if I can figure out what may be causing the issue.

Thank you for your input to this topic. As I indicated in my previous response, we are aware (from what D4Real has written and from our own observations here at this website) this issue seems to occur in J! 1.5.25 and J! 2.5.1. It is interesting to note that you have not found this to be the case with J! 1.7.5. I will pass this information to the development team for their consideration and reply.

I did the following Test process:

1) Clean install of Joomla 1.7.5, Kunena 1.7.2, Akeeba Backup (latest version), and nothing else, using default templates.
2) Create 3 test users.
3) Verify sorting on User List in front end - it works without issue.
4) Update Joomla to 2.5.1 using Extension manager.
5) Verify sorting on User List in front end - it no longer works.

This is using all default templates, options, etc. The only add-on used other than Kunena is Akeeba Backup to make it easy to roll back to an earlier state if needed.

The same issue is happening for another Component, Bookmarks Reloaded. Here is their fix for their component - maybe it can help with Kunena:

www.viryasoftware.com/index/19-support/2...t-end-a-back-end#305

Any news on this? It's still happening in Joomla 2.5.2.

I reported that the development team admits that this problem arises from a defect in K 1.7.2.

K 1.7.2 is end-of-life for the K 1.7.x series (the team is not intending to release a "K 1.7.3" (unless there is something seriously wrong - for example, if there's a major security vulnerability discovered) and the project team is not expending effort to remedy this particular problem at this particular time. I understand that's not music to anyone's ears but these are the facts. If, however, there's a member of the community who has found a way to resolve this particular problem and who would like to share their solution, that would be good news, wouldn't it.

The focus of the development team is squarely on K 2.0. The issue has been resolved in K 2.0 but this version is a couple of months from a stable public release. We ask for your forbearance on these matters.