I'm looking for a module to stablish node links between nodes. I think these module is perfect for me but I need some help because I get errors and I don't know how to solve it.

I work with Drupal 4.7.3 so I tried Relationship 4.7 version, but it doesn't worked for me and Drupal was not able to print the Relationship administration page.

Now I'm triying the cvs version. With these version everything seem to work but I get these error when I trie to create a new story node:

Failed to find a longname (URI) for 'story' - it matches no known identifier
: in relationship_get_longname(), line 843 relationship_api.inc : in relationship_get_object_title(), line 785 relationship.module : in relationship_get_titles(), line 678 relationship.module : in relationship_form(), line 129 administer_relationships.inc 0.08s elapsed. (8 total)

Is the cvs version the most recomended for drupal 4.7?

Thank you.

Comments

dman’s picture

I may be a little confused with the CVS tagging (vs branching) but the state of play is that the 4.7 branch should have been sorta stable, and AFAIK mostly compatable with Drupal 4.7.x, but probably not with Drupal HEAD.

The Relationship CVS version is a bit more volatile, but also works on Drupal 4.7.x, probably not Drupal HEAD.

The bug you report will be directly relating to some changes in the shortname identifier process for content types I touched recently. To do with some work on getting it CCK compatable.
... or actually, it's a leftover debug notification alerting that there's a gap in the systems knowlege.

I need some way of registering that 'story' is a valid content type. I added 'page' but not 'story' yet.

Try visiting admin/settings/content-types/page and just saving that form.

I've recently removed the debug line myself, but have some other tweaks before commiting it.

solanas’s picture

The tip

Try visiting admin/settings/content-types/page and just saving that form.

works for me in cvs version.

Thanks.

dman’s picture

In line with my model of Drupal nodes as classes, the configuration panel available under the node type configs will automatically call into existance a few trivial class statements about node types - but only once that page has been visited.

I haven't yet got it to intuatively know about new node types, I just capture when a change is made to one.

I just tested and smoothed the UI for that a bit in the last hour.

dman’s picture

... so slightly more robust version available now via direct CVS checkout (bundles will happen later).