Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
When upgrading to the latest beta 6.0, meta set with context generate this error :
Notice : Undefined index: instance in DrupalTextMetaTag->getValue()
Comment | File | Size | Author |
---|---|---|---|
#13 | metatag-notice-1970064-13.patch | 2 KB | Jorrit |
#7 | metatag-n1970064-7.patch | 1.31 KB | DamienMcKenna |
Comments
Comment #1
DamienMcKennaOopsie. I'll do some testing with metatag:context next.
Comment #2
Allthegearnoidea CreditAttribution: Allthegearnoidea commentedHi
Same issue for me.
Thanks
Comment #3
Jawi CreditAttribution: Jawi commentedsame issue here after update:
Notice: Undefined index: instance in DrupalTextMetaTag->getValue() ....
Comment #4
krima CreditAttribution: krima commentedI have the same problem:
Notice: Undefined index: instance in DrupalTextMetaTag->getValue() (line 97 ..../sites/all/modules/metatag/metatag.inc).
Comment #5
StuddMan CreditAttribution: StuddMan commentedSame thing, just updated to Beta6 for the node:summary fix and getting the following error on any pages using context with the Meta Data reaction.
Notice: Undefined index: instance in DrupalTextMetaTag->getValue() (line 97 of .../modules/metatag/metatag.inc)
Comment #6
fchandler CreditAttribution: fchandler commentedSame here
Notice: Undefined index: instance in DrupalTextMetaTag->getValue() (line 97 of .../sites/all/modules/metatag/metatag.inc).
lines 96 and 97 of metatag.inc
if that helps
It happens when I click on the "Home" page (a page designated as the front), but not on other pages of the site. It does not do it on my dev site, unfortunately it does on the live site.
Comment #7
DamienMcKennaThis should fix it - all it took was moving the $instance assignment around and adding that value to the $options.
Comment #8
DamienMcKennaCommitted.
Comment #9
Jawi CreditAttribution: Jawi commentedThe latest dev version fixed this issue.
http://ftp.drupal.org/files/projects/metatag-7.x-1.x-dev.tar.gz of 2013-Apr-17
Thanks for the support!
Comment #10
DamienMcKennaNow that v7.x-1.0-beta7 is out, I'm closing this in the interest of keeping the issue queue clean.
Comment #11
Allthegearnoidea CreditAttribution: Allthegearnoidea commentedThanks for your support with this.
Unfortunately for me the notice still remains even after upgrading to the v7.x-1.0-beta7
Comment #12
jaimecarrion CreditAttribution: jaimecarrion commentedActually I got this error when I updated my install to v7.x-1.0-beta7.
Comment #13
Jorrit CreditAttribution: Jorrit commentedA similar change as #7 needs to be applied to
metatag_panels_ctools_render_alter()
in metatag_panels.module, line 88, see the attached patch.In any case, the definition of
DrupalTextMetaTag->getValue()
is erroneous. The$options
parameter has default valuearray()
, which will generate the notice.Comment #14
LaurenW CreditAttribution: LaurenW commentedI am seeing the same error with the update to 7.x-1.0-beta7. Sorry to ask a stupid question, but can someone point me in the direction of a tutorial explaining how to apply the above patch?
Thanks!
Comment #15
Jibus CreditAttribution: Jibus commentedYou can follow these instructions : http://drupal.org/patch/apply
Comment #16
DamienMcKennaCommitted. Thanks Jorrit.
Comment #17
Jorrit CreditAttribution: Jorrit commentedThanks for the commit and git attribution!
Comment #18
DamienMcKenna@Jorrit: FYI I've opened a new issue for the general problem with DrupalTextMetaTag::getValue(): #1994634: DrupalTextMetaTag::getValue() defaults to not having $options['instance'] but expects it
Comment #19
LaurenW CreditAttribution: LaurenW commented[Reply to #15]
I am not a backend developer and the instructions on that page don't really make sense to me. Is there a way to apply this patch without using command line, just FTP and CPanel access to my site? I did find some beginner instructions here http://drupal.org/node/620014 but they are for Windows and I am on a Mac.
Thanks for your help!
Comment #20
DamienMcKenna@LaurenW: All you have to do is download the current -dev version, that includes the fixes.
Comment #21
Countzero CreditAttribution: Countzero commentedStill having the issue with latest dev and latest core : as soon as I set the metatag option on any panel variant, the errors appear.
And the more info I type (title, abstract, etc.) the more notices I get.
No value is set in the META either.
Comment #22
kingfisher64 CreditAttribution: kingfisher64 commentedI'm getting quite a few of these notices with beta7. Tried the latest dev and the errors disappear. Would it be possible to have this as beta8 release as it reads +27 version.
Thank you.
Comment #23
ehalber CreditAttribution: ehalber commentedI am still experiencing the notices also. I have updated to the latest dev version. Any ideas?
EDIT: NM, I downloaded the dev to the wrong directory. I discovered my error when I was reviewing the modules page. Now it's up to 7.x-1.0-beta7+45-dev. That fixed it.
Comment #24
MustangGB CreditAttribution: MustangGB commentedThis is fixed in the latest dev.
Comment #26
pinkonomy CreditAttribution: pinkonomy commentedThe latest dev version removed this notice also for me :)