🇯🇵Japan @Ryo Ichiyama

@mably
MR Works fine!
Thanks for the quick response!

@mably

Rebuilding a system from a blank environment takes time, so I did a little research.

I guessed that the difference in workflow log output between V1 and V2 that I reported was due to "webform_workflows_element.logs.inc".

For testing, I installed Ver.2 and then replaced this file with the V1 file.
As a result, my problem was resolved( But I don't know the impact on others).

I would appreciate it if you could isolate the problem.

@mably Thanks for the reply.

I have confirmed this issue with the following steps

v1.0-dev
=======
A user (TEST_TK_B09) submits an application.
An approver (113161) approves TEST_TK_B09's application.
Another user (TEST_OK_A10) submits an application.
Approver (113161) sends back the application of (TEST_OK_A10).

When the user (TEST_TK_B09) confirms his submission, the workflow log looks like the attached figure “v1.0.jpg”.
I think this is correct.

Update to V2.0-alpha2.
=============================
When the user (TEST_TK_B09) checks his submission again, the workflow log should look like the attached figure “v2.0”.
The workflow log for (TEST_TK_B09) will then also show the log for (TEST_OK_A10).

I once thought of clearing the WEBFORM submission results, but have not tested that yet.
I will try if I have something to try.

ryo ichiyama → created an issue.

ryo ichiyama → created an issue.

Thank you very much. The issue has been resolved.

Hi,

First, I found a way to reproduce the problem.
I can reproduce this problem by setting "Number of values ​​allowed" to 1.
*Please refer to "image_select_element_A.jpg".

And as you say, setting display:none should not work properly. On the contrary, I think this is related to the problem.
Setting display:none seems to apply to the area shown in the figure "image_select_element_B.jpg".

I hope this information is of some use to you.

Thanks for your reply.

I have the following modules installed on my site:

• Metatag 2.0.2
• Metatag: Mobile & UI Adjustments

Schema.org Metatag module is not installed.

Thank you very much for your verification.

The error log of my Linux server did not contain any information related to the metatag module, but after uninstalling the metatag module, it started working normally!

For reference, the error log of the Linux server is as follows.

(70007)The timeout specified has expired: AH01075: Error dispatching request to : (polling), referer: https://MYDOMAIN/admin/webform/manage/MYURLALIAS/submission/980/edit

And as you can see in your log, the memory usage of Apache & PHP-FPM increases.

If this is not a problem with the Webform module, I will close this case. What do you think?

ryo ichiyama → created an issue.

This is not a reproduction procedure, but when I put “display: none;” in the Element CSS style,
the drop-down menu is no longer displayed.

I hope this will be of some help.

I have also confirmed a similar event.

If you click on the upper left corner of the first option (image), a drop down menu appears.

I have tried with Bartik, Clalo, and Edu-x themes and the drop down menu appears in all cases.
I also used Chrome and Edge for Windows and Safari for iPhone as browsers.

I would prefer not to have the drop-down menus displayed, although I have no functional problems with them.

@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.

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

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.

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

Ryo Ichiyama → created an issue.

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.

Ryo Ichiyama → created an issue.

I am glad I could be of help :)

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.