uberhacker → created an issue.
@cilefen: Applying that patch exposes this error. Whack a mole?
Refactored #38 for 10.3.0.
Possible solution?
Not sure what the logic is behind a default sort by order of execution. I'm seeing the taxonomy terms at the bottom and user migrations all over the map in my migration status list. These should be near the top for dependency precedence "order of execution" to make sense. Sorting alphabetically helps when viewing a long list with similar migration ids. It would be ideal to ultimately add an option to sort by any table column. The groundwork is included in the attached patch.
benjifisher → credited uberhacker → .
uberhacker → created an issue.
I noticed there was an error when attempting to access the logs. The attached patch fixes `Symfony\Component\HttpKernel\Exception\ControllerDoesNotReturnResponseException: The controller must return a "Symfony\Component\HttpFoundation\Response" object but it returned a string ("Bad Behavior is not installed correctly. See the README.txt for installation details.")`. Please disregard the earlier patch.
Attached is a patch for Drupal 9/10 compatibility. To install @bmunson's Drupal 8 port and apply this patch, do the following:
Edit composer.json and add...
"repositories": [
{
"type": "package",
"package": {
"name": "bmunslow/drupal8-badbehavior",
"version": "dev-master",
"type": "drupal-module",
"extra": {
"installer-name": "badbehavior"
},
"source": {
"url": "https://github.com/bmunslow/drupal8-badbehavior.git",
"reference": "master",
"type": "git"
}
}
}
],
...
"extra": {
"patches": {
"bmunslow/drupal8-badbehavior": [
"patches/badbehavior-d10.patch"
]
}
},
Do not replace the entire repositories and extra sections but add if there are already existing repositories and/or patches.
Then run:
composer install
Ideally, these changes should eventually go into a 9.x branch in this project but this is a workaround until the maintainers have the time and willingness to update.
It didn't work for me but with the attached patch, it works. To apply the patch, add the following to your "patches" section in composer.json and then run composer install.
"patches":{
"drupal/node_export": {
"Entity queries must explicitly set whether the query should be access checked or not": "https://www.drupal.org/files/issues/2023-12-19/3407066-entity-query-access-check.patch"
}
},
Attached patch...
uberhacker → created an issue.
Although DDEV definitely has some nice features and is easy to use, I have to say it certainly has some shortcomings. I have been using Lando for several years and although it is missing some features that are available in DDEV, I find it more flexible in many regards. I consider this more valuable than baked in features because of the potential for future growth. While it would be nice to have one solution to rule them all, I think "competition" between projects is healthy and can foster improvement in each project overall. That said, I'm not really in favor of making any project "official" because that just elevates one above all others.
uberhacker → created an issue.
Since D8 is now EoL, it makes sense to port to D9/10. Is there any interest in this effort? The current D8 branch codebase looks like it was abandoned 2 years ago.