Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
travisdowns opened this issue Apr 30, 2019 · 5 comments
Labels

Comments

@travisdowns
Copy link

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: [email protected]

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?

@jekyllbot
Copy link
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.

@travisdowns
Copy link
Author

I can still reproduce this on the master branch.

@jekyllbot jekyllbot removed the stale label Jun 30, 2019
@jekyllbot
Copy link
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.

@travisdowns
Copy link
Author

I can still reproduce this.

@jekyllbot jekyllbot removed the stale label Sep 1, 2019
@jekyllbot
Copy link
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.

@jekyllbot jekyllbot added the stale label Nov 1, 2019
@ashmaroli ashmaroli added pinned and removed stale labels Nov 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants