404 page not found when Export

Hi,
I just ran through all the permutations on 4.5-beta2-36888 on php 7 and all is fine on my test systems

It’s doing a POST submit to the page and as you know you should see a link to the csv file (if it’s a public list)

Possibly something is messing with form submit?
Or maybe folder permissions have changed? It needs to write file to uploads folder:
…wp-content/uploads/users_csv/user_list_xxxxx_filter_1.csv

If not permissions, then maybe need to do the old debug
https://webdesign.anmari.com/2932/debugging-a-possible-clash-between-plugins-andor-a-theme/

Thanks Anmari, I will go through your suggestions and post back here with what I find.

Some exports are working fine but it seems like anytime the user list has more than about 1100 entries I get a 404 page. Is there any way to see if it is hitting max memory or other resource limit?

This is the url that is generated that is returning the 404:

https://www.userdomain.com.au/wp-admin/users.php?page=ameta-list.php%3Fulist%3D1&csv=1&_wpnonce=b6fc1d93b4

This is the URL that is in the browser when the query runs and works:

https://www.userdomain.com.au/wp-admin/users.php?page=ameta-list.php%3Fulist%3D1

It does sound like it is hitting some kind of limit.
Check your system log files or put your site temporarily into WP DEBUG and then run the export and see what messages u get and if any relate to this.

Plugin will also tell you what your memory limit is if you go to users lists > about > your user db

It might also be a timeout error if it’s taking too long, but that is not really that many. I’ve tested before with up to 10 000 but it might depend on your server, how big your list is etc.

Gets stranger and stranger. I increased WP_MEMORY_LIMIT up quite high, much higher then is being used to execute the querys – 385Mb. Still returns 404 but only when I run specific combination of filters.

Also, turned on WP_DEBUG and only one line appears:

Notice: Constant AMR_USERS_STORE_URL already defined in /home/pesacoma/public_html/wp-content/plugins/amr-users/admin/updates-page.php on line 5

I am beginning to suspect it may actually be a corrupt user record in the database or something. Is there a way to find out if there is a corrupted user record? Or are there chatacters that could stored inside a user record that could cause the result Im getting?

Re the notice that shouldn’t affect it, but also should not be happening. Do you have a copy of the plugin also active ? Or perhaps an old version of an add-on ?

Maybe it’s not memory then. (a memory plugin like debug bar would help you see how much memory)

So if you know how to create the problem, then focus on that aspect and start isolating the problem further.

Please tell me you have those filters set up as ‘column value’ filters – the default option.

What is special / different about those filters / fields / data ?
Is it only the combination? Ie are they fine by themselves ? – eg: if you filter by one value at a time?

I am getting a similar result when trying to export to CSV. In my case, it’s a 403 error. Exporting to .txt works fine.

Error message is:
403 Forbidden
A potentially unsafe operation has been detected in your request to this site.

URL is:
https://www.mydomain.com/wp-admin/users.php?page=ameta-list.php%3Fulist%3D1&csv=1&_wpnonce=1290196b5a

Hi affinitymc,
This does sound like a permissions type problem. I’m not seeing these issues on my installs.

There isn’t much difference between .csv and .txt exports – uses the same code. .txt passes an extra parameter.

Googling wordpress 403 returns a lot of advice to check your .htaccess (plugin does not touch that)
https://www.google.com.au/search?hl=en&q=wordpress+403+Forbidden%22

Googling the full message points to wordfence?
https://www.google.com.au/search?hl=en&q=wordpress+403+Forbidden+A+potentially+unsafe+operation+has+been+detected+in+your+request+to+this+site#hl=en&q=wordpress+”403+Forbidden+A+potentially+unsafe+operation+has+been+detected+in+your+request+to+this+site

If using wordfence, check the posts (there are only a handful) and see if anything rings a bell.