Under my install of 4.7.5, enabling Freetagger throws an error, specifically:

Type	php
Message	Missing argument 2 for variable_get() in [mysite]/public_html/includes/bootstrap.inc on line 266.
Severity	error

For my installation, removing "Freetagger" module from http://drupal.org/project/freetagger fixed it-- I was only testing this module (it's OK disabled for now) so I didn't actually go through the code to see what's up. I also had the latest versions of both that and CCK installed (along w/ a bunch of other mods :-). Some threads about diff modules, but similar probs, might be at http://drupal.org/node/112408 and http://drupal.org/node/31792 in case that helps track it down.

Comments

emilyf’s picture

emilyf commented

Mine does the same thing...only when I enable this module does this occur.

dfletcher’s picture

dfletcher commented
Priority: Normal » Critical

Remarked critical.

dfletcher’s picture

dfletcher commented
Assigned: Unassigned » dfletcher

Assigned.

AstralP’s picture

AstralP commented

I don't use this module as I am on v5 but I have just spent a few hours with tracing this error. The problem is that the variable_get needs a default variable, even if it is not required by your task. ie;

variable_get('whatever_whatever','FALSE');

so you just need to search for all instances of variable_get which don't have the second argument, or are using an empty variable. Just wasted quite a few hours on this one... hope this helps.

Rory’s picture

Rory commented

I too solved the issue by adding the missing argument so the function would send the expected number of arguments (two). Instead I added NULL (a meaningless value). For eg.

CHANGE:

'#default_value' => variable_get('default_nodes_main'),

TO:

'#default_value' => variable_get('default_nodes_main',NULL),

pomliane’s picture

pomliane commented
Status: Active » Closed (won't fix)

This version of CCK Freetagger is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.

This issue has been automagically closed by a script.