Closed (fixed)
Project:
Node Reference URL Widget
Version:
6.x-1.0
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
10 Mar 2009 at 18:55 UTC
Updated:
25 Apr 2009 at 01:30 UTC
Jump to comment: Most recent file
Comments
Comment #1
quicksketchHow were you able to delete the field if you couldn't access "admin/content/node-type/son"? If you were getting a page not found on node/add/son, this is intentional. If you want this page to work without a referenced NID, you can set the field to use the "Use select list widget" instead of "Display page not found error".
Comment #2
Antinoo commentedNo, I'm not talking about
node/add/son, I'm talking ofadmin/content/node-type/son.I could delete the field since
admin/content/node-type/son/fieldswas still reachable.I've just tried for the 3rd time, with a new content-type, and I'm always getting that error: haven't you ever seen it?
If not, create a new content-type, eg. son, add a Node Reference from URL field to it, and then try to go to
admin/content/node-type/son(the edit content-type form). I don't get the form showed. If you are getting it, I'll try with a Drupal fresh installation.I'll try to look into the source code as soon as I have time to do it.
Greetings, Giovanni
Comment #3
quicksketchI'm not able to reproduce this at all. Make sure you update to the latest 1.x development version before writing a patch, maybe this has already been fixed.
Comment #4
Antinoo commentedI've tried with a fresh D6 installation, and it works fine.
Looking at the backtrace, I've found that maybe there's a conflict between this module and Vertical Tabs one.
If I disable VT, I can access again to the
admin/content/node-type/[node-type]page.Still according to the backtrace, the VT module runs
vertical_tabs_form_alter(),vertical_tabs_node_type_form()anddrupal_prepare_form(), then the control is passed to CCK.I don't have time at the moment to look deeper at the VT source code. I'll check in the next days.
Giovanni
Comment #5
Antinoo commentedHere it is the code I think generates the error (from vertical_tabs.module):
Comment #6
quicksketchThis patch fixes the problem. The manual build process used by Vertical Tabs (and hopefully other modules) doesn't contain a form_build_id element, so we can check that this field exists before throwing an unnecessary page not found error.