All problems solved!
After commenting out Model::shouldBeStrict(); in my project, the lazyloading error dissapeared.
The control panel problem was actually an accidental space in the dutch translati...
Hi
@Emmanuel Ingelaere, thanks for posting and working through this issue transparently, and sorry for any inconvenience it's caused in your production environment.
While the bulk of Model::shouldBeStrict() issues were solved in v0.4.6, upon a little further digging, it looks like you uncovered a bug where a lazy loading error could still occur with some particular configurations of reactions - specifically, multiple reaction sets containing only a single reaction type. I've committed a fix for this which will be included in the next release.
Thanks for your PR to fix the Dutch translation - a great first contribution!
You don't have permission to do this.
You're going a bit too fast! Take a break and try again in a moment.
Something went wrong! Please reload the page and try again.
Hi @Emmanuel Ingelaere, thanks for posting and working through this issue transparently, and sorry for any inconvenience it's caused in your production environment.
While the bulk of
Model::shouldBeStrict()issues were solved in v0.4.6, upon a little further digging, it looks like you uncovered a bug where a lazy loading error could still occur with some particular configurations of reactions - specifically, multiple reaction sets containing only a single reaction type. I've committed a fix for this which will be included in the next release.Thanks for your PR to fix the Dutch translation - a great first contribution!