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

Value element is ignored when set on the <item> (episode) level #161

Open
dergigi opened this issue Jul 7, 2021 · 1 comment
Open

Value element is ignored when set on the <item> (episode) level #161

dergigi opened this issue Jul 7, 2021 · 1 comment

Comments

@dergigi
Copy link

dergigi commented Jul 7, 2021

I believe that setting up a value-split on a per-episode level is not supported by Sphinx yet, even though it is defined in the specification.

Quote from the <podcast:value> spec:

<podcast:value
    type="[cryptocurrency or layer(string)]"
    method="[payment transport(string)]"
    suggested="[payment amount(float)]"
>
[one or more "podcast:valueRecipient" elements]
</podcast:value>

This element can exist at either the <channel> or <item> level.

The value tag, when it exists at the <channel> level, designates the payment scheme for the entire podcast. When it exists at the <item> level, it is intended to override the channel level tag for that episode only.


Please let me know if my assessment is correct. I've experimented with various feed setups and looked through the code, and as far as I am able to tell this feature is simply not implemented yet. It's always possible that I'm wrong though and something is wrong with my feed.

Keep up the great work everyone 🧡

@dergigi
Copy link
Author

dergigi commented Jul 14, 2021

It seems that the specification is not truly final yet, so I might have spoken too early.

I will help move Podcastindex-org/podcast-namespace#116 forward and loop back to this as soon as the spec is final.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant