@johnnydarkko, I’m not sure if you’ve found a solution, but in my case, I didn’t need those fields, so I resolved the issue by merging the `$settings` with the default settings. I’m not creating a patch for this, as it’s probably not the best solution and may not address the issue in the long term. However, it helped me avoid those warnings:
- $settings = $this->getSettings(); + $settings = $this->getSettings() + self::defaultSettings();
@johnnydarkko, I’m not sure if you’ve found a solution, but in my case, I didn’t need those fields, so I resolved the issue by merging the `$settings` with the default settings. I’m not creating a patch for this, as it’s probably not the best solution and may not address the issue in the long term. However, it helped me avoid those warnings:
- $settings = $this->getSettings(); + $settings = $this->getSettings() + self::defaultSettings();
This fix ensures that the invitation code element is added to the webform without disrupting the existing layout or hierarchy by preserving the element structure using getElementsDecoded().
If anyone finds a more efficient or better approach, please feel free to reach out so we can review and improve the solution further.
santiagotrindade → created an issue.
Fix patch
This is the solution I have implemented to address the issue. The fix ensures that the invitation code is only marked as used when the form is actually submitted and completed.
If anyone finds a more efficient or better approach, please feel free to reach out so we can review and improve the solution further.
santiagotrindade → created an issue.