Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
hi all.
i've just noticed a problem with title and taxonomy fields.
steps:
- i have title module enabled with default configuration (no checkboxes in
Administration › Configuration › Content authoring › Title settings
). - let's now create a new vocabulary:
Administration › Structure › Taxonomy › Add vocabulary
: "Example vocabulary". - now, in
Administration › Structure › Taxonomy › Example vocabulary › Manage fields
i have default name and description machine names automatically replaced with field_name and field_description.
actually, i would expect this behavior with name and decription checkbox checked in Administration › Configuration › Content authoring › Title settings › Taxonomy term
.
another issue i've noticed is that, with field_name instaed of name, i only have blank terms all around the administration ui (starting from Administration › Structure › Taxonomy › List
).
am i missing something?
thanks a lot.
Comment | File | Size | Author |
---|---|---|---|
#7 | 1938216-7-entity-empty-fields.patch | 729 bytes | adriaanm |
#5 | entity-translation-configuration.jpg | 125.6 KB | adriaanm |
#5 | title-configuration.jpg | 62.63 KB | adriaanm |
#5 | create-term.jpg | 70.26 KB | adriaanm |
#5 | empty-list.jpg | 39.83 KB | adriaanm |
Comments
Comment #1
plachBlank field values will appear if you replace fields, make them transltable but not enable taxonomy translation in the ET settings. I cannot reproduce the other issue on the latest dev, please provide the exact steps to reproduce it on a clean D7 installation.
Comment #2
plachComment #3
lorenx CreditAttribution: lorenx commentedhi and thanks for your reply.
i don't have a clean drupal installation at the moment.
try this scenario first, i'll set up one if needed.
enviroment:
steps:
this happens even with taxonomy translation module disabled.
Comment #4
lorenx CreditAttribution: lorenx commentedi can confirm this seems a bug to me.
steps:
i would expect this behavior enabling the automatic field replacement feature for name and description in the taxonomy term section, not in the node one.
should i use the dev version? is it safe enough?
thank you for your attention.
Comment #5
adriaanm CreditAttribution: adriaanm commentedI reproduced this issue using a sandbox environment on simplytest.me. Please follow these exact steps to reproduce the issue:
This behavior only occurs when using the Title-module.
Comment #6
plachWow, great report, thanks! I think I'll start using it as an example of how things should be done ;)
I'm pretty swamped these days but I'll try to have a look to this ASAP.
Comment #7
adriaanm CreditAttribution: adriaanm commentedI found out that when you skip reverse synchronisation when inserting an entity in a different language than the active language, the fields are not empty anymore - patch attached.
The title_entity_presave part is quite confusing, since the langcode-variable is used to determine the entity language, the active language, and also as a boolean to check if reverse synchronisation needs to be performed...
Can you take a look at this part and maybe check how it can be re-written?
Comment #8
plachMmh, this might be a duplicate of #1991988: Adding a new translation overwrites the English/source field value. Can you check if we are talking of the same problem just with different symptoms?
Comment #9
adriaanm CreditAttribution: adriaanm commentedI tried reproducing that issue without success. Next I've applied the patch from #8 of #1991988: Adding a new translation overwrites the English/source field value, but that doesn't resolve the problem described in this issue.
Comment #11
plachSorry, it's difficult even for me to wrap my mind around these issues. That part of code is simply tricky :)
I need some time to understand what's going on.