πŸ‡―πŸ‡΅Japan @Ryo Ichiyama

Account created on 23 July 2014, almost 10 years ago
#

Recent comments

πŸ‡―πŸ‡΅Japan Ryo Ichiyama

@andikanio , @mmenavas

Thank you very much.
If I can get my environment back to normal I will try to see if I can update it without reinstalling the module.

πŸ‡―πŸ‡΅Japan Ryo Ichiyama

Hello.

I got an error in my local development environment, so I tried it in the staging environment and got the same error.

Below is the minimal YAML source.

file1:.
'#type': managed_file
'#title': File1
'#file_preview': file
'#file_extensions': 'pdf jpg jpeg png'
'#sanitize': true
'#button': true
'#button__title': Upload1

πŸ‡―πŸ‡΅Japan Ryo Ichiyama

I have seen the same logs as @greatmatters after updating Drupal Core to 10.2.
Additionally, the browser displays the attached error message.
The version of the Webform module (6.2.2) has not changed before or after the Core update.

Any hints would be appreciated.

πŸ‡―πŸ‡΅Japan Ryo Ichiyama

Thank you for responding so quickly.
I have patched and reinstalled the module and have confirmed that the warning is gone.

πŸ‡―πŸ‡΅Japan Ryo Ichiyama

Thank you so much for making the patch.

Since you made it, I would like to try it in my development environment.

I will consider using the lock function to replace the production environment operation.

πŸ‡―πŸ‡΅Japan Ryo Ichiyama

I had the same problem recently, but I found that if the target webform is used as a "wenform node" content, the memo can be used without the "ADMINISTER WEBFORM & SUBMISSIONS" permission.

I am not sure if this is the way it was designed to work, but this is how I handled it.

Production build 0.69.0 2024