Here is the issue I'm running into

I'm setting up contexts for my custom node types using a node reference field populated by nodereference_url. The point is that I want to pull in some bits of data from the referenced node and wrap that around the node add and edit forms.

This setup works ok for the edit form but the contexts do not seem to pass correctly to my node/add form.

Here is the rundown:

* I've enabled the node add/edit page
* I've added my node reference field as a relationship in the panel page.
* All of the expected %nodereference context keywords are displayed on the contexts tab
* If I edit an existing node the %nodereference context is passed correctly
* If I add a new node the %nodereference data is not passed correctly even though it is being auto populated in the "add" form by nodereference_url

It seems the node add form is a special case and different from the edit form. This makes sense in some ways but it still seems like the context should still work since the nodereference value is in fact in the node add form.

Not sure if this is normal behavior or a bug. Any suggestions are mucho appreciated.

Thanks!

P.S. This issue was also noted over in the forums. http://drupal.org/node/956354#comment-3668838

Comments

vonn.new’s picture

vonn.new commented

I'm having the same issue. I see there's been no activity on this. Have you figured it out?

In my case I want to pass a taxonomy tid so that I can have other views of related displayed in panes as I add a data type story.
I've tried passing an argument in the url as I call node/add/story/1
Where 1 is the tid of my taxonomy term.
But then I can't seem to pass it to my views in the other panes. I've tried setting arguments in the configuration for my views content, but that isn't working.

Sure would appreciate any advice anyone can offer.

Letharion’s picture

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

Hello!

Unfortunately, this issue has remained open, without activity, for a very long time. I hope you can understand that between maintaining the module, work, and other obligations, the maintainers are very busy. This leads to not all issues being answered.

In order to figure out who still actually needs help, I'm going over all low activity support requests that has not been touched for 6 months, and marking them "Postponed, needs info". In many cases, I expect the question to already have been answered, or become obsolete.

If you still care for this issue, please just reset it's status to active, and we'll try to help you. Please remember to post any new information that may be relevant, such as new versions of Panels that you are using, or own attempts at debugging.

Regards, Letharion

Letharion’s picture

Letharion commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

A month has passed, and I'm going over the issue queue ones more. Some issues have been closed for other reasons, some re-opened, but this issue has remained silent for the past month.
Because of this, I'm doing a bulk close of a number off issues. I'm sorry that it happened this way, but the issue queue has had to few contributors, and to many questions.

Again, as said in the previous comment, feel free to re-open the issue by setting it to active, if you still need help.

Regards, Letharion.