Skip to content

Conversation

@wr2f25
Copy link

@wr2f25 wr2f25 commented Sep 10, 2025

As 3.5 is removing Bazaar (eprints/eprints3.5#215) we want bazaar specific stuff to be constrained as much as possible to the ingredient (in case someone wants to re-add it rather than just using ingredients).

This moves a couple of settings and the 'FileSelector' plugin as it appears to only be used by Bazaar (at least as far as Core goes).

As 3.5 is removing Bazaar (eprints/eprints3.5#215) we want bazaar
specific stuff to be constrained as much as possible to the ingredient
(in case someone wants to re-add it rather than just using ingredients).

This moves a couple of settings and the 'FileSelector' plugin as it
appears to only be used by Bazaar (at least as far as Core goes).
Copy link
Contributor

@drn05r drn05r left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like that is all the things we agreed to move to the bazaar ingredient.

@wr2f25
Copy link
Author

wr2f25 commented Sep 10, 2025

I don't have write permissions here so you will have to merge this

wr2f25 added a commit to eprints/eprints3.5 that referenced this pull request Sep 10, 2025
These settings (and this plugin) have been added to the Bazaar
ingredient as of eprints/bazaar#1 so that they can be removed from core.
wr2f25 added a commit to eprints/eprints3.5 that referenced this pull request Sep 10, 2025
These settings (and this plugin) have been added to the Bazaar
ingredient as of eprints/bazaar#1 so that they can be removed from core.
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

Successfully merging this pull request may close these issues.

2 participants