- Issue created by @acbramley
- 🇳🇿New Zealand quietone
I noticed the change record for this issue published. Since this issue not fixed I un-published it.
- 🇦🇺Australia acbramley
I don't think we should be adding
@legacy
to all those tests. The block should instead be removed from the profile and theme. - 🇮🇳India annmarysruthy
annmarysruthy → changed the visibility of the branch 3518990-deprecate-syndicateblock to hidden.
- 🇮🇳India annmarysruthy
@acbramley Can I skip deprecating the block and directly remove it? But what if the block is currently being used in sites.
- 🇨🇭Switzerland berdir Switzerland
You want to deprecate the block *plugin* and remove the block configuration from standard profile so it is no longer used.
- Merge request !11853Issue #3518990: Deprecate SyndicateBlock and remove from theme and standard profile → (Open) created by annmarysruthy
- 🇨🇭Switzerland berdir Switzerland
This also is related to 📌 Create a way to declare a plugin as deprecated Needs work . Ideally, a deprecated block shouldn't show up anymore as a possible option in the UI, but you should still be able to view and edit a block that's already placed, possibly with a warning in the UI.
We had custom logic for this for the node type visibility plugin in D8 or 9.
- 🇮🇳India annmarysruthy
Deprecated the block and removed it from theme and profile. still getting a few test failures in merge request !11835.