List all steps in the Quick start to clarify the process

Created on 20 April 2025, 3 months ago

Problem/Motivation

I was trying out the module, but wasn't sure how to do the final step of copying content. Using an Update Hook is mentioned, but I have no experience with those, like the vast majority of Drupal site builders also don't have.

So after creating a field updater, I wasn't sure how to do the final step of actually copying the content from a Source field to a Target field.

A Quick start should list the minimally required steps to help new users try out the module, and get started using it. To lower the barrier of entry, and be as inclusive as possible, it should not assume that the users are experts in coding.

Therefore, using Drush in the Quick start would be the preferred method to use, since almost everyone is using Drush.

Perhaps it can be added in the Quick start?

Steps to reproduce

Create a Field updater, but not sure how to do the final step of copying content from Source to Target field.

Proposed resolution

  1. Add a fifth and final step in the Quick start, using the Drush command
  2. Add a sentence below that expert users can use an update hook

Quick start

  1. Add a new field updater at /admin/config/field-updater
  2. Select: Entity type, Bundle, and Target field
  3. Select: Source field (optional) if you want to copy from an entity_reference_revisions field type (ie; paragraphs).
  4. Save the form and add mappings at /admin/config/field-updater/{id}/mappings
  5. Copy content (replace "ID") from Source to Target with drush field-updater:update ID

Expert users can also use an update hook, see next section.

Remaining tasks

User interface changes

API changes

Data model changes

πŸ“Œ Task
Status

Active

Version

1.0

Component

Documentation

Created by

πŸ‡©πŸ‡°Denmark ressa Copenhagen

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @ressa
  • πŸ‡ΊπŸ‡ΈUnited States apmsooner

    Updated steps. The module audience is generally developers but the steps are pretty simple enough to follow as is for even beginners so calling this good.

  • Status changed to Fixed 11 days ago
  • πŸ‡ΊπŸ‡ΈUnited States apmsooner
  • πŸ‡©πŸ‡°Denmark ressa Copenhagen

    I think you made it even more developer-oriented :)

    The new formulation will very efficiently block any non-developers from using the module ... I am both puzzled and sad, since as I already wrote a few times, this can be a very efficient tool for site builders who need to move data from one field to another, but who are not developers.

  • πŸ‡ΊπŸ‡ΈUnited States apmsooner

    It's extremely difficult to document "quick start" steps for variable forms and different audiences. When I get a chance, i will put together a video that truly shows how simple this module is. Even site builders should know how to create a very basic custom module that serves purpose of providing an update hook. If you think that most don't and theres not good resources out there to instruct then I will start creating videos for all these tasks we take for granted. I was a "site builder" for many years so I can certainly understand and bridge the gap. As for you, thank you for the feedback! Please get a slack account and engage with the community. Drupal could be so much better with people actually getting together and actually talking through ideas and solutions. I'd say the most frustrating thing as a developer is the sheer lack of communication from the audience using our modules. I'm personally just not gonna let issues sit in a "needs review" status or try to help someone solve a bug with no response so at least your comments here are very helpful.

Production build 0.71.5 2024