Support Forum

Admin User sorting lost on page 2

JW Joshua Walton
Joshua Walton
Member
Member since May 2016
18 posts
Jun 30, 2016 · 12:11 pm · Edited

Hello and thank you for an awesome plugin!

We are interested in tracking our most active users. Since there isn’t really any reporting feature (that I have found) we are instead just looking a couple times a week at the Users from the Admin side

Admin Menu > Forum > Users

Then we will sort by whatever data we are tracking, such as the ‘Last Visit’ column or the ‘Posts’ (post count) column. However, once we go to page 2, the column sorting (ordering) resets.

iIn the address bar, It looks like the parameters are not being passed. Can this be fixed? Is there a hotfix you can provide me to update the right file via FTP?

If you have any questions or I can help in any way, please let me know. Thanks for your help!

4 Answers

New Answer
YS Yellow Swordfish
Yellow Swordfish
Member
Member since Nov 2008
16,437 posts
Jun 30, 2016 · 12:33 pm

Gosh that really is broken isn’t it? Our apologies.

This was only introduced in the last update and the irony here is that we moved from using our own code to utilising the core WordPress listing API…

I will open a bug report straightaway and we will look into it. If it is an easy fix then yes – we can post the code fix in the topic here…

MP Mr Papa
Mr Papa
Member
Member since Dec 2006
19,448 posts
Jun 30, 2016 · 10:55 pm

in simple-press/admin/panel-users/forms/spa-users-members-form.php, trying commenting out these lines of code around line 157

                        # set up some globals to handle our bastardized urls
                        $bits = parse_url(SFADMINUSER);
                        $_SERVER['REQUEST_URI'] = $bits['path'].'?'.$bits['query'];
JW Joshua Walton
Joshua Walton
Member
Member since May 2016
18 posts
Jul 6, 2016 · 12:07 pm

Thank you – that fix worked! We are using Version 5.6.7

YS Yellow Swordfish
Yellow Swordfish
Member
Member since Nov 2008
16,437 posts
Jul 6, 2016 · 3:06 pm

And I can confirm that it is also fixed in the forthcoming 5.5.8 update. Thanks for the original information.