Command line shell error: ERROR filters:getContributor Contributor not found in 'publication.yaml.' Contributor:

[ACMAA]

Hi all - I'm trying to run quire preview and I'm getting a list of errors. I've been able to figure out most of them, but this one is stumping me. This is the error I'm getting:

These are the contributors in my publication.yaml file:

And this is how I have contributors in my essays (I've tried it both with and without the quotes around the contributor ID):

What am I getting wrong?
Michelle

[Erin-Cecele]

Hi Michelle, have you tried removing the quotations from the ID as it appears in the Markdown file?

[ACMAA]

Hi @Erin-Cecele ! I did - I tried it both ways and neither worked.

[geealbers]

You might want to double check the YAML formatting in publication.yaml and at the top of your Markdown files by copying and pasting it into a YAML validator like: https://www.yamllint.com/. Just to make sure there's no issue there.

Or do you possibly have any empty / blank contributors listed in any of your Markdown files? Like:

title: My Page
layout: page
order: 10
contributor:
  - id:

[ACMAA]

@geealbers I do have a blank one in the Foreword. Should I get rid of that?

[geealbers]

Yes, give that a try

[ACMAA]

@geealbers So sorry I'm just getting back to this!

I tried the YAML validator and fixed all the things that came up. And I made sure none of my markdown files had blank contributors and removed the contributor from the forward.

But I'm still getting the error.

I've got some more errors that I'm trying to work through but the "contributor not found" is the top one.

[Erin-Cecele]

Since this conversation was continued over email, I want to make sure I post a follow-up here. Per @ACMAA

For the Contributor error, I did what you said and removed the contributor from the YAML in essay.md, then I changed to contributor id in publication.yaml and now that part seems to be working. Yay for small victories!

Markdown and YAML files are chained together in a few ways in Quire, so it's helpful to understand the cause and effect created by that relationship. For example, the contributor ID jkeller is referenced in the publication.yaml of the default starter project. If you update the contributor information in that file and delete jkeller, you need to be sure to remove the ID jkeller from the essay.md file as well. That said, don't leave a contributor field blank. Either delete it from the page YAML or add a new id that reflects new ones created in the publication.yaml file.

[ACMAA]

[like] Michelle Padilla reacted to your message:

…

________________________________ From: Erin Cecele Dunigan ***@***.***> Sent: Wednesday, December 3, 2025 9:46:55 PM To: thegetty/quire ***@***.***> Cc: Michelle Padilla ***@***.***>; Mention ***@***.***> Subject: Re: [thegetty/quire] Command line shell error: ERROR filters:getContributor Contributor not found in 'publication.yaml.' Contributor: (Discussion #1048) [Caution: This e-mail is from an external sender.] Since this conversation was continued over email, I want to make sure I post a follow-up here. Per @ACMAA<https://github.com/ACMAA> For the Contributor error, I did what you said and removed the contributor from the YAML in essay.md, then I changed to contributor id in publication.yaml and now that part seems to be working. Yay for small victories! Markdown and YAML files are chained together in a few ways in Quire, so it's helpful to understand the cause and effect created by that relationship. For example, the contributor ID jkeller is referenced in the publication.yaml of the default starter project. If you update the contributor information in that file and delete jkeller, you need to be sure to remove the ID jkeller from the essay.md file as well. That said, don't leave a contributor field blank. Either delete it from the page YAML or add a new id that reflects new ones created in the publication.yaml file. — Reply to this email directly, view it on GitHub<#1048 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAQDPTN755AEFSESNECWPV3375K47AVCNFSM6AAAAACCDW7CSGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMJVGM4DMNI>. You are receiving this because you were mentioned.Message ID: ***@***.***>