Creates new columns in options table even if field already exists in usermeta

Good morning Robert,

I go inline:

The plugin does not check to see if a metadata field exists already. On line 132 in the current version (1.4.2), it simply adds to the options table any columns it found in the CSV that do not match a string of stock WP field names (matching case exactly).

I have added fields to the profile using the filter hook user_contactmethods, which puts the metadata into the usermeta table.

Yes, this is the current functionality in the current version.

Use this filter could be a good idea, we can do it if you support this new functionality.

All of the extra metadata in the CSV was put into the options table instead if it was not a stock field. (Since my email field was labeled “email” instead of “Email”, the plugin also created an extra column for “email”, though it put the required email data into both the usermeta field and a new field in the options table, within the acui_columns array.

Please make it clear that the column names are case sensitive and must exactly match your column names, and that this plugin will not update existing added metadata, but will only add metadata fields.

I will add it to the new version that will appear today.

Your plugin is okay if you have not already added the metadata fields, or if you are not updating metadata (but then there are other CSV importers for that.) I would strongly suggest storing metadata in the usermeta table, and not the options table. I unfortunately cannot suggest the specific code to handle checking for existing metadata and populating it from the CSV.

The data is stored in metadata table, but yes, this is also indexed in the options table in order to have a reference.

How would you save this reference?

As nobody have answered again, I close this thread now.