This patch #3 works but it does goes through the TFA verification before redirecting. It mean that anybody asking for reset password can directly be identified if he get the reset URL.
oups here is the applicable patch for pervious comment.
I have exactly the same error message when trying to access a add content page in the admin with a user having specific role (for admin it works well).
Here is a patch. It looks like the is_null logic is_numeric are the opposite that needed.
I also take care of the non object that is mentioned in issue
https://www.drupal.org/project/domain/issues/2936697 →
We could also consider to give the option to the webmaster to delete all the entity translations for this language.
Here is a module who delete translation for entities
https://www.drupal.org/project/delete_entity_translations →
Second patch, just checking in the hook_update_xxxx if the table exist before creating it.
If the table exist we don't try to create it.
First patch to simply remove the hook_update_xxxx function.
Here is a patch implementing the solution suggested by "la vague illuminee" in comment #36.
I did a bench of test with taxonomy, media and node entities and it works.
It allows to display the "title" field where you defined it from within the "manage display" admin page.
Here is a patch implementing the solution suggested by "la vague illuminee" in comment #36.
I did a bench of test with taxonomy, media and node entities and it works.
It allows to display the "title" field where you defined it from within the "manage display" admin page.
Here is my patch proposition to finalize the implementation of this feature
Just added a code suggestion and precision on the module version used.
I had the same issue with module "Content Moderation" enabled and this fix works for me.
Needs to contrib the patch files.
Any way maybe to do a bridge to migrate to https://www.drupal.org/project/usage_data → inistead of making a new contrib module from it with the needs of Mainteners. Usage data already have mainteners and is stable with more features.
It looks like we can start to do this change.
The this method has been integrated in the Drupal core one month after this ticket has been created :)
Hi folks, @roderik @jappery
Is there any plan to do a release soon?
Just adding related issue to the right sidebar of this issue.
This patch for D9 works has expected for me.
We can configure the "Permission Policy" headers and it is added and applied.
"Feature Policy" still present and works also.
Thanks
Appologize my patch was false, I miss used the access result interface. This permission access is not a responsability of VBO. You can find information and fix on this issue https://www.drupal.org/project/drupal/issues/2949017#comment-14899806 🐛 There is no way to delete file entities of other users Fixed
The issue has been fixed and included since Drupal 10.1