Thanks yovanny.gomez.oyola! This patch got rid of the error on the status page about the missing fields and the related PHP error when updating to 10.3.0.
This was patched in Automated Drupal 10 compatibility fixes 📌 Automated Drupal 10 compatibility fixes RTBC
I applied 3165886-11.patch and that fixed the problem for me.
This patch does apply cleanly to 4.0.0, but caused a failure when I upgraded a site from D9 to D10.1.4. When running 'drush updb' it failed in password_policy_update_8305 at:
$config_path = drupal_get_path('module', 'password_policy') . '/config/install/password_policy.email.yml';
because drupal_get_path was removed from D10 - https://www.drupal.org/node/2940438 → .
I suppose one upgrade path would be to apply the patch to the D9 site and run 'drush updb', but the path of least resistance for me was to re-roll the patch in #39 to change the failing statement to one which is compatible with both D9 and D10:
$config_path = \Drupal::service('extension.list.module')->getPath('password_policy') . '/config/install/password_policy.email.yml';
I have only tested the patch when running password_policy_update_8305 on a D10 site but it *should* work on D9 also.
First time I have seen composer silently failing when a did a test apply of the previous patches. I had to use -vvv to see any errors. Giving it another go with a rerolled patch.
Previous patch was bad. Re-rolled.
ShaunLaws → created an issue.
The patch in #7 💬 Problem filtering first level options Needs review solved the issue that I was seeing with a 4-level taxonomy in 4.0.0 with the following settings:
Parent: (none)
Hierarchy depth: 3
Required depth: 1
I am no longer seeing the error message "The hierarchy depth cannot be 3 because the selection list has 0 levels." that I was seeing without the patch.
@liquidcms → - thanks so much for this. I am excited to see what you did :)
@liquidcms → - I know a lot of time has passed, but did you ever post your code for anonymous subscription and notification anywhere? I have a project that has the same requirements as you had. I have some thoughts about how to implement this using Message Stack and seeing your code would give a sense of whether I am heading in the right direction.