Closed (won't fix)
Project:
Content Construction Kit (CCK)
Version:
5.x-1.x-dev
Component:
nodereference.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Jan 2007 at 22:21 UTC
Updated:
11 Jan 2012 at 16:46 UTC
Comments
Comment #1
yched commenteddoes make sense :-)
Comment #2
dopry commentedMoshe,
I think for this particular issue, you're just going to have to remember to update your nodereference fields.... I don't think you should tread into changing the machine readable names of fields lightly. It is something I would prefer that we didn't expose in the UI. There is really no functionality gained by exposing this value, except assisting theme developers. I think if a theme developer is into php enough to write custom node templates they can handle some slightly misrepresentative variable names. Also how are your theme's going to know about the changes when you do this?
I personally believe we should remove editing the machine readable names from core. It presents a need for a relatively useless event for modules to respond to a *machine* readable name change.
Comment #3
karens commentedThe D5 version is no longer being supported. Sorry.