Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
From the linked issue:
"On my two installations, only views that had overridden the default Metatag setting are showing the Meta Tags section. Pre-existing views with no custom meta tags set, or newly created page views, do not show the Meta Tags options. This appears to be the case for sites using both the patch in #1 and the patch in #14."
Comment | File | Size | Author |
---|---|---|---|
#5 | metatag-n2353079-5.patch | 4.7 KB | DamienMcKenna |
Comments
Comment #1
DamienMcKennaSorry. :-(
Comment #2
DamienMcKennaI've confirmed the problem. Dangit :(
Comment #3
mloveridge17 CreditAttribution: mloveridge17 commentedDoes 'confirming' the problem mean that your first comment, #1 is null and that this is a bug to be fixed in 7x-1.4?
Comment #4
DamienMcKennaI've confirmed the bug exists, and that I want to fix it for the next release. I've not found a solution, neither has anyone else posted a working patch therefore I can't say when a fix will be available.
Comment #5
DamienMcKennaI believe this should work.
The problem stemmed from logic changes in options_summary() that were incorrect.
Comment #6
DamienMcKennaComment #7
pkiff CreditAttribution: pkiff commentedI'm the one whose post is quoted in the issue description. I have tested the same two installations with this newest patch, applied to metatag 7.x-1.3. This patch appears to resolve the issue in the two cases I am working with.
I have not reviewed any of the code, but just checked to see that the Meta Tags section appears correctly in the Views UI, regardless of whether that view is using default or overridden values. All looks good to me.
Thanks for continuing to work on this today, Damien. Metatags is a very helpful module, and I find it especially valuable for producing properly tagged Views pages.
Comment #8
DamienMcKenna@pkiff: Thanks for the review, hopefully we'll have some others take a look too.
Comment #9
ofry CreditAttribution: ofry commentedPatch #5 working fine! This problem has solved!
Comment #10
DamienMcKennaThanks for the reviews. I've committed the patch.
Comment #12
mloveridge17 CreditAttribution: mloveridge17 commentedI'm slower than all y'all at implementing the fixes, but I finally got it in place and it looks to be working as expected.
@DamienMcKenna Thank you so much for all of your efforts on this module. It is greatly appreciated!
Comment #13
lquessenberry CreditAttribution: lquessenberry commentedWorked for me.