For some reason I have one field group that refuses to be deleted. Below is a screen cast showing the problem. Ignore the dogs battling in the background, they were just showing off.
| Comment | File | Size | Author |
|---|---|---|---|
| #22 | enable-groups.png | 64.87 KB | nils.destoop |
Comments
Comment #1
joostvdl commentedsubscribe... same problem here
Comment #2
nils.destoop commentedIs it possible for a non-java movie? Don't have the java plugin installed on chrome / firefox :).
Comment #3
bryancasler commentedUploaded the video for you
http://k.min.us/ijhyMe.mp4
Comment #4
nils.destoop commentedCan you take a screenshot from your field_group table in the database? Maybe something is wrong there.
Comment #5
bryancasler commentedHope this helps
http://awesomescreenshot.com/06c83r8f0
Comment #6
nils.destoop commentedCan you delete the row with id 6? Maybe this causes the problem
Comment #7
nils.destoop commentedComment #8
bryancasler commentedI'm able to delete it now through drupals interface. Not sure what was causing this. Additionally after deleting it, the row with id 6 is still there.
Comment #9
Stalski commentedStrange, but glad it is fixed. I don't know how this 6 without group_name was possible, but it shouldn't.
Comment #10
mstrelan commentedWere you using features? I have the same problem, cannot delete fieldgroup if the fieldgroup is part of a feature. I want to delete it and then recreate the feature, but when I hit delete it just resets to whatever was exported in the feature.
Comment #11
kars-t commentedI can confirm this behaviour. We couldn't delete a group that was part of a feature. Error message was:
Comment #12
wmostrey commentedThis might be related to #1177652: Features revert causes error.
I have the same issue. A field group can not be deleted if it's part of a feature. There are two cases in which I did manage to delete the field group:
Comment #13
Stalski commentedComment #14
nils.destoop commentedFieldgroups can now be deleted. When they are exported, they will be disabled with ctools. Disabled items are not shown anymore.
However: a bug is in features at the moment. Features doesn't notice that the feature is overriden, when a group is disabled. Because of this: you can't re-enable them.
I created an issue at the issue queue from features: #1239734: Feature not beïng set to overriden, when a ctools export (fieldgroup) is disabled
Comment #15
Stalski commentedGreat
Comment #16
Stalski commentedAnother bug came up here.
- Create a content type vertical tabs content (or something :p)-
- Create a vertical tab group and two vertical tabs underneath.
- Remove the vertical tabs group.
- Add it again with the same machinename
- It's not showing up anymore.
The reason is that in ctools_export_load_object the group in question is loaded, but it's status is disabled, so it's filtered out.
I will check now if we can add "disabled=0" for each normal creation.
Comment #17
nils.destoop commentedGroups are now default enabled, when they are created.
Comment #18
Stalski commentedLooks good and seems to work.
Comment #20
Stalski commentedThis should probably be reverted.
After a chat on IRC with Berdir, we found that
really removes the group, also when it's in code.
The proposition is to do something with the disabled property, the way views does. We could grey them out at the bottom of the fields UI screen so they are not really gone, just disabled while existing in code.
Comment #21
darrenmothersele commentedAfter creating a field group programmatically, and then deleting it through the admin interface, there's no way to get this field group back again.
I found I had to comment out this
continuein order to get my field group back again:I now have an issue that if I make changes to the field group in code, they are not reflected in the field group settings shown in the admin interface.
Comment #22
nils.destoop commentedI just committed new code for re-enabling fieldgroups in code. Once you delete a fieldgroup, that is stored into code. An extra vertical tab will appear, to re-enable the group. Included a screenshot of it.
Comment #23
Stalski commentedGreat job, that's what we needed!