I'm also faced with this issue and the forms i'm using have a lot of text format fields on them.
I noticed a similar permission error when upgrading from 4.0.3 and realised due to the extra permission checks introduced in 4.1.0 I had to tick off the 'View own webform submission' permission for the role.
This was due to the extra check in 'WebformSubmissionResource.php' to view the submission. I also noticed there's an error in the comment:
// Check user have permission to delete webform submission.
should be:
// Check user have permission to view webform submission.
Yes I can confirm this fixes the issue. Thanks.
It’s a plain image old image field.
I upgraded from 2.5 so appreciate there have been a lot of changes since then. However the bundle class always appears to be null.
Same happens for me. Downgrading fixes the issue.
Realised it was a permission issue.
This doesn't quite work multi valued views as 'Add new item' gets added as a new entry.
Ok, I've realised its a custom theme issue.
However I've switched to a default Olivero theme which displays the 'Add another item' button fine, but when I try an delete or update an existing value and click update, it automatically adds 'Add another item' as a new entry?
It's a conflict with the rules mode: https://www.drupal.org/project/rules/issues/3279526 →
Any update on this one?
Additional steps to reproduce based on the YAML above:
1. Click yes to 'Display name' field
2. Enter info for 'Test field'
3. Click next and you can proceed to the next page without uploading a required document in the 'test upload' field and no validation warning is shown.
I have experienced this issue as well with a long multi step form using the iframe resizer embedded on another site.
This causes a problem in the use case i've got.
I'm using the webform rest module to trigger a get submission on PostSave but it always get the previous data as it hasn't been committed to the database yet.
rviner → created an issue.
This caused our multi step ajax form to get completely stuck.
Patch resolved the issue.
This is still an issue in version 2.0.
I can't share the webform settings but get this error with a simple multiple step form with ajax turned on and draft submissions enabled.