Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Here are the notice I have in my logs:
Emplacement http://toto.com/admin/structure/types/manage/pays/comment/fields?render=...
Référent http://toto.com/content/france
Message Notice : Undefined index: comment_node_pays dans _field_ui_bundle_admin_path() (ligne 325 dans /var/www/toto.com/modules/field_ui/field_ui.module).
Comment | File | Size | Author |
---|---|---|---|
#3 | Correct stack trace.png | 126.4 KB | Reg |
#2 | Stack trace.png | 68 bytes | Reg |
Comments
Comment #1
star-szrDid you try clearing your cache? It sounds a bit like Field UI was looking for a field that was no longer there.
If you can provide the steps to reproduce this error from a clean install that would be very helpful.
Comment #2
Reg CreditAttribution: Reg commentedI get this every time I create a new content type even with no 3rd part modules on the latest version, 7.21 .
To reproduce, create a new content type and this is with all cache turned off.
I can offer a little more information as as I have a stack trace which I'm attaching as a graphic.
Somehow I uploaded the wrong screen shot. Please ignore and use the one in the following comment.
Comment #3
Reg CreditAttribution: Reg commentedCorrect screen shot.
Comment #4
Edgar Saumell CreditAttribution: Edgar Saumell commentedI did a clean install of 7.22
Steps to repeat:
Clearing caches does not solve it.
Doing a search of '_field_ui_bundle_admin_path' on d.o. gives a lot of related issues. This one (same problem with forum module) has some patches: #1351506: Disabling or uninstalling a node-type module (e.g. Forum), or removing a node type, results in "undefined index" notices and a workaround https://drupal.org/node/1351506#comment-5428118
In my case I got rid of this notices running
delete from field_config_instance where bundle = 'blog' || bundle = 'comment_node_blog';
on the database and then clearing caches.Comment #6
apadernoComment #7
apaderno(The correct status is probably this one, since the issue summary needs to be updated.)