I am trying to set up the user relationship module so it behaves like facebook. Eg.
If I select that i am the child of a user then the user will automatically be given the relationship of parent to me.
I made 2 relationships "Child" and "Parent". For the child I selected a one way relationship and implied a reverse relation to parent. For the parent I selected a one way relationship and implied a reverse relation to child. This is how the module is supposed to work right?
All the log says is "u_relationship" and then a date but other than that it's blank.
Comments
Comment #1
attheshow commentedI'm getting the same result. Everything works fine for two way relationships, but if you make a one way relationship with an implicated relationship, you get a blank page in Firefox.
Comment #2
ccdoss commentedWas this ever answered? I'm trying to create a writer/reader relationship. I've created one-way relationship of writer, and selected that this implied the reverse relationship of reader. When UserA selects to have a writer relationship with UserB, UserB should show up in UserA's writers list, while UserA should show up in UserB's readers list. However, when I check the relationship tab, it states that UserA is a writer and reader of UserB. Is there a fix coming?
Comment #3
alex.k commentedYes, will address it. Are you experiencing it in 5.x, as well as the original poster's 6.x.
Comment #4
ChadH-1 commentedAny update on this issue? I'm using UR 6.x-1.0-beta9 and have the following relations setup:
When I request a parent or child relationship I get a "Fatal error: Maximum execution time of 30 seconds exceeded in /drupal-6.6/includes/database.mysqli.inc on line 100" or "Fatal error: Maximum execution time of 30 seconds exceeded in /drupal-6.6/includes/database.mysql-common.inc on line 42".
If I change the relations setup to:
Then I can create parent and child relationships just fine and the parent relationship automatically creates the child relationship as it is supposed to. However, the child relationship does not automatically create the parent relationship (which is how this setup is supposed to work I think).
Thanks,
ChadH
I have the following UR modules enabled:
UR-API
UR-Blocks
UR-Elaborations
UR-Implications
UR-Mailer
UR-Node Access
UR-UI
UR-Views
Comment #5
alex.k commentedThanks for reports, it's an infinite loop by the look of it, when A implies B, and B implies A. Will check it out.
Comment #6
alex.k commentedCorrected and committed. Also in parallel fixed a bug #358669: Cannot use multi-valued parameters in user_relationships_load().
Behavior has changed a little, hope for the better. If a relationship does not require approval, then its implications are created instantly. If it requires approval, then implications module will wait until it is approved. At that point all implied relationships will be created, pre-approved (which may fire off additional implications, and so on..)
If pending relationship is rejected, then its implied relationships are not touched, since they were not created in the first place.
Code-wise action happens now at a different stage. Whereas 'presave' was used before, now implications will be checked after the relationship is already saved. This is much easier, as during presave database has not been changed yet, so we have to guess what relationship is about to be created.