New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggest fields with create:true not saving/displaying custom added values #1722

Closed
beckysoll opened this Issue Jan 15, 2018 · 0 comments

Comments

Projects
None yet
2 participants
@beckysoll

beckysoll commented Jan 15, 2018

Expected behaviour

When saving data with a suggest field, custom added values and values added from option list should save in the yaml, and display in the field when re-editing the entry/page

Actual behaviour

I've tested this with a max_items of 1, and no max_items, and i've tested it with no pre-built options, and with pre-built options, behavior remains the same under any of these situations.

If I have pre-defined values for the field available and select one or multiples of them, everything behaves as expected. If I manually add an option, and do "save and continue", everything appears to behave as expected. But if i exit the entry I had been editing, and then go back into it, The manually added value is not displayed. At this point, it remains in the entry's yaml. If I don't edit that field at all, edit other fields and save the entry, the data stays where it is (in the yaml, but continues to not display in the field when editing). If I add or edit any value in that field (predefined or manually added) and save the entry, the original manually added value disappears from the yaml.

Steps to reproduce

  1. edit value of suggest field by adding a custom value
  2. save and close the entry/page
  3. reopen the entry/page

Server Details

Operating System: macOS High Sierra 10.13.2 (17C88)

Web Server: apache (via mamp pro)

PHP Version: 7.1.8

Statamic Version: 2.8.0

Updated from an older Statamic or fresh install: updated

List of installed addons: none

@jackmcdade jackmcdade added the bug label May 1, 2018

@jackmcdade jackmcdade self-assigned this Jun 4, 2018

@jackmcdade jackmcdade closed this Jun 7, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment