- Issue created by @joaopauloc.dev
- Merge request !127Adding field_ui.field_add_eventinstance route into the excluded route in compute fields. → (Open) created by joaopauloc.dev
- 🇧🇷Brazil joaopauloc.dev
Hi folks.
First of all, great module!!! good job.
This module saves me a lot of time.With the fixed applied I was able to add the fields as expected.
Take a look at the image below. - 🇧🇬Bulgaria pfrenssen Sofia
Thanks for the report! I can replicate the error.
However it is not the right solution to start maintaining a potentially unlimited list of routes that might at some point in the future decide to compute the availability on a new or orphaned event instance.
What is the root of the problem is that the registration creation service expects a fully populated event instance (including referenced event series):
/** * Set the event entities. * * @param \Drupal\recurring_events\Entity\EventInstance $event_instance * The event instance. */ public function setEventInstance(EventInstance $event_instance) { $this->eventInstance = $event_instance; $this->eventSeries = $event_instance->getEventSeries(); }
We should here throw an
\InvalidArgumentException
if an event instance is passed that is missing an event series. And on the calling side we should probably avoid calling into::setEventInstance()
if the entity is new. - Merge request !131Do not attempt to calculate attendance related values on unsaved event instances. → (Merged) created by pfrenssen
- 🇧🇬Bulgaria pfrenssen Sofia
I added a new MR with my proposed fix. @joaopauloc.dev does this also solve the problem for you?
- 🇧🇷Brazil joaopauloc.dev
hey @pfrenssen.
I agree with you regarding the route stuff.
I tested your merge request, and it works.
Thanks.
-
pfrenssen →
committed 400e300b on 2.0.x
Issue #3483283 by joaopauloc.dev, pfrenssen: Unexpected error when...
-
pfrenssen →
committed 400e300b on 2.0.x
-
pfrenssen →
committed 400e300b on 3.0.x
Issue #3483283 by joaopauloc.dev, pfrenssen: Unexpected error when...
-
pfrenssen →
committed 400e300b on 3.0.x
Automatically closed - issue fixed for 2 weeks with no activity.