Observations after use
| Project: | Node2Node |
| Version: | 6.x-1.1 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Ok. Just as I thought, this module's very flexible. Very cool.
One observation I made was the
Link target
Set this node to be the target node so that other nodes can be associated with it (Mark Target)
feature. I didn't realize that each time I clicked this link, it would only make ONE page as a target.
For example,
I want to make the category 'books' as a target, then the subcategory (genre) that's called 'horror', 'sci-fi', 'romance'
it would look something like this...
Books
- Horror
- Sci-Fi
- Romance
then of course I'd make the target be 'books', but after that, I want to put something else in lower subcategories, so I figured if i chose all the links that can be 'potential' targets, that each time I made a page, I would see something like
Parent node Type Relationship This node Check
Books page :
Horror page :
Sci-Fi page :
Romance page :
you know, so I'd get to choose, but that's not the case. right now each time I want to make a parent/child relationship, I have to reselect which page is the 'current' parent. Does that make any sense?
Is there any way to make more than one page the parent?
So instead of seeing;
Parent node Type Relationship This node Check
Books page :
I see instead;
Parent node Type Relationship This node Check
Books page :
Horror page :
Sci-Fi page :
Romance page :
Next, the Node2Node administrator page. I originally assigned relationships, but in an attempt to get rid of the (page) text that's written there, I went ahead and took all the relationships off.. it did not give me an 'error' 'relationships needed', instead, it gave me a database error. I originally assigned 3, and so, automatically 3 more blank areas popped up (that was really cool), however, when I realized I just wanted to work with one relationship (because I think the module might get confused) there was no way to get rid of any of that. Even when I deselected page has/belongs to page, deselecting just lead to the database error. So my thinking is that they can go on, but not come off. If i ever tested to see if 3 more will pop up, I'd essentially never get rid of them, it seems.
thanks again for your time, and for this cool module.

#1
Ok, I fiddled around with the module a bit more to find out that the first thing "link target" is available once I have more than one relationship established. So that would work fine. If I have a new page that should be a target, I just have to set a child to it first, and after that, I won't have to select it again it seems.