We have Metatag 7.x-1.21 installed on a Panopoly 7.x-1.38 distribution (Drupal 7.44, Token 7.x-1.6). After enabling Metatag, everything looks good. If we try and enable any other Metatag module (like Metatag Panels) we see the following on the status report and Tokens stops working properly:

The following tokens or token types are missing required name and/or description information:

$info['types']['date']
$info['tokens']['node']['url']
$info['tokens']['file']['size']
$info['tokens']['user']['url']
$info['tokens']['date']['custom']

The following token types are not defined but have tokens:

$info['types']['node']
$info['types']['term']
$info['types']['vocabulary']
$info['types']['file']
$info['types']['user']
$info['types']['current-user']

Disabling the enabled module puts everything back to normal. This doesn't happen if we enable some non Metatag provided module. Only those that came bundled with Metatag.

Any help would be greatly appreciated.

Comments

abcto created an issue. See original summary.

abcto’s picture

After a lot more testing and looking at the code, I am now convinced that the issue is not with Metatag at all. Further research indicates that other modules have fallen victim to this exact same issue and symptoms and some test showed that it may be caused by problems with APC. I've made some changes to my apc.ini file to try and eliminate problems with Drupal being unable to allocate pools (this was recommended by several others that were plagued with the warning messages).

I will do some further testing and monitor whether the problem only occurs after the pool allocation failure warnings occur.

DamienMcKenna’s picture

Category: Bug report » Support request
Priority: Major » Normal

I'm happy to hear you've at least partly worked out where the problem is coming from, please keep us posted on what else you find out, it might help others.

abcto’s picture

The problem definitely is related to the issues with APC. The original information about the APC issues was found at https://www.drupal.org/node/1154448. It does appear that you have to experiment a bit with the settings to find ones that will work for a particular configuration but once you eliminate the underlying issue, everything behaves as it should.

This issue should be closed.

DamienMcKenna’s picture

Version: 7.x-1.21 » 7.x-1.x-dev
Component: Miscellaneous » Documentation
Category: Support request » Task

@abcto: Good find, thanks. Lets add a Known Issue to the docs for this.