Skip to content
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

Dropdown manual list seperator #29

Closed
greenwellness opened this issue Jun 11, 2014 · 2 comments
Closed

Dropdown manual list seperator #29

greenwellness opened this issue Jun 11, 2014 · 2 comments
Assignees

Comments

@greenwellness
Copy link

Personally I feel using the pipe | operator to separate the list items a bit 'counter intuitive' since the textarea is so big, I've nearly every time used newlines on every first try, to remember it doesn't work that way. I don't know how many people submit lists of 50 or more items, but personally I think you might wanna abstract into a piece of dynamic db driven list if your static lists are becoming that long. So while pipe might be good (due to width) for text_fields_, they seem less appropriate to use inside a multirow/column text area unless frequently populated with a large amount of items.

@tzyganu
Copy link
Owner

tzyganu commented Jun 11, 2014

@greenwellness OK. You have a point with the pipe separator. I will turn that into new lines.
As for the db driven lists...you can always create a separate entity instead of a dropdown with a few values, and set that entity to be a parent for your main entity. The result will be the same. You will have a dropdown field with some values in both cases. The dropdown attribute type is there in case you want to add, like you suggested, a small list of possible values.

@tzyganu tzyganu self-assigned this Jun 11, 2014
@tzyganu
Copy link
Owner

tzyganu commented Jun 12, 2014

This should be fixed in version 1.9.1.2

@tzyganu tzyganu closed this as completed Jun 12, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant