Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
It would be nice thing to have the whole idea of multiple relationships explained together with example usecases.
Would multiple types of images in single type of gallery work ?
Would multiple types of galleries with single type of image work ?
Or is it only for gallery_A <-> image_A and gallery_B <-> image_B ?
It's not clear.
Comments
Comment #1
crea CreditAttribution: crea commentedCurrently one can't reuse content types in more than one relationships. I suppose it was design decision.
Having content type mixing between relationships would help to implement "default galleries". I would just create additional relationship "default gallery" with additional "default gallery" content type. Access for "default gallery" nodes would be controlled by simple Drupal content-type-related permissions.
Comment #2
justintime CreditAttribution: justintime commentedIt was a design decision made early on in the 2.0 branch that just came over in the 3.0 branch - #1130450: Image type is already part of a relationship.
So, to answer your question, it's
gallery_A <-> image_A and gallery_B <-> image_B
It will be one of the first things to change if/when the D7 branch is created.
Comment #3
crea CreditAttribution: crea commentedI think I got the general idea..
Comment #4
crea CreditAttribution: crea commentedCan you add something like this to the documentation ?
"Currently Node Gallery relationships are isolated from each other: every image type should have own gallery type. It was design decision made in the previous branch of the module.
It may be changed in future branches."
Comment #5
justintime CreditAttribution: justintime commentedAdded:
Content types belong to one Node Gallery relationship exclusively -- every image type has exactly one gallery type
and vice-versa. This dependency may be removed in later development, see http://drupal.org/node/1130450.
to relationship-settings.html in advanced help. Also marked the issue referenced above as a postponed feature request. Committed to 6.x-3.x-dev.
Comment #6.0
(not verified) CreditAttribution: commentedtypo fix