- Issue created by @AstonVictor
- Issue was unassigned.
- Status changed to Needs review
about 1 year ago 1:12pm 6 November 2023 - 🇺🇦Ukraine AstonVictor
Created a new MR.
Created a new submodule for taxonomy terms. It contains all other features from other issues: new permissions, block plugin, view plugin, schema config, etc.
- Status changed to Needs work
about 1 year ago 9:54am 10 November 2023 - 🇮🇹Italy aronne
@AstonVictor I don't think creating a submodule for taxonomy terms is the right choice to make.
I would rather do a work of refactoring and create a new Annotation Plugin called PrevNext which could be derived for any entity type so that we won't break the DRY principle. - 🇺🇦Ukraine AstonVictor
I guess we can refactor the module to create a new settings page for enabling prevnext links for any content entity types (nodes, taxonomy terms, comments, media items, etc).
After enabling the entity type we can render a list of bundles and other configs (enable permissions and so on) via drupal states.
It requires updating other plugins/hooks/etc and implementing permission callback to create permissions for enabled entity types.I think we will need to create a new version of the module for the updates e.g. 3.0.x
- Assigned to AstonVictor
- Issue was unassigned.
- 🇺🇦Ukraine AstonVictor
Created a new MR.
I refactored the whole module to allow users to add PrevNext links to any entity type.
Tested with content, taxonomy vocabularies, and users.It should be a new release e.g. 3.0.0
-
aronne →
committed 4fbff382 on 3.0.x authored by
AstonVictor →
Issue #3398285 by AstonVictor: PrevNext for all entity types
-
aronne →
committed 4fbff382 on 3.0.x authored by
AstonVictor →
- 🇮🇹Italy aronne
@AstonVictor the issue status is still in "Needs work".
Did you forget to change it or does it really need more work? - Status changed to Needs review
12 months ago 2:34pm 5 December 2023 - Status changed to Fixed
12 months ago 2:37pm 5 December 2023 Automatically closed - issue fixed for 2 weeks with no activity.