You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have Person data in a Paragraph, in an entity reference field connected to the Person vocabulary. I’d like to map the Person entity reference field in the Paragraph to be the “author” in the citation. I did this:
Selected “Map from Entity” in the paragraph reference field.
In the Paragraph > Paragraph Type > Person entity reference field > set the CSL field as “author”
But I don’t see any names in the citation block.
This is what I have in my object, and “Dara Virks” is a term within Person taxonomy.
This is how I mapped the Person Name field in my paragraph type:
And this is the setting in my “Person Bundle” paragraph field in the Repository Item content type:
I talked with Akanksha about this and she said:
the author (or any CSL name variable) not being rendered is a bug. This is a problem with using author in anything other than typed relation. Since we use typed relation field for author we never really tested it with vanilla entity reference. In CSL, name fields have to be formatted differently and the formatting is done only for typed relation right now. I’ll raise a quick PR for this later today.
So it sounds like this is a bug. I'm opening this issue in case it helps. Thank you!
The text was updated successfully, but these errors were encountered:
I have Person data in a Paragraph, in an entity reference field connected to the Person vocabulary. I’d like to map the Person entity reference field in the Paragraph to be the “author” in the citation. I did this:
But I don’t see any names in the citation block.
This is what I have in my object, and “Dara Virks” is a term within Person taxonomy.
This is how I mapped the Person Name field in my paragraph type:
And this is the setting in my “Person Bundle” paragraph field in the Repository Item content type:
I talked with Akanksha about this and she said:
So it sounds like this is a bug. I'm opening this issue in case it helps. Thank you!
The text was updated successfully, but these errors were encountered: