CCK Field - Settings apply to all in this content type
| Project: | Relevant Content |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Jump to:
wow, cck implementation works beautifully! i created a simple group to house the field and it shows in nice little box below content and above comments
only request: as this works now - and perhaps this is not flexible - the fieldtype exists once and only once and in turn, like all cck fields, presents the 'global settings' options...
but i'd like to have two instances of this going on - one for rigid vocabularies generating 'similar content by type' (for example, all 'stories' are from a category like sports, business, arts, etc - a forced selection which in turn generates the related items)
...and i'd like to add another field that spans multiple content types using freetags - which is in fact shared already by multiple content types - but as things stand now, i can't select freetags because it will crowd the 'similar stories' cck item with other content type links - which i want to place separately, so that a user sees this:
story title
story body
etc
field: similar stories (cck fieldgroup: field_similarstuff)
field2: other stuff you may find interesting: (cck fieldgroup: across all tags multiple content types)
would this be possible? is it already and i'm just missing something obvious? i don't see the ability to add another relevantcontent field (more than once)
#1
as far as I'm aware you should be able to add more than one field of the same type with different settings.. I'll give this a go over the weekend. It's possible I didn't do the CCK implementation correctly...
Thanks for the kind words, much appreciated!!
#2
you're more than welcome - this is EXACTLY what i was looking for and it spared me the nonsense of a custom node.tpl for each content type or a hack to the original theme structure to move a 'block region' above comments to drop in related content!
also helps handle the custom block placement issue (as in, depending on terms chosen, a user may have to go back and specify when to display a block, particularly if free tagging is an enabled vocab for this module)
#3
I just tested this out. Using Devel I created 2 vocabs and about 100 nodes of Page and Story type across these nodes. I then added 2 fields to my 'Page' type. The first (field_rc_test) lists 5 'Stories' from my 2 vocabs. The other (field_rc_test2) lists 10 'Pages' from 2 vocabs. I set field_rc_test to display as Plain and field_rc_test2 to display as links; both for full node only.
In this test, teasers show nothing and full view shows two extra fields as configured above.
Have you tried adding two fields? I believe I am running the latest CCK dev release... I recall having minor issues while developing the CCK fields...
Regarding your 'global' comment... I'm not sure what you mean. I went to my Story type (from above example) and there was a new second option to add an existing field to the Story type from the fields I created on the Page type... Could you please elaborate on the 'global' idea?
#4
oh, i'll have to try to just add the field again to a content type for the second instance - thought that it was limited to one time (as in, certain cck prevents some fields from appearing in dropdown of existing fields if they've already been added)
global just means that part in configuration of the field where it says "these settings will apply to this field in any content type in which it is used" (usually appears on lower half of screen in field setup in content/manage fields)
#5
I'll take a look into that "global" thing... Do you have an example of a CCK Field which does this currently? I've never seen the option...