Closed (cannot reproduce)
Project:
Webform
Version:
8.x-5.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Feb 2021 at 12:23 UTC
Updated:
29 Jul 2021 at 15:18 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
jrockowitz commentedI am not able to replicate this issue.
Below are my steps to review this functionality
file_managedtablefile_usagetable with a count of 1Below is the test for this functionality.
\Drupal\Tests\webform\Functional\WebformEditorTest
All the code that is handling this functionality is in webform/includes/webform.editor.inc
Comment #3
berdirThis is not for a confirmation message, it's the separate "Advanced HTML Element" that you add like a form element. I think it was nested in one or likely even multiple container-ish elements.
Comment #4
berdirAlso, as always I didn't expect you to be this fast and dedicated in checking this :)
Mostly, I just created this so that it's "documented", as it came up in a client support ticket and I found those forgotten comments in the referenced issue.
If it becomes an important thing for us that we want to have fixed or get paid to do so we're happy to look into it ourself :)
Comment #5
berdirYeah, so this element is inside a fieldset inside a flexbox inside a wizard page. Because why not ;)
Comment #6
jrockowitz commentedThere should be test coverage for that too. I can do a quick manual test later.
Comment #7
jrockowitz commentedThe same steps work as expected using the attached webform.
I am using Drupal 8.9.x and Webform 8.x-5.x
Comment #8
jrockowitz commentedThe attached webform tries to mirror the example from #5 but I still can't replicate this issue.
If we can replicate this issue, it is a major or critical issue because of the data loss.
Comment #9
berdirI'm not sure. I've definitely seen the result on the client site, with broken images that point to the deleted files, but I didn't try to reproduce, we did some workarounds there for now.
I will need to see if I can reproduce it somehow. Only idea that I have left atm is that it might be related to translations? This is a multilingual site.
Comment #10
jrockowitz commentedMarking this as postponed until we can reproduce this issue.
Comment #11
jrockowitz commentedI am going to change this to cannot reproduce. Please reopen this ticket if the issue can be reproduced.
Comment #12
bburg@Berdir, Do you happen to have a Content Security Policy enabled on the site where you were seeing this? I was getting the same report from a client, with images uploaded to text elements in webforms, having their status as "Temporary", then being purged. I checked the logs, and saw these CSP violations:
I'm not sure what the document uri is about, this particular site doesn't have an /about page, and I never visited that URI, but these did seem to coincide with the testing I was doing on the webform. I checked the "unsafe-eval" option for script-src in the CSP settings, and I was about to save a webform with an uploaded image in a text field with the status set to permanent. Enabling the unsafe-eval option globally isn't ideal, but this is a similar issue I've seen before #3164287: Paragraph module content with edit mode "closed" break CKEditor.
Comment #13
jrockowitz commentedI think this might have been addressed via #3218296: Inline image is stored as temporary file again
Comment #14
bburgI think you are right, and I just hadn't cleared a cache or something.