Not sure whether this fully classifies as a bug or not.

I understand why a non-optional non-SRD spell being attached to homebrew prevents it from being shared, as this would make the homebrew broken for users that don't have the appropriate spell(s) unlocked.

However, if I add a Spell entry to a homebrew that contains multiple spells (enabling the user to pick one) and some are SRD, and others aren't, then this really shouldn't prevent sharing as end users can still choose from the SRD option(s) available in the list.

For example, say I add a Spell entry and in the Spell box I add burning hands and searing smite so that a player can choose which of the two they want to gain; while searing smite is a non-SRD spell, burning hands is part of the SRD, so a player who only has access to SRD content would still be able to use my homebrew (they just wouldn't be able to choose searing smite until they unlock it).

Again, not sure this really classifies as a bug or not, as it's sort of just current, flawed, behaviour. However it probably wouldn't be that hard to "fix" either; instead of blocking homebrew if a Spell entry contains any non-SRD spell, it should only block if the Spell entry contains only non-SRD spell(s) (i.e- any SRD spell in the Spell entry would make it valid for publishing).

In case the developers disagree that this is a bug and consider it to be behaving as intended, please consider voting on my feature request to have the behaviour corrected.

That is correct. If you allowed an option of all 1st-level Wizard spells it would work, but as soon as you map specific spells by name they must all be SRD or EEPC spells.

That's why it feels like a bug or fault of some kind to me; if adding a spell list (which contains a mixture of SRD and non-SRD spells) is fine, then adding your own list of choices that contains a mixture should be fine as well. At best it's an inconsistency.

It comes down to if the spells are individually mapped to the ‘brew or not.

I know why it's happening, I'm not looking for an explanation; I'm just reporting it as flawed behaviour, as it's inconsistent.

If the reason we need to use only SRD spells is because otherwise the homebrew would be broken for anyone that doesn't have the non-SRD spells we try to attach, then if a spell entry contains a mix of both non-SRD and SRD spells as options, then there's no way for the homebrew to be broken; in the worst case a user can still select from the SRD option(s) on the list, i.e- the homebrew does not require any paid content.

I've posted a feature request on the ZenDesk site anyway since it's debatable whether this a bug or not, though I'd still consider it technically a bug (the behaviours do not match, and the restriction is blocking content that it doesn't need to).