Timeline for How can I combine the fields of two field collections in my theme?
Current License: CC BY-SA 3.0
20 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 15, 2020 at 9:13 | history | edited | CommunityBot |
Commonmark migration
|
|
| Feb 4, 2016 at 12:21 | comment | added | No Sssweat | @ultrabob yea to 2 fields for each role. One for staff users and the other for non-users. | |
| Feb 4, 2016 at 12:18 | comment | added | UltraBob | That will still end up with 2 fields per role on the entry form right? The way it exists now is handy, and allows for extensibility. | |
| Feb 4, 2016 at 12:15 | comment | added | No Sssweat | then I guess it's best to go with my 2nd comment approach. | |
| Feb 4, 2016 at 11:53 | comment | added | UltraBob | There are thousands of entries, and it won't be me entering the publication data going forward so I don't think I want staff members creating users all the time when they add their publications. I also don't really think I want 10 fields to assign people for 5 roles. So far @NoSssweat, you and migrate are the good things about Drupal, but In this case I don't think this solution works for me. It is a lot slicker to have two unlimited entry field collections to handle it all. The interface I'm migrating from had one clunky field to handle it all, but the two field solution is easier to use. | |
| Feb 4, 2016 at 10:57 | comment | added | No Sssweat | or the Fields Permission module to hide or show fields for their user page.. | |
| Feb 4, 2016 at 10:56 | comment | added | No Sssweat | You could then use the Profile2 module to create separate unique profiles for them. | |
| Feb 4, 2016 at 10:53 | comment | added | No Sssweat |
@UltraBob another approach is that you can create dummy user accounts for non-staff members. Perhaps you can create an non-staff role give them a non-staff role. You can add users at /admin/people/users (I hope this link is correct, just going off memory here)
|
|
| Feb 4, 2016 at 10:50 | history | edited | No Sssweat | CC BY-SA 3.0 |
added 36 characters in body
|
| Feb 4, 2016 at 10:50 | comment | added | UltraBob | In actuality there are 5 or 6 roles, not just the 2. I need to think about whether that will make a good entry experience, and whether I can make the migration work that way. I do like the simplicity of the approach on the output side. One other downside to this approach is that I was intending to add an organization field for the other users collection to allow the specification of affiliation for non-staff contributors. | |
| Feb 4, 2016 at 10:49 | comment | added | No Sssweat | rewrite results example drupal.stackexchange.com/questions/188892/… | |
| Feb 4, 2016 at 10:46 | comment | added | No Sssweat |
right, you just create a text field for those non users. (ex: lets call them Editors Text) Add the field to your view. Click hide from display. Make sure this field is above the entity reference field. Then click on the Editors entity ref field and rewrite the results. Use the replacement patters. [field_editors] <span class="test">[editors_text]<span> then with css you can add a coma at the beginign of the editors_text list.
|
|
| Feb 4, 2016 at 10:33 | comment | added | UltraBob | I think you are missing that I need both users and non-users to be able to be assigned to each role. | |
| Feb 4, 2016 at 10:26 | history | edited | No Sssweat | CC BY-SA 3.0 |
added 1 character in body
|
| Feb 4, 2016 at 10:19 | history | edited | No Sssweat | CC BY-SA 3.0 |
added 261 characters in body
|
| Feb 4, 2016 at 10:14 | history | edited | No Sssweat | CC BY-SA 3.0 |
added 261 characters in body
|
| Feb 4, 2016 at 10:08 | history | edited | No Sssweat | CC BY-SA 3.0 |
added 646 characters in body
|
| Feb 4, 2016 at 10:01 | history | edited | No Sssweat | CC BY-SA 3.0 |
added 646 characters in body
|
| Feb 4, 2016 at 9:56 | history | edited | No Sssweat | CC BY-SA 3.0 |
added 646 characters in body
|
| Feb 4, 2016 at 9:42 | history | answered | No Sssweat | CC BY-SA 3.0 |