Custom Panels entity edit form not passing the correct langcode [#2379813]

I'm having an issue where after saving a metatag on a panelized page, it will correctly save, but upon editing again the value in the form is set to the global defaults instead of our local changes.

After some debugging, it looks like the panelized page is passing 'en' as the $langcode into metatag_field_attach_form, but the actual data is stored in 'und'. This causes the raw data to save in the $metatags array (as shown in the attached screenshot).

I don't have any multilingual modules or anything on my site, and I'm not sure where to go from here. Adding $metatags = $entity->metatags[LANGUAGE_NONE]; as the fallback condition would solve my issue, but I don't know if this would break anything somewhere else.

Any thoughts?

Comment	File	Size	Author
	debug_metatag.png	24.55 KB	bkildow

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

DamienMcKenna

NH, USA

CreditAttribution: DamienMcKenna commented 22 November 2014 at 03:25

Seeing as I'm the maintainer of both modules, I'm really interested to know why this is happening. Are you using the latest dev release of Panelizer? Have you customized the node form using Panels, or is it the normal node edit form?

Comment #2

bkildow CreditAttribution: bkildow commented 25 November 2014 at 16:08

I'm using panelizer that comes with the panopoly distribution (7.x-3.1). I just tried the dev version, and the same issue appears. I am using a customized node form using panels, close to what panoply provides. Is there a way to configure what language the form should be saved in from panels?

Comment #3

DamienMcKenna

NH, USA

CreditAttribution: DamienMcKenna commented 30 November 2014 at 15:24

Title:	Panelizer not passing the correct langcode	» Custom Panels entity edit form not passing the correct langcode
Component:	Code	» Panels integration
Issue tags:		+panopoly

I suspect the problem is in the way the custom Panels edit form is doing its work, rather than Metatag's entity handling. I'll take a look at this shortly.

Comment #4

DamienMcKenna

NH, USA

CreditAttribution: DamienMcKenna commented 30 November 2014 at 20:48

Version:

7.x-1.4

» 7.x-1.x-dev

Comment #5

bkildow CreditAttribution: bkildow commented 18 December 2014 at 16:29

I dug into this a bit more, and I think I figured out the main issue. It turns out I had the "locale" module enabled, and upon disabling this, NEW content correctly saved the metatags. Looking in the database in the node table, new content is now saved with the langcode "und". When the locale module was enabled, content was being saved with the langcode "en".

Once the locale module was disabled however, saving existing content kept whatever langcode the content was originally set to (in my case "en"), and metatags never saved.