- Issue created by @cbstuart
- Status changed to Needs work
about 1 year ago 10:02am 8 February 2024 - 🇬🇧United Kingdom scott_euser
Thanks for the patch!
Could you create as a merge request please?
Approach is okay, but could be improved by instead getting the config for the base fields as the root problem here is that the existing code is checking for added fields only, and should also check for base fields like taxonomy_term hasSo similar to
$this->configFactory->listAll('field.storage.' . $entity_type);
we should get the base fields and check if they are text, text_long, etc and add as dependants.Thanks!
Yep, completely agree. I just didn't have time to be fiddling around it. I'll take it a bit later.
- 🇬🇧United Kingdom scott_euser
All good, I'm sure your patch will already come in handy for others upgrading who use terms, so it's already a useful contribution as is :)
- Status changed to Needs review
about 1 year ago 8:44pm 9 February 2024 - 🇬🇧United Kingdom scott_euser
Nice this looks great, much smarter approach than loading from config. Will have to give this a proper test. Thanks very much for your work on this!
- Merge request !33Issue #3419898: Description missed for Taxonomy terms update → (Merged) created by scott_euser
- Issue was unassigned.
- Status changed to Needs work
about 1 year ago 12:10pm 15 February 2024 - 🇬🇧United Kingdom scott_euser
Hmmm when I run this now, the data-text attribute is empty
Steps:
- Added a fn via 3.1.x branch within a paragraph
- Updated to this issues branch
- Ran the drush command
drush footnotes:upgrade-3-to-4 paragraph
- Status changed to Needs review
about 1 year ago 12:36pm 15 February 2024 - 🇬🇧United Kingdom scott_euser
Okay got it, that works now. Turns out that
<fn value text></fn>
is also an option. Where text is on an attribute instead of within the tag. Added support for that... bit of scope creep here sorry! -
scott_euser →
committed cab1bd1e on 4.0.x
Issue #3419898 by scott_euser, CbStuart: Description missed for Taxonomy...
-
scott_euser →
committed cab1bd1e on 4.0.x
- Status changed to Fixed
about 1 year ago 12:43pm 15 February 2024 Automatically closed - issue fixed for 2 weeks with no activity.