nodefamily should be improved to a general node relation (API) module, while "old" features will be available in another legacy module.

CommentFileSizeAuthor
#4 nodefamily.zip32.16 KBfago
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

tanc’s picture

Any news on how this is progressing? Will the module retain the same name or should I look out for something new?

The 5.x version of the module is awesome and I use it extensively on a complex site, thanks for coding it.

chipway’s picture

Hi,

Sorry for the new issue. I copy my question here.

Do you plan to upgrade Node Family to D6 ?

Do you have any idea of the availability date ?

Thanks a lot.

edward.peters’s picture

I have heard from fago that a port has been done, but it needs testing. He says he will publish the code asap so that we can test. Warm thanks to these heroes!

fago’s picture

FileSize
32.16 KB

Here is it. as said it needs testing and perhaps some love, but it should basically work.

Conceptional changes since 5.x-1.x:
* the main module changed to a node relation API module, which can be used by other modules or e.g. by not yet existing pageroute integration
* the "old" functionality of automatically creating relations between the nodes of a user is gone into a nodefamily legacy module, which makes use of the new API.
* Views integration is still missing

tanc’s picture

Awesome fago, nice one. I will test it soon... actually not for a little while but I'm looking at using it on an upcoming D6 project so I'll let you know my experience. Thanks.

edward.peters’s picture

Fago, thanks so much for publishing this code. I have done a little initial testing. I notice that the readme.txt may need a little updating in relation to the changes, e.g. admin/content/nodefamily apparently replaced now by admin/content/nodefamily_legacy. Also, when I put the function nodefamily_relation_load into the node.tpl file as per the readme.txt, the function was not found. Unfortunately I am not a Drupal developer and therefore not able to offer more useful feedback at present. But I look forward to seeing the new module stabilised, as I am in great need of it! Thanks again.

fago’s picture

hm, I think README is still the old and needs to be updated.

chipway’s picture

Hi,

Any news about this port ?

Thank you

bneel’s picture

+1

paulnem’s picture

Fresh install of drupal 6.x, enabler nodefamily and nodefamily_legacy results in the following error :

Fatal error: Call to undefined function nodefamily_add_relationtype() in /home/datitho4/public_html/sites/default/modules/nodefamily_legacy/nodefamily_legacy.install on line 31

Muskwa’s picture

are there any news on drupal 6 port?

sam.e2’s picture

Any progress?

In the mean time, does anyone know another way of limiting the number of nodes a user may create/edit?

Thanks, and thanks for making this module in the first place :)

SocialNicheGuru’s picture

subscribing. this module is very useful

design.er’s picture

Hi sam.e2,

This module should help you: http://drupal.org/project/node_limitnumber
Here is also the port to D6: http://drupal.org/node/259084
And it seems that the developer forgot to create a function that should create a table in the drupal db. :)
So, before installing the patched module, you have to create this new table in your drupal db:

CREATE TABLE IF NOT EXISTS `node_limitnumber_rules` (
  `id` tinyint(3) unsigned NOT NULL auto_increment,
  `class` enum('role','user') NOT NULL,
  `item` int(10) unsigned NOT NULL,
  `pubtype` varchar(32) NOT NULL,
  `max` tinyint(3) unsigned NOT NULL,
  PRIMARY KEY  (`id`)
) ENGINE=MyISAM  DEFAULT CHARSET=latin1 AUTO_INCREMENT=5 ;

The sql code that is delivered on the port page does not work, so you'd better use mine.

I hope that will help you.

Regards,
Stefan

ianchan’s picture

subscribe

Antinoo’s picture

subscribing

sridharraov’s picture

Subscribe

giorgio79’s picture

This seems to be the way to go in D6
http://drupal.org/project/noderelationships

Aren Cambre’s picture

Title: Port to 6.x » Is Node Family abandoned?
Category: task » support
Priority: Normal » Critical

Given #18 and no progress in a long time, can this module be abandoned?

fago’s picture

Status: Active » Closed (won't fix)

That would be fine for 6.x, but there is still a 5.x release - but there never was for 6.x. So I don't see why 5.x should be abandoned thanks to a not existing 6.x version? However feel free to take over 6.x development if you wish.