When I export files, they come up empty.

Which version are you using?

Thanks for your reply. The version is 1.27.13.

Can you make a test with the previous version?

You can do it using this plugin: https://es.www.ads-software.com/plugins/wp-rollback/

In the plugin’s list you have to choose which version you want to downgrade and to which version.

When I downgraded from 1.27.13 to 1.27.12 using the method you taught me, I was able to export without any problems! I’m happy to learn about useful plugins too.

Thank you for your quick response – it was very helpful! This is my favorite plugin.

Thank you so much!

Thanks for your words. If you like this plugin, please give us a good review: https://www.ads-software.com/support/plugin/import-users-from-csv-with-meta/reviews/#new-post

And it is very strange your problem, I need to find out what you have in common that the rest do not have.

What operating system does your hosting run on? Your short term problem is fixed but you should keep upgrading in the future and for sure.

If you want to help in the development of this plugin, so that it can continue to exist and you can continue to receive support and improvements, you can leave us a good rating: https://www.ads-software.com/support/plugin/import-users-from-csv-with-meta/reviews/#new-post

This problem that you have and I can not reproduce in fact of all the thousands of users of the plugin are only 3 cases that suffer it, I would like to know what may be happening in your installations.

Are you on a Windows hosting maybe instead of a Linux one?

I wrote a review. Thank you.

I don’t fully understand what hosting is, but if you could tell me where I can check this information, I will look into it.

I have sites on three servers, and even within the same server, some sites experienced issues while others didn’t. It doesn’t seem to be a server-related problem.

After testing several other sites, I found that some sites had issues while others didn’t. This was the result even with WordPress and other plugins being up to date.

Sorry but I have just tested in differente servers, in local, with different configurations and it always work.

I need to know what’s happening to fix asap.

Version 1.27.13 is a version that introduces a major security enhancement. It appears that the applied fix fails in some environments. I don’t know why because in 10 different installations: some new, some old, in different systems… it always works for me.

I need someone with the problem to prepare me a new test installation, without any personal data and send me accesses in a safe way to be able to solve the problem.

I am sorry but I can not reproduce the problem and without seeing where the origin is I can not give you a solution.

I hope someone can send me that access soon to be able to fix it ASAP.

Good news. I have been able to find a server in which this version fails.

I am working hard on it to solve it asap.

I just finished fixing the problem. It only occurred in exports of a certain size, when I saw the source of the error I was able to fix it.

I thank you all for your patience.

And I would ask you, to those who have not done it, to leave a positive review of the plugin.

I dedicate many hours of my work and my family to this plugin for free and because of problems like this I have even received a one star rating that does a lot of damage to this project and to my desire to continue dedicating part of my time to this.

I tried the new version 1.27.14 and was able to export without any issues!
Applause for the quick fix!
Great work!
Thank you!

@carazo Your account is now flagged for moderation.

I need someone with the problem to prepare me a new test installation, without any personal data and send me accesses in a safe way to be able to solve the problem.

You should not have made that ask, and if you repeat that then your plugin may be removed from this site. It is that serious.

You need to reply here that you understand and will not repeat that again.

While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.

If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.

Thankfully are other ways to get information you need:

• Ask the user to install the Health Check plugin and get the data that way.
• Ask for a link to the https://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
• Ask the user to create and post a link to their phpinfo(); output.
• Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
• Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site vistors).
• Ask the user for the step-by-step directions on how they can reproduce the problem.

You get the idea.

We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.

When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.

@moderator,

Sorry!!! I was really desperate because I didn’t understand what was going on and the truth is that doing this in a public forum (because they are not users of any premium support and I had no other way to contact them privately and securely) was not a good idea.

Thank you very much for your recommendations and it will never happen again. I understand now perfectly the reason and not even in a case of extreme urgency I will never do something similar again.

I have understood and I apologize for the effort of having to write this post that you send me.

Thank you for the work you do for the community and for allowing such a massive support forum to work in such a safe and correct way.