Just a heads up..
I was testing the https://drupal.org/project/paragraphs module with https://drupal.org/project/scald_galaxy on simplytest.me and I noticed this error after saving a node that included a paragraph bundle field that has an included long text / textarea field. I see the error only if that field includes an embedded atom (image) in that textarea field.
Steps to reproduce:
- Create a paragraph bundle (called Rich Text)
- Add a field type long text / text area called main-text.
- Make sure DND is enabled for that field
- Add a "Paragraph" field to the Article content type called "inlines" and check the box to include/use the new Rich Text
- Create an article node.
- Create a new paragraph of type "Rich Text" and drag and drop an atom inside the wysiwyg editor.
- After Saving the node you see the error.
Notice: Undefined index: field_text in dnd_process_textarea() (line 77 of /home/sb01415a6be091fa/www/profiles/scald_galaxy/modules/scald/modules/library/dnd/dnd.module).
Note: the atom still displays correctly on the article node.
Just thought I would let someone know in case it is an easy fix.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | fix-undefined-index-notice-2166119.patch | 977 bytes | gmclelland |
| #1 | fix-undefined-index-notice-2166119.patch | 872 bytes | gmclelland |
Comments
Comment #1
gmclelland commentedThis seemed to fix the problem for me.
Comment #3
gmclelland commentedUm.. Not sure what that test failure is about? Looks like the testbot may be malfunctioning.
Comment #4
DeFr commented1: fix-undefined-index-notice-2166119.patch queued for re-testing.
Comment #5
DeFr commentedThe original failure was probably a testbot problem, so I've queued the patch for retesting.
That being said, now that I've actually looked into it, this definitely needs work, because it's going to break the "per field default context" feature; you'd need
instead of just
Comment #6
gmclelland commentedThanks @DeFr - Here is a new patch based on your recommendations.
Comment #7
gmclelland commentedChanging back to NR
Comment #8
gmclelland commentedFYI...It is still a problem in Scald 1.2. I just tested the patch in #6 again with Scald 1.2 and it still fixes the problem.
Comment #9
jcisio commentedCommitted a simplified version. Thanks.
Comment #12
freblasty commentedWhy not retrieve the field instance based on the element instead of suppressing the error?