Unable to configure fields to use value revisions

Created on 27 September 2024, 2 months ago

Problem/Motivation

I am unable to get a field configured to use value revisions. I have tried several field types, including the "other (revisions)" that is available in the selection when creating a new entity reference field. After creating fields, I go to add content in them (I have tried taxonomy term references, content node references, and other simpler fields). But every time I try, I go edit new content and I am unable to get any data to show up in the value_revisions table.

Steps to reproduce

  1. Start to create a field
  2. Select entity reference field type and then choose "Other (revisions)"
  3. Finish creating the field
  4. Try creating content in that field
  5. See that data is added to the field, but that the revision is not tracked in the value_revisions table
πŸ› Bug report
Status

Active

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States MegaKeegMan

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

Comments & Activities

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

    Worked with @lelkneralfaro on this one, and we were able to sort out that creating the fields in the way I describe above does not do anything. Rather, what was missing, was that we had to

    1. go to /admin/config/search/value-revisions
    2. select the "content" check box
    3. select the field name for our regular term reference field
    4. and finally save

    I was confused initially because the first time I tried this, I selected "Taxonomy term" instead of content, but what I did not understand is that selecting "Taxonomy term" at the top opens up the list of fields that are ON taxonomy terms, and not the term reference fields themselves.

    Updating this issue to be about improving documentation in the UI.

  • πŸ‡ΊπŸ‡ΈUnited States MegaKeegMan
Production build 0.71.5 2024