Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.BrokenWebformHandler says
Broken/missing webform handler plugin
If this class can show more debugging details like
- Specify whether it is Broken or Missing
- Further details about what is breaking the plugin
it would be very helpful for the third party module maintainers who are trying to write Handlers for Webform Module.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | brokenwebformhandler-2847642-4.patch | 747 bytes | jrockowitz |
| |||
Comments
Comment #2
jrockowitz CreditAttribution: jrockowitz as a volunteer and at The Big Blue House commentedI think the broken handler's summary could include a more information. Do you have any suggestions on what should be displayed?
Comment #3
gokulnk CreditAttribution: gokulnk at Azri Solutions commentedThis could help in avoiding issues like https://www.drupal.org/node/2847639 and make debugging easier.
Comment #4
jrockowitz CreditAttribution: jrockowitz as a volunteer and at The Big Blue House commentedI copie the message from the block broken plugin.
Comment #5
gokulnk CreditAttribution: gokulnk at Azri Solutions commentedJacob Rockowitz can you quickly download and enable https://www.drupal.org/project/webform_queue module. The handler provided by this module is not listing and I am not having enough info to debug further.
I think this will be the scenario for many other developers as well. So if we can address this it would be helpful for other module developers as well.
Comment #6
gokulnk CreditAttribution: gokulnk at Azri Solutions commentedComment #8
jrockowitz CreditAttribution: jrockowitz as a volunteer and at The Big Blue House commentedComment #10
OnkelTem CreditAttribution: OnkelTem commentedI've got BrokenWebformHandler for a custom handler on our DEV instance after synchronizing configuration and wasted 7 hours already to figure our the bloody reason of its appearance. YET NO ANY CLUE. Whatever this has been fixing, it didn't help.
Comment #11
jrockowitz CreditAttribution: jrockowitz as a volunteer and at The Big Blue House commentedThere is no need be frustrated. If you post your broken custom handler on https://drupal.stackexchange.com/questions/tagged/webform someone should be able to give you a second set of eyeballs and figure out what is wrong.
Comment #12
OnkelTem CreditAttribution: OnkelTem commented> There is no need be frustrated. If you post your broken custom handler on https://drupal.stackexchange.com/questions/tagged/webform someone should be able to give you a second set of eyeballs and figure out what is wrong.
Honestly I don't need anybodies help with this because my plugin is JUST FINE. The reason why it's failed once is out of the field of my observations but that doesn't matter. The problem is that once being marked as "broken" this status didn't allow any further actions with it. Basically - you can't fix it anymore no matter what you do - it doesn't read the new version from the updated config webform entity: when saving the entity it's continuing to use the old broken version of a plugin.
Comment #13
mparker17Hello,
This thread has recently shown up on the Drupal.org administrative dashboard. We would ask all participants in this thread to abide by the Drupal Code of Conduct (https://www.drupal.org/dcoc) when engaging with others.
We expect individuals to first try to resolve conflicts between themselves in a constructive manner, asking for help when needed, in accordance with our established conflict resolution policy and process (https://www.drupal.org/conflict-resolution) to resolve their dispute.
Thanks!
Comment #14
jrockowitz CreditAttribution: jrockowitz as a volunteer and at The Big Blue House commentedI understand @OnkelTem's frustration and this issue has been resolved. #2935099: Once a webform handler is marked as broken it can not be restored.