Needs review
Project:
Task
Version:
8.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
5 May 2020 at 01:16 UTC
Updated:
6 May 2020 at 18:46 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
trobey commentedComment #3
trobey commentedI discovered upon making my browser window taller that there are flyout menus under the Structure menu. These do not appear if you click on Structure which just has a link that leads to an empty form. It was not possible to make the window tall enough for the flyout menus to be usable and this is likely the case for many people with either a somewhat complex website or not using a large monitor. This is almost everybody. This also does not follow how Drupal core and popular contrib projects are organized. So I am updating the patch so it preserves existing functionality but places it in the standard places and makes the links usable.
First, under the structure menu there should be a link to modify the structure for the Task entity. This menu is not suitable for lots of links so that is the only link there. This makes the functionality similar to the content types provided by core.
Everything else is moved under the Configuration menu. This provides for subsections for settings where multiple links can appear. The task closure reasons and tasks statuses appear under the task subsection. The task list also appears here. I put a link in the Extend menu under enabling the task module that goes to the task settings. There really is no documentation for this project so this link is a hint for where to start and the task list can be found through that link. Once documentation is written the link for the task list should probably be removed.
The task list should actually appear under Content similar to comments, files and media. Click on the Content link and it shows all the node content and tabs for content for other entities. I added a task tab here since that is where someone would look for task content.
This fixes the menus so that they are usable and follows standard Drupal conventions. There were other people that gave up trying to use this project because they could not find anything and could not get it to work. I had to write code to get this project to work since it was not possible to access or even know about the links provided in this project. Of course, documentation would also be nice but if things are put in the standard places there is some hope for figuring out how to use this project.