Closed (fixed)
Project:
Custom Field
Version:
3.0.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
9 Dec 2024 at 19:02 UTC
Updated:
30 Dec 2024 at 04:22 UTC
Jump to comment: Most recent, Most recent file
Show commands
changes
Comments
Comment #2
apmsooner commented@giuse69, see attached screenshot for what i'm thinking on this. The checkbox would be visible if the parent checkbox on field is checked. Question I have, should the default state be checked or unchecked for new fields? I'm thinking unchecked to keep in line with how Drupal normal fields work.
Comment #3
giuse69 commentedHi @apmsooner, well, imho there is no direct comparison with normal Drupal fields since it does not have (unfortunately) subfields.
I think that if the "user may translate" option is checked, means that the overall custom field is translatable, so maybe checking also subfield is consistent, then the admin may uncheck some subfield is the translation applies only partially (i.e. to some and not all subfield).
So I am thinking something like the following:
-) first load of the form: nothing is checked
-) the admin checks the overall translation => automatically all subfields are checked as translatable.
-) the admin unchecks some subfields => no automatic action occurs
-) the admin unchecks the overall translation => automatically all subfields are unchecked, to keep the situation consistent.
How does it sound?
thanks for keeping on improving this module
Comment #6
apmsooner commentedThis is good to go. I'm merging it in and creating a new release as the last one had a minor regression bug that broke the preview in image widget.
Comment #7
apmsooner commentedThis new feature is available now in 3.0.3 release.