The body field has no text. Please supply content to the body field.

Yes, it will be expanded upon so you can select which longtext field to summarize. In its current form, its based against node fields, so I am not sure how to make it paragraphs aware yet.

Circling back on this. I have noticed just a couple of things.

- It would be nice if you could 'replace' the response into a given field.
- It would be nice if you could use the same tools from the Node creation form (may require JS?)
- Definitely need to be able to select from a list of all text based fields on the node object instead of assume body only.

The third point I can go after right away.

Is the issue that the body field must exist for the search to take place. For instance, a node that has several long text fields but none of them are the body text field. If the body text field is not present the search cannot happen. However, if the body text field is present but left blank the search proceeds and looks at the remaining text fields?

The issue is that the user does not have the ability to select which field to look at right now, and body is hardcoded.

I believe there is a patch here: 🐛 openai_content functionalities appear only on edition and not on creation Fixed

This has been fixed: 🐛 openai_content functionalities appear only on edition and not on creation Fixed

Automatically closed - issue fixed for 2 weeks with no activity.

@kevinquillen this is not fixed. unless i understand something wrong, identification of text fields within paragraphs is not supported yet. So to return to the initial issue description, if body is removed from the content type and the basic content text field is within a paragraph, its not identified by the openai module as candidate for summarise etc