Possible bug with backend dropdown defaulting to 1st option

  • Sjourney

    (@sjourney)


    9 years, 8 months ago

    Hi @xnau
    So I’m not able to reproduce this bug as of yet.
    Background:
    I have a DB setup with one of the Fields in the form being a dropdown of about 6 items.
    I went back in to the database to edit several records. I did not change the dropdown field at all. I saved my changes. Later it was brought to my attention that the same field had reverted to another value. Actually all the records that I edited had that field reverted to the same value. The value happens to be the default 1st item of the dropdown list.

    Have you encountered this before?

    https://wordpress.org/plugins/participants-database/

Viewing 1 replies (of 1 total)
  • Plugin Author xnau webdesign

    (@xnau)

    9 years, 8 months ago

    If you are using a dropdown field, and the value in the record does not match any of the defined values, it will go to the default. If that record is then saved, the original value will be lost. This typically happens when the field values are changed. Of course, you said you didn’t do that, but the symptoms match that situation for whatever reason.

    If you can, you should check the records in the database (not using the plugin, using a database tool like phpMyAdmin) to see what the value of that field is.

    Another way around this is to use a “dropdown/other” type, which will show the value as an other value if it does not match any of the defined values.

Viewing 1 replies (of 1 total)
  • The topic ‘Possible bug with backend dropdown defaulting to 1st option’ is closed to new replies.