occurrence page crashes if there are more than one occurrence field on an entity type

Amusingly I think I did have the $field_id in the path at some point and refactored it out to simplify things. I think there might be other complexities involved with having multiple fields on the same entity. Is there a particular use use case for having more than on?

> Is there a particular use use case for having more than on?

I installed the demo module and wanted to build my own event node type while referring back to the demo.

Would one field storage work across multiple node types if different settings for the date are required? I can't remember offhand whether the settings are on the storage or the field instance.

Ah! I thought you meant more than one field on the same entity type.

I'll look back at the original repo where I removed the field name from the path see what comment I made, and see if it makes sense to put it back for working out the field to load.

> Ah! I thought you meant more than one field on the same entity type.

Yup, that's what I meant.

- The demo module provides the occurrence field A on its own node type
- I made node type my_event with occurrence field B

Seems in moving the field storage id into the route parameters I'd not taking into account it was creating multiple routes (with different param values) but the same path. So opting (almost) for A putting back just the field machine name into the URL fixes this https://git.drupalcode.org/project/date_occur/-/commit/26b531bf11cb13bed...

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