Is it ok to share a comment field with multiple content types?

Anders

5/10/24, 2:47 PM

Imagine I want to convert individual forum threads (topic + comments) into a content type 'Blog post' to preserve them for the long term.

In order to make this work, the comment field of 'Blog post' needs to be identical to that of 'Forum topic' (this is a limitation of the conversion module currently in beta). Thus I simply re-used the comment type comment_forum also for 'Blog post', which works fine.

Now I wonder if that'll cause problems in the long term. At least it seems pretty counter intuitive to use comment_forum for anything other than 'Forum topic'. I do not yet fully understand what the implications are of sharing a comment field with multiple content types.

Should I go ahead? Are there better ways to accomplish this?

0 + 1

nodes

comments

Clive

5/10/24, 3:11 PM

If the comment field has to be literally identical, then this is the only solution. Even if you just mean it has to have the same field and storage settings it probably doesn't change anything - sharing fields across multiple bundles is common, encouraged even, that's why the API goes out of its way to allow it. Aside from the potentially confusing field name, I'd say you don't have anything to worry about

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: Is it ok to share a comment field with multiple content types?

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.