🇫🇷France @mayeulk

Hi,
Are those automated patches enough to make this compatible to Drupal 11? If so, can they be merged?

@stephenplatz
You wrote (March 2022 at 16:28):
"Until there is a better way, using content moderation, we've set the default moderation state on the generated node content to draft"
Please, how do you achieve this?

Here are the options I can see at https://www.irnc.fr/fr/admin/config/webform_content_creator/my_content
[x] Synchronize the creation/edition of content based on unique content field
[x] Synchronize Webform submission with the created content in edition
[_] Synchronize Webform submission with the created content in deletion
Synchronization field machine name: field_webform_sync_id
[_] Redirect to entity

I checked the first two. I cannot see "set the default moderation state on the generated node content to draft"

You wrote: "which allows for staff to edit and or approve content before it's published."
Anyway, this seems hard to make it compatible with our workflow, as we want webform respondants to be able to edit their entries even after submission. That is: an editor sees the submitted values, and asks a respondant for clarification and/or corrections. Once the corrections have been made (on the webforms), the editor validates them for publication. This implies that, for each specific submission, the editor needs to be able to freeze (and possibly unfreeze) the submission; in effect, the freezing should be done before the reviewing process starts (we have multipage submissions; we do not want the editor to review page 1, then page 2, then having the respondant edit page 1 while page 3 is being reviewed by the editor). My workaround for this use case is to change the ownership of the webform submission (using the Webform module function, described ate https://www.drupal.org/project/webform/issues/2865100 → ).
This has severeal shortcomings:
- need to record the name of the original respondant (I use webform submission administrative notes for this).
- tedious (several clicks).
- Once a submission is validated and published, there is no process to allow the original respondant to make suggestions to change it again (if further corrections are needed) while disabling these suggestions to be published instantly. (I I uncheck the sync options, the other submissions will not be synch'ed any more).
I have the impression that, without "allow manual validation" (on a case by case basis, allow or disallow sync from webform submission to node), the above cannot be solved. Any hint?
Thanks,
Mayeul Kauffmann

@cecelias I can see at your drupalcode page
https://git.drupalcode.org/Helianthropy
that you "pushed new branch 3082093-manual-entity-creation at Issue forks / webform_content_creator-3082093"
(but I failed to find code commits). Is there some progress on this?

Hi,
Which Drupal version are you using? I got entity created, using Drupal version 10.4.6

For me, I can confirm that the sync works only one way (from webform to entity). Using webform_content_creator Version : 4.0.9 on Drupal 10.4.6.

Install TCPDF

I second the suggestion to include a comparison of these. In particular, is one of them working better with Drupal webforms?

fix typos

Hi. Apparently I'm facing this bug with:
$ drush st
Drupal version : 10.3.7
DB driver : pgsql
PHP OS : Linux (Docker container)
PHP version : 8.3.11
Drush version : 13.3.2.0

I had to uninstall markdown module (which was not working anyway), through the admin GUI then with :
composer remove drupal/markdown
composer remove league/commonmark:^1
drush cache:rebuild

Is there a way that I can get both drush and markdown working?

Hi. I needed a short code to get all submissions, as a text-based backup (to be able to verify that submissions are correctly saved). I do this, with PostgreSQL:

pg_dump --dbname=postgresql://postgres@127.0.0.1:5432/postgres > /home/myself/backup/drupal_pg_backup.sql

cat drupal_pg_backup.sql | grep ^my_second_webform_survey > results.csv

where 'my_second_webform_survey' is the URL name of the survey I need.

If you do not need the full sql backup, this works too:
pg_dump --dbname=postgresql://postgres@127.0.0.1:5432/postgres | grep ^my_second_webform_survey > results.csv

This gives the content of the public.webform_submission_data table (note there are other webform tables)
The headers are:
webform_id;sid;name;property;delta;value
Similarly, you could get some of the other tables; for instance, the public.webform_submission table has these fields:
sid,webform_id,uuid,langcode,serial,"token",uri,created,completed,changed,in_draft,current_page,remote_addr,uid,entity_type,entity_id,"locked",sticky,notes