Method for supplying feed-global author information conflicts with theme expectations · Issue #274 · jekyll/jekyll-feed · GitHub
Skip to content

Method for supplying feed-global author information conflicts with theme expectations #274

Open

Description

@travisdowns

If you want to provide a name for the top-level/global <author> tag in feed, you can do it like author: Travis Downs in the _config.yml. So far so, good. If you want to provide more than just a name though - say your email, it seems like jekyll-feed supports doing it it by making author a map in the _config.yml like this:

author:
  name: Travis Downs
  email: travis.downs@gmail.com

The problem with this is this blows up themes which expect author to be a scalar. For example, Minima fails to serve when this is done, because it expects a scalar string author.

It is really clear who is "at fault" here, i.e., whether it is valid to make author a map.

Is there any other way to set the global author info including email so I can work around this issue?

Activity

  1. jekyllbot commented on Jun 30, 2019

    @jekyllbot
    Contributor

    This issue has been automatically marked as stale because it has not been commented on for at least two months.

    The resources of the Jekyll team are limited, and so we are asking for your help.

    If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.

    If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.

    This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.

  2. travisdowns commented on Jun 30, 2019

    @travisdowns
    Author

    I can still reproduce this on the master branch.

  3. jekyllbot commented on Aug 31, 2019

    @jekyllbot
    Contributor

    This issue has been automatically marked as stale because it has not been commented on for at least two months.

    The resources of the Jekyll team are limited, and so we are asking for your help.

    If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.

    If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.

    This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.

  4. travisdowns commented on Sep 1, 2019

    @travisdowns
    Author

    I can still reproduce this.

  5. jekyllbot commented on Nov 1, 2019

    @jekyllbot
    Contributor

    This issue has been automatically marked as stale because it has not been commented on for at least two months.

    The resources of the Jekyll team are limited, and so we are asking for your help.

    If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.

    If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.

    This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions