Hi,

I am curious. Has anyone used this module with nodeprofile ? I have nodeprofile enabled and I do not see the link "Create a relationship with " when visiting a user's profile as another logged in user. I have all these permissions enabled for authenticated user :

can have relationship
maintain relationships
view user relationships

as well as :

access user profiles (from user module)

even the block for "Relationship Actions" that usually shows from the user profile page (when the sub-module for user relationship blocks and the block is enabled) is not visible.

It seems user relationships does not play well when nodeprofile is enabled.
I have another site where I am not using nodeprofile and I dont have any problems there.

Before I start to get my head into this further to figure it out I am wondering if anyone using nodeprofile with this module has already experienced this and if there is a workaround .. or am I doing something completely wrong here ? ( like I said I am able to get it to work on another site but not when using it with nodeprofile enabled).

Comments

alex.k’s picture

alex.k commented

It would be good to hear some users of nodeprofile + user_relationships chime in...

As far as the block, could you try this php snippet for block visibility:

if (arg(0) == 'node' && is_numeric(arg(1)) && !arg(2)) {
  $node = node_load(arg(1));
  return is_nodeprofile($node->type);
}
return FALSE;

it would show the block on nodeprofile nodes, perhaps it'll help.

jaydub’s picture

jaydub commented
Priority: Critical » Normal

not critical...UR doesn't claim to work with nodeprofile...

drupdrips’s picture

drupdrips commented

Thanks .. will try out the suggestion and update my findings soon.

drupdrips’s picture

drupdrips commented

Finally got time to get back to this again.

Alex's suggestion in #1 works. Thanks!!

drupdrips’s picture

drupdrips commented

I spoke too soon. Actually it is only working when I put the check on "Allow multiple relationships" with or without that block visibility code given in #1. When I turn off the "Allow multiple relationships" as I only want one type of relationship that is defined in the Types, the block for UR Actions does not show anymore, even if I have the block visibility code. Of course in the block visibility I have the option "Show if the php block returns TRUE" checked also.

drupdrips’s picture

drupdrips commented

ok .. did some more experimenting. When I said that the other site I was testing on which did not have nodeprofile, and UR was working for me .. well I had "Allow Multiple Relationships" checked. when I unchecked that, the link for Create Relationship and the Relationship Actions block disappears.

So this does not seem to have anything to do with nodeprofile.

So my question now is: Why do we have to have "Allow Multiple Relationships" checked to see any sort of "Create relationship" link on any of the user pages. What if I only want to have one type of relationship "Friend" and that's it and I do not check "Allow Multiple Relationships". Shouldn't there be a link "Create a relationship" or the visibility of the "Relationship Actions" block for this somewhere still on the user profile pages ?

drupdrips’s picture

drupdrips commented

5.x-2.x-dev works for me. All this time I was using 5.x-2.8 and it did not work for me for some reason unless "Allow multiple relationships" was checked.

Also played with the 5.x-3.x-dev version which is a 3.x branch but it seems all the plugins (like the ones for integration with privatemsg etc.) are missing. However the author/maintainer Jeff at that time seemed to have suggested this :

"3.x!? Are we already at v3?

Yes, it breaks the old API in favor of a newer, better, faster API. It also strips out a lot of cruft that built up. Mostly it separates the API and UI (a la Views) so if you just need the API, you can have it, it's yours, enjoy."

My question to Alex (the current maintainer) : Do you know if we can use the plugins from 5.x-2.x-dev with the 5.x-3.x-dev branch ? Since Jeff is suggesting code improvements with the 3.x API (especially I like the word "faster") I am interested in using it but the plugins are missing, so not sure if they will work with 3.x.

drupdrips’s picture

drupdrips commented
Title: User Relationship and Nodeprofile not playing well together ? » Create Relationship Link does not show unless "Allow Multiple Relationships" option is checked

Changed the title to fit the subject matter better since I have come to the conclusion now that my issue has nothing to do with interaction from nodeprofile module.

alex.k’s picture

alex.k commented

It sounds like some other module besides nodeprofile might be involved. I could not reproduce the issue, i.e. I see the link as expected even when multiple relationships are disabled. Also, can you check that in the case where you don't see the link, there isn't already a reverse relationship (from user B to A) established.

drupdrips’s picture

drupdrips commented

Thanks Alex. As I said 5.x-2.x-dev is working for me as expected, but for some reason 5.x-2.8 gave me issues with seeing the create relationship link unless multiple relationships was enabled. And no there was no reverse relationship already existing.

I guess I will try deinstalling the dev version and re-install fresh the 2.8 again and see if the problem reproduces in case I rain into some kind of gremlins.

Just two questions:

(1) In case I get stuck with the problem again on 2.8, is it ok to go ahead and use the 5.x-2.x-dev version. It seems this is a more later version based on last commit dates.

(2) Also can you comment on the better API (faster performance) of the version 3.x is usable or not and if so what about the plugins that the 2.x versions came with ? These plugins are not available from the 3.x download tar file.

alex.k’s picture

alex.k commented
Assigned: Unassigned » alex.k

I would recommend staying with 2.x-dev. It differs from 2.8 mostly by bugfixes committed since Sept '08 when I took over the module. So it is not likely to have introduced many new bugs. A 2.9 release could be made with the current snaptshot.

As to the 3.x branch. There will not be a performance gain that I know of - the intent of 3.x was to refactor the API to align it with 6.x for easier support of both versions. This rewrite is not finished yet as you see, and there is not so much interest nor developer time to work on that. I don't know what is easier - to port 5.x-2.x plugins to 3.x, or to backport them from the 6.x branch :)

Thanks for troubleshooting. As you don't have the issue using 2.x-dev, I would say we can close it and consider it fixed.

drupdrips’s picture

drupdrips commented
Status: Active » Fixed

Thanks again for the final confirmations and your suggestions. I have updated the status to "fixed" .

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.