- Issue created by @mortona2k
- 🇺🇸United States mortona2k Seattle
I can see a Metatag field handler in 1.4, but not 2.x. Is that still in progress?
- @mortona2k opened merge request.
- 🇺🇦Ukraine nginex
2.x is outdated and does not contain all the changes from 1.4.x.
2.x will be updated and released when all the todos are finished for 1.4.x
Makes sense to fix it in 1.4.x, and then backport patch to 1.3.x
- Status changed to Needs review
10 months ago 4:27pm 23 August 2023 - First commit to issue fork.
- Status changed to Needs work
8 months ago 8:54pm 20 October 2023 - 🇺🇦Ukraine abramm Lutsk
There are a few comments in the MR, moving to Needs work.
- Assigned to abramm
- Status changed to Active
8 months ago 1:09pm 27 October 2023 - Assigned to nginex
- Status changed to Needs review
8 months ago 1:15pm 27 October 2023 - 🇺🇦Ukraine abramm Lutsk
The comments are actually handled already, it's just GitLab not showing them as not resolved since there was no maintainer's response.
Moving it back to review for @nginex. -
nginex →
committed 807ffc5d on 1.4.x authored by
mortona2k →
Issue #3382913: Support Metatag 2.0 json storage
-
nginex →
committed 807ffc5d on 1.4.x authored by
mortona2k →
- Issue was unassigned.
- Status changed to Fixed
8 months ago 3:18pm 27 October 2023 - 🇺🇸United States bdanin
When will a new release be created that incorporates this fix? I have run the dev-1.4.x version of the module and it works, so it would be really nice to have an official release and not run the dev version in production.
- 🇺🇦Ukraine abramm Lutsk
There's nothing special in dev vs tagged release, 1.4.x is not unstable version or something; there's no tagged release with this feature yet as we don't feel there are enough remarkable changes to create a new one and urge people to make fairly unnecessary upgrade.
I'd suggest just keeping a dev version or, if your company or project policy forbids it, applying a patch from MR on top of latest tagged release.
- 🇺🇸United States bdanin
The 1.4.3 version simply does not work for me in my Drupal 10 site. The dev version does. I don't understand how a module not working vs. actually working isn't a big enough change to warrant a new release.
To me, this represents a very remarkable change and it would be great if there was a new version. It will likely help others not have to track down this issue and then apply patches or change to a dev version of the module as well.
- Status changed to Fixed
8 months ago 5:35am 8 November 2023