last version changed meta field handling (bug?)

  • Resolved colins

    (@colins)


    4 years, 8 months ago

    I have a meta field in my user records called “share_email”. In the CVS file for the import, this column is either 1 or 0, and previously that was properly importing as either
    array (
    0 => ‘1’,
    )
    or
    array (
    0 => ‘0’,
    )
    respectively. As of a recent version (probably 1.7.0) of the plugin, for the 0 value, this either does not create the meta field at all, or if I go and uncheck “Don’t add Empty value fields in database” then the meta field is created for 0, but as
    array (
    0 => ”,
    )

    So for some reason, the new version is treating a 0 in the CSV file as NULL, i.e. there is no value.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter colins

    (@colins)

    I rolled back to version 1.6.5 and it behaves exactly the same. I don’t know what is going on, the import worked fine for me a week ago, in the manner described above, and now it doesn’t any longer. Last week I never touched the “Don’t add Empty value fields in database” flag, and the field was always created even for a 0 value, now it is only created (but empty) if I uncheck that option.

    Is it possible that something else has changed w/respect to the default value of this meta field in the new or updated user record, before your plugin ever goes to try to set it? This is an ACF field, if it matters.

    Plugin Author vjinfotech

    (@vjinfotech)

    Hi

    Thank you for getting in touch!!

    please mail me on on [email protected] with your issue with details. i will provide solution in minimum time.

    thanks and have a nice day

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘last version changed meta field handling (bug?)’ is closed to new replies.