When Recurring Events is enabled alongside Admin Toolbar, the user may hover over "Content" in the tool bar and see options for Events (links to add event and view series/instances/registrants).

If the user happens to not have Admin Toolbar installed, there is no easy way in the UI to add or view events, they must go directly to those pages via URL.

Some possible solutions:
1. Add blue "+ Add Event" button to top of /admin/content. And/or have a link at the top of this page that says something like "Go to Events" that would take you to admin/content/events
2. Allow events to show up in the content list of /admin/content alongside the rest of the site content to view. (Similarly, is it possible to have the custom content types show up as options at /node/add?)
3. Add a tab at the top of /admin/content for "Events" that could potentially display the content on admin/content/events. Or, this tab could show all of the event nodes in a list (much like on /admin/content) with a blue button link for "Add Event" at the top.

Comments

pjudge created an issue. See original summary.

owenbush’s picture

Thanks for submitting this. I'll take a look and see if I can get this resolved. Or feel free to submit a patch if you want.

I like the approach of #3 as I think that follows the standards set by other entities like files and comments.

owenbush’s picture

Status: Active » Needs review
StatusFileSize
new7.24 KB

I have put together a patch to resolve the issue if the admin toolbar is not enabled. @pjudge please take a look and see if this resolves your issues. If it does, then set the issue to 'Reviewed & tested by the community'.

pjudge’s picture

I've applied this patch to the module on a new install of Drupal 8.7.8. I love the tabs. Easy to use and works as expected.

pjudge’s picture

Status: Needs review » Reviewed & tested by the community

  • owenbush committed 8d93871 on 8.x-1.x
    Issue #3069520 by owenbush, pjudge: Difficulty accessing events when...
owenbush’s picture

Status: Reviewed & tested by the community » Fixed

Awesome, thank you @pjudge. I've merged and committed this patch to the 8.x-1.x dev branch.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.