When upgrading to the latest beta 6.0, meta set with context generate this error :

Notice : Undefined index: instance in DrupalTextMetaTag->getValue()

Files: 
CommentFileSizeAuthor
#13 metatag-notice-1970064-13.patch2 KBJorrit
PASSED: [[SimpleTest]]: [MySQL] 73 pass(es).
[ View ]
#7 metatag-n1970064-7.patch1.31 KBDamienMcKenna
PASSED: [[SimpleTest]]: [MySQL] 21 pass(es).
[ View ]

Comments

Component:Code» Context

Oopsie. I'll do some testing with metatag:context next.

Hi

Same issue for me.

Thanks

same issue here after update:

Notice: Undefined index: instance in DrupalTextMetaTag->getValue() ....

I have the same problem:
Notice: Undefined index: instance in DrupalTextMetaTag->getValue() (line 97 ..../sites/all/modules/metatag/metatag.inc).

Same 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)

Same here
Notice: Undefined index: instance in DrupalTextMetaTag->getValue() (line 97 of .../sites/all/modules/metatag/metatag.inc).

lines 96 and 97 of metatag.inc

  public function getValue(array $options = array()) {
    $name = "metatag:" . $options["instance"] . ":" . $this->info["name"];

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.

Status:Active» Needs review
StatusFileSize
new1.31 KB
PASSED: [[SimpleTest]]: [MySQL] 21 pass(es).
[ View ]

This should fix it - all it took was moving the $instance assignment around and adding that value to the $options.

Status:Needs review» Fixed

Committed.

The 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!

Status:Fixed» Closed (fixed)

Now that v7.x-1.0-beta7 is out, I'm closing this in the interest of keeping the issue queue clean.

Thanks for your support with this.

Unfortunately for me the notice still remains even after upgrading to the v7.x-1.0-beta7

Version:7.x-1.0-beta6» 7.x-1.0-beta7
Status:Closed (fixed)» Active

Actually I got this error when I updated my install to v7.x-1.0-beta7.

Status:Active» Needs review
StatusFileSize
new2 KB
PASSED: [[SimpleTest]]: [MySQL] 73 pass(es).
[ View ]

A 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 value array(), which will generate the notice.

I 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!

You can follow these instructions : http://drupal.org/patch/apply

Status:Needs review» Fixed

Committed. Thanks Jorrit.

Thanks for the commit and git attribution!

@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

[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!

@LaurenW: All you have to do is download the current -dev version, that includes the fixes.

Status:Fixed» Needs work

Still 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.

I'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.

I 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.

Version:7.x-1.0-beta7» 7.x-1.x-dev
Status:Needs work» Fixed

This is fixed in the latest dev.

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

The latest dev version removed this notice also for me :)