Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Thanks for http:// www.gizra.com/content/message-notify-multilingual-email-notifications.
Today also a change received message_notify.
Now we see the following problem also in a 'fresh' Drupalinstallation without enlargements:
- Notice: Undefined index: message_type in _field_ui_bundle_admin_path() (Zeile 320 von /var/www/xxxxx/html/xxxxx/modules/field_ui/field_ui.module).
- Notice: Undefined index: message_type in field_ui_fields_list() (Zeile 35 von /var/www/xxxxx/html/xxxxx/modules/field_ui/field_ui.admin.inc).
The subject is often discussed. Several code changes do not seem to be able to solve the problem yet.
Maybe new solution attempts are found.
Or did we overlook a little bit?
With many greetings
Comment | File | Size | Author |
---|---|---|---|
#34 | message-entity_info_hook_notice_undefined_index-1391442-34.patch | 518 bytes | japerry |
#31 | message-entity_info_hook_notice_undefined_index-1391442-31.patch | 870 bytes | rjacobs |
Comments
Comment #1
amitaibuDo you have latest entity API?
Comment #2
efarg CreditAttribution: efarg commentedYes:
7.x-1.x-dev| tar.gz (95.63 KB) | zip (122.33 KB) | 2011-Dec-28
Comment #3
drupalycious CreditAttribution: drupalycious commentedHello,
I am having the same issue when I go to admin/reports/fields just after enabling the module.
I have tried the stable and the dev version of message.
This is done on a clean install where I wanted to test the module messages, the website has no content yet, only a couple of modules enabled.
Any idea how to fix this?
I enclose 3 images:
the fields report page,
and 2 images of the drush output for the list of the modules in this drupal install (name, version, state)
thank you
Comment #4
amitaibuIt's probably related to Entity API, because Message doesn't do anything by itself in regards to field-UI.
Comment #5
drupalycious CreditAttribution: drupalycious commentedthanks for your answer,
I am using the latest dev version of entity API.
I am going to try with the stable version, but I need the dev for OG 2.x.
Do you think I should transfer this issue to the entity API issue queue?
Comment #6
drupalycious CreditAttribution: drupalycious commentedSame issue with Entity API-7.x-1.0-rc3
Comment #7
drupalycious CreditAttribution: drupalycious commentedjust in case it is useful:
when I enable OG example, the field names "message_text" and message_text_subject" are still mentioned as "locked" and it is indicated that they are used in message_type_email content type, but as you can see in the image I attach, this content type is not linked to anything, I cannot click on it to see or manage its fields.
When I go to the "structure" menu, there is a direct entry for "message types" with add and import options, and when I go to the entry content type, "message types" is not there.
I don't know if it is related or if it is a different issue.
Comment #8
drupalycious CreditAttribution: drupalycious commentedAfter updating ctools, message and message_notify, I got new error messages:
It seems that with the following patch #1375452: Renaming a content type bundle causes notices on manage fields page (test improvements) , these messages would not appear anymore.
But presently the patch failed testing.
Comment #9
JordanMagnuson CreditAttribution: JordanMagnuson commentedJust wanted to report that I'm also getting these messages at admin/reports/fields .
Comment #10
amorales@drupal.org.es CreditAttribution: amorales@drupal.org.es commentedSame problem here in admin/reports/fields. With Drupal Commerce Kickstart 2 fresh install.
Comment #11
Robin Millette CreditAttribution: Robin Millette commentedI'm going to try and fix this...
After a fresh install, there are no defined message types as seen on the admin/structure/messages path.
I had entity rc3, then upgraded to current dev version, no change.
UPDATE
Oh, there's a new message version 1.6. Same thing.
Comment #12
Robin Millette CreditAttribution: Robin Millette commentedToo much entity foo going on for me. Someone else will have to solve this.
Part of the problem is that
field_info_bundles('message_type');
returns an empty array.
Sorry I couldn't be of more help. At least, I learned a tiny bit in the process...
Comment #13
Robin Millette CreditAttribution: Robin Millette commentedCurrent dev message.module line 140
If you replace the line
with
Then the notices go away but I'm quite sure there's still a bug in there.
Comment #14
Christopher Riley CreditAttribution: Christopher Riley commentedAny word on getting this resolved?
Comment #15
joemaine CreditAttribution: joemaine commentedReceiving the same error message on an install of 7.x-1.8 - uninstalled, reinstalled - same error
Notice: Undefined index: message_type in _field_ui_bundle_admin_path() (line 325 of ///public_html/modules/field_ui/field_ui.module).
Notice: Undefined index: message_type in field_ui_fields_list() (line 35 of ///public_html/modules/field_ui/field_ui.admin.inc).
...edit...just tried a fresh Drupal install - notice still appears
...FWIW...here are the enabled modules...
Comment #16
SocialNicheGuru CreditAttribution: SocialNicheGuru commented#13 This gets rid of the error and creates an entry Message type for this which is not clickable.
Is that the correct behavior?
slight modification
Comment #17
joemaine CreditAttribution: joemaine commentedI updated the code from #16 and still have the Undefined index notices
edit - The Undefined index notices have now disappeared. ...a couple of cache flushes were required
Comment #18
vantastic CreditAttribution: vantastic commentedHad exactly the same notices as #15 when calling on Administration › Reports › Field List:
Replacing line 142 in ../sites/all/modules/message/message.module with the five lines from #16 fixed it, but only after clearing the cache and arguably not at its root.
Comment #19
nielsonm CreditAttribution: nielsonm commentedI created a patch to add message_type to the bundles sub-array of the entity info hook. This appears to fix it for me as well.
Comment #20
bjlewis2 CreditAttribution: bjlewis2 commentedChanging to "needs review" so the testbot tests the patch
Comment #21
saurabh tiwari CreditAttribution: saurabh tiwari commentedpatch in comment #19 doesn't work for me!!
Comment #22
fossle CreditAttribution: fossle commented#19 worked for me. Thank you for posting.
Comment #23
T.Mardi CreditAttribution: T.Mardi commentedApplied the patch in #19. On clearing the sites cache I get this error message:
EntityMetadataWrapperException: Unknown data property message_text. in EntityStructureWrapper->getPropertyInfo() (line 339 of /sites/all/modules/entity/includes/entity.wrapper.inc).
Comment #24
kjProtocol CreditAttribution: kjProtocol commented#19: message_entity_info_hook_notice_undefined_index-1391442-19.patch queued for re-testing.
Comment #25
robcarrApplied patch, cleared cache and message gone
Comment #26
mpotter CreditAttribution: mpotter commentedTested #19 in Open Atrium 2 and it works here also. Should get this committed?
Comment #27
amitaibuCan you re-roll this please
curl https://drupal.org/files/message_entity_info_hook_notice_undefined_index-1391442-19.patch | git apply
I get:
Comment #29
rjacobs CreditAttribution: rjacobs commented19: message_entity_info_hook_notice_undefined_index-1391442-19.patch queued for re-testing.
Comment #31
rjacobs CreditAttribution: rjacobs commentedInteresting, patch applies fine via normal "patch" command (some fuzz):
I wonder why the testbots choke on it.
Anyway, here's a re-roll.
Comment #32
rjacobs CreditAttribution: rjacobs commentedFrom the history it seems the only thing that knocked this out of RTBC status was something corrupt about the patch. So after this re-roll, and passing tests, (with no other changes) I'm going to go ahead and restore that status.
Comment #33
cjoy CreditAttribution: cjoy commented#31 works for me
Comment #34
japerryThe #31 patch fails in the most recent version of message. Here is a re-patch to this issue, and it resolves the error.
Comment #35
millionleaves CreditAttribution: millionleaves commentedThe patch in #34 worked for me (after clearing cache) - thanks.
Comment #36
Arrow#34 worked for me as well.
Comment #37
szczesuil CreditAttribution: szczesuil commented#34 works for me on 7.28. Thank you!
Comment #38
chickenforce CreditAttribution: chickenforce commented#34 was helpful for me as well with Commerce Kickstart 2.19. Thank you so much :)
Comment #39
jelo CreditAttribution: jelo commented#34 worked for me too. Core 7.33, message 7.x-1.9.
Comment #40
aramboyajyan CreditAttribution: aramboyajyan commented#34 worked for me too. Core 7.34, message 7.x-1.9.
Comment #41
r2coder CreditAttribution: r2coder commented#34 worked for me too. Core 7.34, message 7.x-1.9.
Comment #42
wundo CreditAttribution: wundo commentedThis was pushed on github: https://github.com/Gizra/message/pull/12#event-238625366
Marking as fixed