404 File not found when I try to sort on a column

Tomodea,
please check your wp settings page (not plugin settings) Check that the wp home page and the wp page have the proper urls in them.
eg:
wp: https://friendsofchurchillisland.org.au/wp/
and then what should home be:?

I don’t think the wp in subdirectory is what it is. I work with wp relocated all over the place so I can run multiple test systems off the one set of code. eg: in the demo system wp is down at
https://directories.wpusersplugin.com/wpe/
but it looks to the user like its at https://directories.wpusersplugin.com

Plugin uses wp functions to get what wp thinks the current url is.

Alternatively you may have something interfering. Try usual debugging https://webdesign.anmari.com/2932/debugging-a-possible-clash-between-plugins-andor-a-theme/

anmari,

Thank you for your suggestions.

I’ve checked the WordPress Address (URL) and the Site Address (URL).
The WordPress Address is: https://friendsofchurchillisland.org.au/wp
The Site Address is: https://friendsofchurchillisland.org.au/wp

I tried setting the Site Address to be: https://friendsofchurchillisland.org.au

However, it made no difference to the way the amr users plugin behaves. When I click on the Name column, the URL that is generated is still https://friendsofchurchillisland.org.au/my-dashboard/list-of-web-site-users/?sort=display_name&dir=SORT_ASC

On the other hand, when I click on a username (which has an “edit user” setting), the correct URL is used: https://friendsofchurchillisland.org.au/wp/wp-admin/user-edit.php?user_id=3

Please note that my current WordPress site is always accessed using the URL that includes the WordPress directory name, i.e. https://friendsofchurchillisland.org.au/wp This is because the WordPress site is still in test mode and is running alongside the current site which is accessed using only the domain name, i.e. https://friendsofchurchillisland.org.au

Perhaps everything will work as expected when I change the .htaccess to include a rewrite rule that causes references to https://friendsofchurchillisland.org.au to be rewritten as https://friendsofchurchillisland.org.au/wp ?

Thanks, Tom O’Dea
Melbourne, Australia

Tom,

As I said It works fine on all my sites, so something must be interfering on yours. PLugin uses remove_query_arg() which returns the current URL by default. Somehow that is not being correctly returned – maybe another plugin or maybe a permalinks thing. (have you refreshed those?)

How does it behave in admin side ?
If fine there, then something is interfering on front end and stripping the /wp/ part of the url OR somehow messing with the urls.

Did you do the normal debugging? https://webdesign.anmari.com/2932/debugging-a-possible-clash-between-plugins-andor-a-theme/?
ie: wp default theme and ALL other plugins off. Refresh page to make sure there is no cacheing etc of any kind going on.

I’m afraid I cannot help further if I cannot replicate the problem as it appears to be unique to your setup.

By way, page doesn’t look good in firefox on windows – has what looks like full menu in sidebar first, and then table below

View post on imgur.com

anmari,

Thanks for the info. about the use of remove_query_arg.

I looked at where this was being used and found it in 2 places in the include file ameta-includes.php.

The first is in the amr_adjust_query_args function:
$base = remove_query_arg (array('refresh','listpage'));

The second is is in the ausers_form_start function:

$base = remove_query_arg(array(

			'refresh', 

			'listpage', 

			'rows_per_page',

			'filter',

			'su', 

			'fieldvaluefilter',

			'doing_wp_cron',

			'index'));

I ran some tests with these 2 statements commented out and it now works for me!

I’m not seeing any obvious downside in not having these statements executed.

Thanks, Tom

The downside is that
1) those queryargs will not be removed if they exist in the current irk (eg if someone has just done a filter or a search or… Etc). They will be included in the url and keep bring added to the url and the plugin will use them

2) secondly you are modifying core plugin code. These mods will be overwritten in the next update. There is an update to be done soon.

So something is making remove_query_arg return something other than the current url (which is what it is supposed to do)

Have u 1) refreshed permalinks yet and
2) seen what happens when in std theme and no other plugins – this is a temporary thing -a debug technique – I’m not suggesting it stay like that – it is really the only way to find out what is interfering. If something is doing doing something odd it may also impact you in other ways. Best to know sooner rather than later.

The downside is that
1) those queryargs will not be removed if they exist in the current irk (eg if someone has just done a filter or a search or… Etc). They will be included in the url and keep bring added to the url and the plugin will use them

2) secondly you are modifying core plugin code. These mods will be overwritten in the next update. There is an update to be done soon.

So something is making remove_query_arg return something other than the current url (which is what it is supposed to do)

Have u 1) refreshed permalinks yet and
2) seen what happens when in std theme and no other plugins – this is a temporary thing -a debug technique – I’m not suggesting it stay like that – it is really the only way to find out what is interfering. If something is doing doing something odd it may also impact you in other ways. Best to know sooner rather than later.

Wow double post – smartphone glitch
Actually the remove_query_arg returns or is supposed to return the $_SERVER. Request_uri

Which on my system is /wp/….

If you var_dump ($_SERVER) before one of those calls and see what it has that should shed some light . Ie it’s your server setup somehow or something affecting the remove_query_arg

anmari,

I’ve done a var_dump ($_SERVER) as per your suggestion and the result is quite interesting. I’m not going to include the complete output because it is rather long and it contains cookies, etc.

The most interesting part is the REQUEST_URI which is showing as “/my-dashboard/list-of-web-site-users/” whereas we would have expected it to be “/wp/my-dashboard/list-of-web-site-users/”.

However, the REDIRECT_URL is showing as “/wp/my-dashboard/list-of-web-site-users/”.

I’m beginning to think that it might have something to do with my .htaccess. Once we’ve switched across to the new WordPress site, the .htaccess will be modified so that references to friendsofchurchillisland.org.au will be redirected to riendsofchurchillisland.org.au/wp.

I will leave it as is for the present and will uncomment the 2 statements when we make the switch.

Thanks, Tom