- Issue created by @shenron_segamag
- First commit to issue fork.
- Merge request !6896Issue #3419074: Argument #1 ($array) must be of type array when editing node fadded condition โ (Open) created by himanshu_jhaloya
- ๐ซ๐ทFrance tabestan Sargentville, Maine
Here's a patch that works with 10.2.x.
- ๐ง๐ชBelgium wanjee
I have the same error message in 10.2.6 when I try to add a field of type "reference" or "media" to a content type or paragraph (did not test other entity types).
Patch provided in #5 also fixes this issue.
Tested. Cannot apply patch #5 (3419074-uasort-plugin-manager.patch)
Tested version: Drupal 10.3.2.- ๐ธ๐ฐSlovakia coaston
HI shenron_segamag,
I am experiencing the same issue - it was caused by uninstalling business rules which have been used as "dependent field" based on this guide here : dependent-field โ , so I had to install it back, however business rules are not D10 ready and are replaced with ECA โ .
For D10 it would be better to achieve the same with this module dependent_fields โ and this guide: guide
In my case for every content type where such "dependent" business rule entity reference is being used I am unable to edit/add once bussines rules module is not available. In content which does not have such rule everything works as expected. So looks like similar or the same issues to me.
Maybe it is different case, but at least it can help anyone else who tries to migrate from D9 to D10 and deleted all business rules but forgot to get rid of rules configured in views as entity reference.
- First commit to issue fork.
- ๐ซ๐ทFrance shenron_segamag
Hi @coaston,
Thank you, I had no idea business rules was a requirement to use dependent fields. I have already started to use ECA instead of it, but I will follow your advice to totally get rid of it.
Created a patch for version 10.3.0 , as attached #5 and the one that comes with a merge request didn't work.
For me patch in #11 fixes the exception in SelectionPluginManager, but then leads to the exception described in #6.
I think this patch ought to be a temporary solution. Believe this is isn't necessary in d11.
- ๐ฎ๐ณIndia KumudB Ahmedabad
I am not able to reproduce this on Drupal 11.x.dev version there is no error occuring while creating or editing node type with entity reference fields.
Steps to Reproduce
1. Create a Content Type- Add fields that reference other entities, such as Commerce Products or other content types.
- Allow any logged-in user to create/edit these nodes
.
2.Test Permissions:
- Ensure permissions are assigned such that non-moderator roles can interact with these fields.
3. Test Node Edit:
- Create a node type.
- Attempt to edit the node as a user with minimal privileges.
4.Check Field Configuration:
- Review the entity reference fieldโs storage and widget settings.
- Ensure the selection handler is correctly set and aligns with the referenced entity type.