I'm using the latest dec version of drupal and i want to create new product types with commerce.
So i cannot create new fields on my product types.
When I do that i get the following error:
Undefined index: in _field_ui_bundle_admin_path() line 309 in field_ui.module
This funtion looks like:
function _field_ui_bundle_admin_path($entity_type, $bundle_name) {
$bundles = field_info_bundles($entity_type);
$bundle_info = $bundles[$bundle_name];
if (isset($bundle_info['admin'])) {
return isset($bundle_info['admin']['real path']) ? $bundle_info['admin']['real path'] : $bundle_info['admin']['path'];
}
}
I've looked up all teh info on the net and there are old post about this but i've checked all of them all these patches are correct in my version.
Can anyone help me out.
Kind regards,
ed
Comment | File | Size | Author |
---|---|---|---|
#27 | field_tabs_entity_info_cache.patch | 1.67 KB | dawehner |
#25 | field_tabs_entity_info_cache.patch | 1.67 KB | dawehner |
#23 | field_tabs_entity_info_cache.patch | 1.67 KB | dawehner |
#16 | field_tabs_entity_info_cache.patch | 2.58 KB | dawehner |
#14 | 1079966-rename-bundle-test.patch | 1003 bytes | dawehner |
Comments
Comment #1
edg1 CreditAttribution: edg1 commentedComment #2
edg1 CreditAttribution: edg1 commentedupdate the fiel_group module to the latest _dev
doesn't work
i don't know what to do can anyone help here ?
Comment #3
edg1 CreditAttribution: edg1 commentedComment #4
Oceanman CreditAttribution: Oceanman commentedI am getting these notices too. This error appears when I am in the "Manage Fields" tab of the field collection module.
# Notice: Undefined index: fieldable in field_ui_menu() (line 72 of modules/field_ui/field_ui.module).
# Notice: Undefined index: fieldable in field_group_menu() (line 25 of /modules/field_group/field_group.module)
Could this be an issue for field collection and not core? Maybe it should be moved.
Comment #6
Wappie08 CreditAttribution: Wappie08 commentedActually this happened to me with the core book module after I renamed the machine name (from book to customname):
Notice: Undefined index: customname in _field_ui_bundle_admin_path() (line 309 of /modules/field_ui/field_ui.module).
Actually it's weird that "book" seems to be hardcoded in the system, it would be much more logical if one can change this name (instead of having to make a new content type and deleting type book).
btw. after uninstalling and reenabling book the problem was solved.
Greets
Comment #7
klonosI also got this when trying to go to the "Manage fields" tab of a custom content type after I'd just changed its machine name to a custom one. I'll give this a go in a vanilla setup ...unless someone beats me to it.
Comment #8
klonos...related(?): #686938: Undefined index: admin in _field_ui_bundle_admin_path()
Comment #9
klonos...sorry, meant to have a generic token-style name there in the title.
Comment #10
catchAttaching a patch, I haven't tested this, please give it a try and report back. Instructions for using patches are at http://drupal.org/patch/apply
As a @todo, field_attach_rename_bundle() should change to entity_rename_bundle() in Drupal 8.
Comment #11
catchThis needs simpletests, but please try manually if you're experiencing the bug.
Comment #12
catch#1091054: Disabled content types and modules cause notices in field_ui_fields_list() was duplicate.
That bug report suggests the might also be a need for clearing caches on bundle deletion if that's not already done.
Comment #13
xjmTagging issues not yet using summary template.
Comment #14
dawehnerHere is a patch for the test, but it sadly doesn't fail at the moment.
Perhaps someone understands why.
Comment #16
dawehnerHere is a merged patch
Comment #17
catchCan you explain why the node_type_save() cache clears are moved around - I'm sure we moved them the other direction not too long ago.
There's an extra blank line in the first hunk.
The logic in field_ui looks sound to me, although it makes me wish we had crud functions for menu router items instead of info hooks + manual calls to menu_rebuild().
Comment #18
catchComment #19
dawehnerActually i just merged the patch from you in, so i'm not totally sure why this was done.
Comment #20
catchOh dear :( I knew I remembered something but didn't realise it was a few comments up
Trying to remember back to June - we needed to clear the cache in both update and insert hooks before anything was invoked. It feels like that leaves a potential race condition if the cache is set again before the hooks are done, so I think it does need work for that and that's clearly my fault.
Comment #21
steinmb CreditAttribution: steinmb commentedSubscribing. Got a few D6 upgraded sites that throw those errors all over the place, pls. let me know I you need help testing patches.
Best reg.
steinmb
Comment #22
Todd Young CreditAttribution: Todd Young commentedStill seeing this error on D7.8, subscribing.
Comment #23
dawehnerActually it doesn't need tests anymore.
So let's try out what happens if you don't reorder the stuff in node.module
I guess if the test passes this is optional at the first place.
Comment #24
xjmThis is super nitpicky but I believe this is supposed to be "Tests..." rather than "Test..."
Comment #25
dawehnerOkay you should know it :)
Comment #26
catchExtra line break.
Otherwise looks good to me.
Comment #27
dawehnerHere is the new version.
Comment #28
chx CreditAttribution: chx commentedLooks good to me as well.
Comment #29
webchickCommitted and pushed to 7.x and 8.x. Thanks!
Comment #30
klonosThank you people!