Posted by Frippuz on October 4, 2011 at 9:22am
3 followers
Jump to:
| Project: | NodeStream |
| Version: | 7.x-2.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Each time I add new field to a content type provided by NS, the NS feature is overridden.
In most cases the overrides contains changes in dependencies or field weights, but it looks ugly when feateus are overridden, making me think that there are something wrong. Or, I ignore the overrides because I "know" what lays behind the override.
Can this be resolved at all? I guess it lays in the nature of featues to report breakage in all cases, even if the overrides resides in another feature.
Comments
#1
It is possible to add new fields without causing a weight issue. I guess we should try and set the weights on the "core" fields in a way that they don't conflict with new fields.
A thing you could try is to not adjust the weights of your fields in the interface at all, just export the feature and then adjust the weight manually. When you are pulling things up and down in the UI, you must change the weight of the other objects as well, which causes overrides.
#2
Try the new 7.x-2.x-remove-fields-from-features branch out. It might do the trick for you here as well.
#3
The changes are now in NodeStream core, which means you should be able do what you will with the fields. Please post back here with your results.
#4
I'm setting this to fixed, since this should not be a problem anymore.
#5
Automatically closed -- issue fixed for 2 weeks with no activity.