Closed (fixed)
Project:
Prevnext
Version:
2.0.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
1 Nov 2023 at 09:37 UTC
Updated:
19 Dec 2023 at 14:39 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #3
astonvictor commentedCreated 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.
Comment #4
aronne commented@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.
Comment #5
astonvictor commentedI 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 form 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
Comment #6
astonvictor commentedComment #9
astonvictor commentedComment #10
astonvictor commentedCreated 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
Comment #11
astonvictor commentedComment #13
aronne commented@AstonVictor the issue status is still in "Needs work".
Did you forget to change it or does it really need more work?
Comment #14
astonvictor commentedthanks
changed the status
Comment #15
astonvictor commentedMerged to 3.0.x