Bug #23173 See Comments

Deleting custom member fields generates error

Version: 3.5.10 Reporter: Ottenhoff Consulting

When deleting a custom member field, an error is generated. The field does get deleted. However, when deleting multiple custom member fields at the same time, the same error is generated, but only ONE of the fields is actually deleted. So, this. error requires that custom member fields be deleted 1-at-a-time.

Exception Caught

SQLSTATE[42000]: Syntax error or access violation: 1091 Can’t DROP ‘m_field_ft_14’; check that column/key exists: ALTER TABLE exp_member_data DROP m_field_ft_14


Stack Trace: show

  • I’m not able to replicate, and each member field should have an m_field_id_x and corresponding m_field_ft_x field in exp_member_data.

    If you check the table directly- is it only the one field that seems to have lost its corresponding ‘ft’? Any chance some of the data were imported or added via a third party addon that didn’t create the ft field?

    The problem isn’t the query so much as the database, those ‘ft’ columns need to exist.

    What might be a bug is how they ended up missing. Any ideas how that table may have gotten off?

    Robin Sowell
    14th July, 2017 at 6:28pm
  • Hi Robin,

    I’ve confirmed the corresponding fields exist. There are only 8 custom member fields, and there is a one-to-one match.

    I have imported just over 16,000 member accounts. All member-related functionality works throughout the site. Just having this glitch.

    Is it possible there could be some data in the member fields that could cause the issue? Like a stray quote, or something?

    Ottenhoff Consulting
    17th July, 2017 at 10:32am
  • Hrm, that shouldn’t be it. If you just go create a new field and then delete it- same problem?

    Robin Sowell
    17th July, 2017 at 10:43am
  • Hm.. That’s working fine. So, it must be something with the data that was imported? Honestly, it’s not that big of a deal.

    Ottenhoff Consulting
    17th July, 2017 at 10:56am
  • It is puzzling, though! I’d try adding a field again, maybe put some content in it for one entry. Then just skimming to see if you can spot anywhere in any of the member tables there’s a discrepancy between the fields.

    But agreed, there’s something different about the imported data that’s throwing it off.

    Robin Sowell
    17th July, 2017 at 11:45am

You must be signed in to comment on a bug report.

ExpressionEngine News

#eecms, #events, #releases