CCK node references not being styled as specified

I'm having a similar probem with 2.0 beta4b, Panels not responding with proper formatting when referring to a node reference in one of the panes. I'm trying to get the whole node to show but only the title with a link is displayed. What I have is a review form that has a CCK field with a node reference in it. I would like the reviewers to be able to see the node they are reviewing on the same page as the review form itself.

In the Context tab of Panels, I am using the relationship Node from reference and then in the Content tab selecting Content field and then Full node in the field Field/Formatter.

@jfuzzy: the version tag should (almost) never be changed to an earlier version. It's primary use is to indicate the most recent version of a module for which a particular problem exists.

If either of you could verify that this was a problem in beta3, but became a problem in beta4, it would be very helpful to me in tracking down the source of the problem.

A note, though - what you're talking about sounds a lot more like something that should be done in a view, then pull that view into panels. The way you're going about it could be a real performance killer, as you're loading _way_ more data than required to output what you're outputting. At least, that's what it sounds like based on these limited descriptions.

@sdboyer - I'm using the Panel because I am overriding the default content type (node/%) to add header text and attempting to show 2 nodes side-by-side, one referencing the other. In my beginner knowledge, I do not believe that I can accomplish the side-by-side effect with Views and this is why I chose to go with Panels.
Note taken about the version tag, but it did seem redundant to post separately. Thanks for any help on this issue, but I am not able to check the function in beta3.

Sorry, I wasn't clear - my comment about using views was more directed at meo than you.

re: versions - well, you're kind of trading one redundancy for another. The assumption is that any issue that exists in a given version will ALSO exist in all the preceding versions. It's implicit, but nevertheless pretty much rock-solid unless someone says something specifically to the contrary (as meo did, thinking that it worked prior to beta3). In that case, however, the assumption shifts over to being that all the intervening versions between the current version and the older version are affected by the bug. That's what makes explicitly identifying one of those issues redundant.

Finally, in reference to the substantive issue at hand - I'm almost completely sure that this doesn't belong in the Panels queue, as the code that's responsible for the problem (if indeed there is one, and it's not just a configuration error) is not in the Panels codebase. More than likely, it's in the CCK plugin declaring a panels content type.

Closing this as there's nothing we can do on our end.

You're right about this being a CCK issue. The fix is here:

http://drupal.org/node/278631

Glad that fixes it.

So, why did you reopen the issue? As I said - that file is not a part of the Panels package; it is a part of the CCK package that implement the Panels API.