My observations so far suggest that the sort order for similarly named terms are likely one of these
Term ID (asc)
created at (asc)
machine name (asc)
position on the taxonomy term page (desc)
jonsimonsen → created an issue.
I added a patch for Gutenberg 2.9 based on the current merge request
Tested it on a project where Gutenberg wasn't loading and the Javascript tab in developer tools showed this message
<br/><b>Warning</b>: Undefined array key "drupalmedia/drupal-media-entity " in <b>/var/www/html/web/modules/contrib/gutenberg/src/Controller/BlocksController.php</b> on line <b>119</b><br />
I did not observe any issues afterwards. I do see that GB 3.0 is structured somewhat differently so one of the files in the MR is not present in GB 2.9.
So I'm not so used to working with issue forks. Is it possible to create one here for GB 2.9, or will that require an entirely new issue to be created?
I did not see a button for creating a new issue fork here at least
There is no "Media" in the GB blocks. Note that I did not upgrade to 3.x yet (the original post implied that there are issue on both 2.x and 3.x). I can try the upgrade and see how it looks afterwards
So from what I can see, the log message appears immediately when going to add new content that is set up with GB. I've still not seen anything that is obviously broken in the editor. The issue seems to have appeared after upgrading to D10. I don't see similar messages on the D9 version of the site.
I'm seeing the same message when adding new content that use GB. We had a custom module with some GB blocks, but the message still appeared when that module was disabled.
My project is set up with Gin as admin theme. I'm not sure if that should have anything to say, but I noticed that gin_gutenberg is currently not installed. I'll just test if that makes any difference
Fixed #3. Not sure if there is a standard way to refer to a comment in the commit message here, but I apparently followed a non-standard way of referring to the issue.
I also figured out that I'll remove the module from gitignore next time I work on something like this so I can see directly on the test project what changes have been made and revert them back afterwards.
jonsimonsen → created an issue.
For the record, I tested this fix on my local setup. The previous behavior of exporting empty files that should not get exported into the default sync directory (because they were in a dev split) did indeed get fixed. Thank you, https://www.drupal.org/u/bircher →
bircher → credited jonsimonsen → .
The link to the Norwegian-English word list under "Be consistent" points to a page that seems to have been deleted or moved.