- 🇫🇷France mchamps Finistère
Being able to generate node on demande would be great.
I have just discovered your module and I have about 50 past submissions that I'd like to create nodes from...Great module, Thanks !
- Status changed to Closed: works as designed
about 1 year ago 10:09pm 27 April 2024 - 🇵🇹Portugal joaomarques736
Hello all,
As we have the alternative solution with content moderation, this functionality won't be in scope for this module in the near future.
Best regards.
- 🇺🇸United States helianthropy
If a community provided patch were to be offered, would it be accepted into the project? And if so, is there a preferred approach to take to add this functionality? (Any hints at where to implement would be appreciated as well.)
- 🇵🇹Portugal joaomarques736
Hi Helianthropy,
Yes, if we have a patch it can be accepted into the project. I think it could be a new operation link in webform content creator page (like "Manage fields" and "Edit").
Thanks!
- Status changed to Active
about 1 year ago 10:38pm 8 May 2024 - 🇺🇸United States helianthropy
Preparing to take this on, here is the ambitious proposal in a series of three steps. Feedback appreciated.
Proposal:
- User Interface
- Add checkbox on Webform Content Creator add/edit configuration form: “Automatically create entities.” (default to checked to enable existing functionality)
- Add "Convert Submission(s)" to Operations menu
- Add Webform submission selection page with checkboxes on each submission (indicating previously converted if field machine ID was provided), multiple select list to choose fields to display for submission identification, and “Convert to ” button.
- Code
- Update for existing webform config data to add new default field value.
- Add check for automatic creation setting before creating new entities on webform submission.
- Add route, controller, and form for submission conversions.
- Utilize Batch API since it’s possible to create long operations with on-demand bulk requests.
Planned steps
Phase 1
Add menu items and links to get started with the starting points for operations. Add forms and form updates to collect needed info for processes.
Phase 2
Add checks for default process to skip automatic entity creation if not indicated. Create connection to process on-demand entity creation.
Phase 3
Add check for previously created entities for conversion form display, revise form display as needed for UX/accessibility. Add batch support. Add update script. Explore integration with Webform submissions operations menu per issue summary.
- User Interface
- 🇵🇹Portugal joaomarques736
Hi Helianthropy,
Thanks for your help, it seems to be a good plan and it would be really appreciated if you can go ahead with it!
Best regards.
- Status changed to Needs work
12 months ago 4:06pm 14 May 2024 - Assigned to helianthropy
- 🇫🇷France mayeulk
@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? - 🇫🇷France mayeulk
@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 entityI 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