There is nothing we can do about it.
LGTM
Works. Thx :)
chr.fritsch → created an issue.
Just incredible @alexpott 🥳
chr.fritsch → created an issue.
Bringing back src/SchedulerEvents.php and src/SchedulerEvent.php fixed the issue for me.
The MR is only a doc change. How could that help?
I could reproduce it locally and the problem is that .module files are not loaded before a drush updb. So the alias was not registered
I think https://git.drupalcode.org/project/scheduler/-/commit/46b1988b7e87e47188... is the commit that introduced the problem
I am using SCMI 2.x and I get that error during a "drush updb" from scheduler 2.0.1 to 2.2.0.
I am running into the same problem, but I don't understand why we would need this, because the scheduler module itself also adds the aliases.
See https://git.drupalcode.org/project/scheduler/-/blob/2.2.0/scheduler.modu...
chr.fritsch → made their first commit to this issue’s fork.
chr.fritsch → made their first commit to this issue’s fork.
Finally... Thx everyone for your patience
chr.fritsch → made their first commit to this issue’s fork.
chr.fritsch → changed the visibility of the branch 3433828-drupal-11 to active.
chr.fritsch → changed the visibility of the branch 3433828-drupal-11 to hidden.
chr.fritsch → made their first commit to this issue’s fork.
No, on production sites you don't need field_ui, because you don't change the forms displays. But you still need field_group to view the form displays.
I am facing the same with field_group 3.x. It's because of this change in core https://www.drupal.org/node/3473558 → .
I already found out how to fix it and will provide a MR.
Thanks for fixing the tests. I will review them soon. I am still concerned that this only works with the dev version of the select2 library, but there is nothing we can do about it.
chr.fritsch → created an issue.
https://www.drupal.org/project/drupal/issues/3487031 🐛 Performance Degraded after update to twig 3.14.2 Active
Since we are not using this module anymore, I am happy to welcome you as a maintainer.
chr.fritsch → created an issue.
chr.fritsch → made their first commit to this issue’s fork.
chr.fritsch → made their first commit to this issue’s fork.
chr.fritsch → created an issue.
chr.fritsch → created an issue.
chr.fritsch → created an issue.
chr.fritsch → made their first commit to this issue’s fork.
chr.fritsch → created an issue.
+1 for @alexpott's approach
chr.fritsch → made their first commit to this issue’s fork.
chr.fritsch → created an issue.
Tests are all failing. Far away from done...
chr.fritsch → made their first commit to this issue’s fork.
chr.fritsch → created an issue.
chr.fritsch → made their first commit to this issue’s fork.
chr.fritsch → made their first commit to this issue’s fork.
chr.fritsch → made their first commit to this issue’s fork.
chr.fritsch → created an issue.
chr.fritsch → created an issue.
Yes, I think getting write access for volkerk, daniel.bosen and me would be useful.
Thanks
Instead of composer.json you need to use composer.lock. That contains all installed modules. The json could only contain thunder/thunder-distribution.
Did #3
chr.fritsch → made their first commit to this issue’s fork.
chr.fritsch → created an issue.
It's not beta anymore
chr.fritsch@gmx.net → created an issue.
chr.fritsch@gmx.net → created an issue.
chr.fritsch@gmx.net → made their first commit to this issue’s fork.