Thomas S

Hi, and thanks for this problem report, and my apologies for the issue. Out-of-Memory (OOM) errors _tend_ to come as the result of an action or filter looping unexpectedly. Not sure what or why would be causing it right now, but to troubleshoot I would need to know more about your setup.

Things like the other active plugins / add-ons you’re using, the theme/child theme.

Am not in front of my computer right now, so can’t dig into the code atm, but will take a look asap.

If you’re not using the import plugin actively, I’d suggest disabling it and the utilities plugin for now.

It provides shared functionality across my plugins, and is required yes.

I’m sure you’re avoiding quote (single, double, back-tick, etc), possibly wildcard (*, %) and non ASCII characters in the passwords. Would also be cautious with long strings, but other than that there shouldn’t be anything I can think of, off the top of my head. (Been a little while since I wrote that code, and not in front of a computer right now to check, sorry).

Hi,

Thank you for using my plugin, and for reaching out for help with the problem you’re experiencing.

I’m unable to access the sheet you linked to due to the access control settings, which is very reasonable. Would you mind copying a couple of lines of the sheet into a different sheet and anonymize the data, so I can try or assess what the problem might be?

Hi,

I’m not sure that I understand the problem you’re describing? Where are you not seeing the user?

In the WP Users table, or some other location in the database? Perhaps in WordPress itself?

Are you expecting an imported user to appear somewhere specific?

AFIK, multisite WordPress uses a single unified database table for all registered users. There may be something specific that needs to happen for a user to become available/visible on a specific sub-site.

What that is, I currently do not know.

A (very) quick Google search doesn’t uncover anything different between a single-site WordPress user and a multi-site WordPress user. I.e. that there’s more/different information in the user record part of the database for the two WordPress configurations.

Me not finding anything right now doesn’t mean much. For instance, I don’t know if there are specific roles that need to be assigned to a user. And I would not know what those might be, off the top of my head.

Unfortunately I have not tested this plugin for multi-site configurations either and it’s on my longer term “ToDo” list (adding multi-site to automated testing for the plugin).

• This reply was modified 2 years, 8 months ago by Thomas S. Reason: Fix an obvious typo

Hi again.

It took a little longer than I’d hoped, but the issue you reported has been fixed along with a few other issues including – I believe – the problem some sites may have had with exporting to CSV.

I also added the option of setting your own filename when saving the .csv export.

Hi, and thank you for downloading and using my plugin!

I honestly don’t recall why I chose the format I chose (may actually have been for export/import reasons, but ..?)

I’m currently not in front of a computer and won’t be for the rest of the year, but can take a look at what it will take to implement your request after the 4th of January, 2022.

Hopefully that’s going to be ok..?

Sorry, didn’t see this until now! (Gotta go check my spam filters. They may be a tad too strict!!)

Anyway, yes it’s definitely due to this plugin, sorry!

I have 2 editions of the plugin and the 2nd edition is available from my private server. That means it uses a different setup for the 2nd edition one-click update.

This functionality was supposed to be removed as the plugin was getting pushed to www.ads-software.com, but that didn’t happen so I have now deactivated the functionality altogether.

You will need to upgrade to the current version (v8.4) and the silly error message should stop.

My apologies for this erroneous error message.

• This reply was modified 3 years, 8 months ago by Thomas S.

*sigh*…

I’ve tested 6.3 on multiple different setups now and I _believe_ 6.3 is a “non-fatal-error” version of this plugin.. (Sorry!!!)

Sorry, this should have been fixed now.

Closing w/the release of v5.10 (should be in the repo now)

Sorry about this!

Should be fixed in v5.10 (just released).

My apologies for the late reply as well. Life is a little hectic at my day job right now.

Sorry about that!

There was a bug which has since been fixed. The current release should be a-ok.

Thanks for the report @beatty67, and thanks for the workaround @elzix!

Bug fix coming in the (completely rewritten) plugin that I’m (still) working on.

Depends on what you mean by “group” in this context.

If you mean “WordPress User Role” then the answer is “yes”