I just upgraded to CCK 3.0 for multigroup capabilities. Since I have updated, I noticed that nodes created through Node Relationships "Create & Reference" feature will not publish automatically, even if the content type is set to publish automatically, and the "publish" option is checked when saving the new node. I'm not sure if the fault here lies with NR or CCK, but I'm pretty sure it was working without any problems on CCK 2.7 and Node Relationships 1.6. Anyone able to help on this?

Comments

karens’s picture

karens commented
Status: Active » Postponed (maintainer needs more info)

I don't know what you mean by 'publish automatically' -- are you using some other module that is supposed to do something with your nodes?

NathanM’s picture

NathanM commented

I mean that nodes created through node relationships are unpublished, even if in the content type settings they should be published upon creation. This may have been fixed by the recent nested fieldgroups patch. I will do some testing and report back.

NathanM’s picture

NathanM commented

Ok, after going back and looking at this again, the problem is a little different than what I described. Nodes created through Node Relationships are in fact being published, but additional instances created by the multigroup function are not being referenced once the node is saved. So, for example, I have the following multigroup:

Company: (Node Relationships Create & Reference)
Dates Employed: (Date)
Job Description: (Text)

When I create this fieldgroup as a multigroup, the first instance will look like this:

Company: Company A
Dates Employed: April 2000 to May 2005
Job Description: I worked here.

The 2nd, 3rd, etc instances should then look something like this:
Company: Company B
Dates Employed: May 2005 to August 2006
Job Description: I worked here too.

However, on these 2nd and 3rd instances, the Company field is not being saved, even though it initially appears to be properly created and referenced on the edit form.

NathanM’s picture

NathanM commented

I did some more testing, and it appears that standard nodereference fields are saving in multigroups, it is just an issue with Node Relationships Node-Reference fields.

So perhaps the issue title should be changed to "Issue with CCK multigroups and Node Relationships: Created node-references are not being saved".

karens’s picture

karens commented
Status: Postponed (maintainer needs more info) » Fixed

Sounds like an issue that you should post on Noderelationships.

karens’s picture

karens commented
Project: Content Construction Kit (CCK) » Node Relationships
Version: 6.x-3.x-dev » 6.x-1.x-dev
Component: nodereference.module » Code
Status: Fixed » Active

Actually, I'll just move this issue there.

NathanM’s picture

NathanM commented

Interestingly, I noticed that when pressing "Preview" instead of "Save", it appears that the 2nd and 3rd instances of the node reference fields are previewing properly. It is only when you press "Save" that they are lost. So this should, in theory, be a pretty simple fix, no?

NathanM’s picture

NathanM commented

Is there anyone else that can confirm for me that this issue in fact exists and that I'm not going crazy? CCK3 Alpha 1 has been released now, so I'd think that this issue is going to be cropping up more in the future.

finex’s picture

finex commented

I can't reproduce this behaviour using cck 3 (-dev)