Only one destination taxonomy is detected

Created on 27 January 2024, 11 months ago
Updated 10 February 2024, 11 months ago

Steps to reproduce:

  1. Create a new taxonomy vocabulary.
  2. Go to the content type settings form.
  3. Check only Tags vocabulary can be selected.

Expected behaviour:

Any vocabulary can be selected as destination

🐛 Bug report
Status

Fixed

Version

1.0

Component

Code

Created by

🇪🇸Spain alvar0hurtad0 Cáceres

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

Comments & Activities

  • Issue created by @alvar0hurtad0
  • First commit to issue fork.
  • Status changed to Needs review 11 months ago
  • daniel_mm02 Burriana, Castellón

    The error was that it was not necessary to create a vocabulary for each taxonomy; instead, it was necessary to create a taxonomy for each vocabulary so that Autotagger could correctly identify it in the "Destination fields" field. I attach screenshots below where you can see the process for it to work correctly.

  • Status changed to Fixed 11 months ago
  • 🇪🇸Spain alvar0hurtad0 Cáceres

    Thanks.

    Looks good.

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024