- Issue created by @lazzyvn
- Assigned to abhishek_virasat
- Issue was unassigned.
- Status changed to Needs review
4 months ago 11:06am 4 March 2024 - last update
4 months ago 130 pass - 🇮🇳India abhishek_virasat
created patch as per above proposed resolution and it works. please kindly review the patch file.
- 🇩🇪Germany diqidoq Berlin | Hamburg | New York | London | Paris
Thanks for the report! Can this be caused by changes from last 4.x dev issue commits? Can you review them here?:
- ✨ Support for Inline Entity Form Fixed
- ✨ Compatibility with shs module Needs review
And is this creating a WSOD or making the site not working? If yes feel free to raise the issue priority again. Otherwise: Descriptions of the Priority → and Status → values can be found in the Drupal project issues → documentation.
- 🇫🇷France lazzyvn paris
No, I don't think so, that happens with the new settings module as well, The developper is not attention to #after_build. The EntityDisplayRepositoryInterface (injection dependency) was recently added. before it call drupal service so that's why we don't have any trouble.
- Status changed to Postponed: needs info
4 months ago 12:15pm 5 March 2024 - 🇩🇪Germany diqidoq Berlin | Hamburg | New York | London | Paris
Thanks for coming back on this and your efforts in here! +1 Very much appreciated. I was asking because of we both are no native tongues :) and you have mentioned "dev" in the issue summary shortly without further details. So, do I understand correctly, that you refer here rather to core dev? Could you please try to rephrase the issue summary a lit bit so that it is better understandable what it is about? That would help a lot because it still reads somewhat confusing... Thank you.
And can you please review the patch provided regarding your reports intention?
Great finding and thanks for the report! +1
- 🇫🇷France lazzyvn paris
please check the debug in the attached file, you will see what is happening
i debug from return \Drupal::service('conditional_fields.form_helper')->afterBuild($form, $form_state); - Status changed to Needs work
4 months ago 2:02pm 5 March 2024 - 🇩🇪Germany diqidoq Berlin | Hamburg | New York | London | Paris
Thank you! Please keep posting. I viewed the image before already but I haven't seen an error there popping up. What do you mean by you have debugged. In your IDE? So this error is not thrown in Drupal but only in your debug environment?
EntityDisplayRepositoryInterface has been introduced with Drupal 10.1 so it is not that new, so I am not sure what has caused this in your case and I sadly cannot reproduce it at the moment in a Drupal install. I will take a look at it in your IDE and will try to reproduce your debug experience.
I actually wanted to make a beta release start of this week. But now I hesitate.
- 🇫🇷France lazzyvn paris
I have case it create alots of bug in dev version (not in 4.0.0-alpha5 version)
could you install state machine → or Field States transitions → .
- Active conditional_fields in widget (form manage)
- Now in the formatter (display manage) you can select formatter type form transitions, after that, site crashes.
That means that if there is a form in the formatter (not with the widget in the form view), the conditional fields will get a lot of errors (90% with new added dependency injection in dev version)