Resolved Can't import J5 users

Hello,

1) don't require password reset for existing super users.

With a rule and settings in template you can skip update of password field for super users. That can be done by running two imports. Both imports can use same import file and import template. The first import will skip all super users and update all other user types. That can be done using RO CSVI Skip rule to skip super user rows. Second import can skip all other user types other than super users and in this case you can set password field to skip template field so that is not updated on import.

2) don't create a user with no uid or username.

You can use RO CSVI Skip rule plugin to skip records with empty user id or username.

ok, I think we can close this one. There are 2 minor issues that would be nice to have addressed but its not critical.
1) don't require password reset for existing super users.
2) don't create a user with no uid or username.

Hi Bear,

I hadn't applied it to fields. I mistakenly thought that was automatic but things still don't look correct.

Whether things are automatic or not completely depends on your import file. If your import file can be imported as-is and you do not need any pre-processing of the data then you can set the template to use you column headers from the import file.

This is a canadian website so the dates need to display in canadian date format to the user.

All good but that is not something RO CSVI controls, that is what Joomla controls and is also based on the site settings and the user profile. The database is going to need the date in UTC format so it can display it in the correct timezone and correct format. This means the date must be in the format of Y-m-d H:i:s or in other words Year-Month-Day Hour:Minute:Seconds.

If I see it correctly, the user export comes out of another Joomla site correct? If so, you just need to export the date fields as-is. Do not make any changes to it and you can import it without modification. This goes for all date fields.

I also noticed that it has a date for the "send email" field which shouldn't be a date but a boolean yes/no.

That is a misconfiguration in the export file. The export file you created has no text enclosures set. This should be set to a double quote to ensure data is kept together.

Let me know if you are exporting from a Joomla site using RO CSVI because if so, we should look at your export template first.

I hadn't applied it to fields. I mistakenly thought that was automatic but things still don't look correct.
This is a canadian website so the dates need to display in canadian date format to the user.
The user is wanting to add/remove products via csv so I assume he's going to want to use canadian date format.
I noticed the time was reset to 00:00:00:00 on all dates. This is incorrect. instead of custom date should we use just date?
I don't understand the before/after option in the rule. I read the documentation and didn't see it mentioned.
I also noticed that it has a date for the "send email" field which shouldn't be a date but a boolean yes/no.
It's correct in the exported csv but when imported its changed to a date.

Hello,
Did you apply the rule on the date fields? Can you post the latest template XML to check? To get the template XML file from RO CSVI templates list page select the import template and click on Backup templates button. Post the downloaded XML file.

I created the rule for both export ( on old site ) and import ( on new site ) and it didn't change anything.

Hello,
Thank you for posting the requested files. I was able to see the issue with your import file.

1. You have date in format Monday, 20 October 2025 in import file but database supported format is Y-m-d H:i:s. So this needs to converted to database supported date format. To convert the date use RO CSVI Multireplace rule plugin and Custom date format operation.
2. Since you have comma in dates and they are not wrapped in text enclosures each value is considered to be a column and that is breaking the import. See attached screenshot for date fields. Once you change the date format as explained above this should also be solved.

Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in E:\Bearsampp-development\sandbox\www\new\plugins\csviaddon\users\com_users\model\import\user.php on line 399
{"process":false,"url":"administrator\/index.php?option=com_csvi&view=logdetails&run_id=9&return=aHR0cHM6Ly9uZXcubG9jYWwvYWRtaW5pc3RyYXRvci9pbmRleC5waHA\/b3B0aW9uPWNvbV9jc3ZpJnZpZXc9dGVtcGxhdGVz"}

That is not error but a warning. You can set Error reporting to Simple in Details tab in Import template and run the import.

As far as 500 error I am thinking once you correct import file that should also be solved. Try and let me know on how that goes.

due to the highly sensitive nature of the user information I'll have to email it to you.
here is the error that showed up after settting debug to maximum

Status error: 200

Status message: parsererror



Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in E:\Bearsampp-development\sandbox\www\new\plugins\csviaddon\users\com_users\model\import\user.php on line 399

{"process":false,"url":"administrator\/index.php?option=com_csvi&view=logdetails&run_id=9&return=aHR0cHM6Ly9uZXcubG9jYWwvYWRtaW5pc3RyYXRvci9pbmRleC5waHA\/b3B0aW9uPWNvbV9jc3ZpJnZpZXc9dGVtcGxhdGVz"}

Hello,
Please post import debug log and import file to check. To get the debug log read How to collect debug information? document.