Since a profilenode must now necessarily be of population 1 (I put 2 and then enable content type as nodeprofile, and the population automatically gets reset to 1), when I try to create a translation of the node, when I submit it, I am told I can only create a single node of this type.

Support for i18n would require a population size to be doubled (ideally only) in the case of using the additional node for translation purposes.

Am willing to help in coding, since I do need a solution, but would like to listen first, before starting to hack.

Thanks.

Victor Kane
http://awebfactory.com.ar

Comments

fago’s picture

fago
Primary language German
Location Vienna
CreditAttribution: fago commented

sry for the late reply
indeed that would be a great feature. Unfortunately I've not knowledge with i18n, the last time I've used it is over a year ago..

How are translated nodes tied together?
I think the fix has to go currently into nodefamily, which does the population restriction. So I would say, keep the value of one for nodeprofiles, but count all translations of one node together as 1.
However there might be some necessary UI changes for nodeprofile too!?

Of course I'd appreciate any contributions :)

idmacdonald’s picture

idmacdonald CreditAttribution: idmacdonald commented

Hi,

This is something that I need for a site, too. I have tried hacking the nodeprofile code a bit to allow this, but it does look like some extensive changes to the nodeprofile module would be necessary, as well as changes to the nodefamily module. So, for the moment, I am just creating a CCK field for each language in the nodeprofile, then using different views for different languages to show the appropriate field. It's not a great solution, but it is the only way to do this at the moment. But just as normal profiles can be internationalized with i18n, it would be great to have this for nodeprofiles too. Does anyone else have any solution or better work-around?

-Ian

victorkane’s picture

victorkane CreditAttribution: victorkane commented

What I wound up doing (and this works for my needs right now) is hacking nodeprofile.module as follows, circa line 230:

    // 20070914helpargentina vk: we need to be able to specify a max of two for translations
    /****
    if (is_nodeprofile($form['#node_type']->type)) {
      $form['workflow']['nodefamily_max']['#disabled'] = TRUE;
    }
    ****/

This enables the nodeprofile enabled content type specification of maximum number of nodes, instead of freezing it at 1.