itthinx

The enterprise release is prepared for multi-tier programs.

Thanks for reporting this, although I could not get the scalar warning to appear, the plugins you mention do not add any widget controls in their panels and LWL didn’t take that into account.

I’ve provided an improved version which has just been released as 1.2.2. Please update to that version.

For further comments please preferably leave feedback at the plugin’s page here: Lazy Widget Loader plugin page.

After testing on WP 3.2.1 with Widget Logic 0.48 and Lazy Widget Loader 1.1.0 I could not reproduce the Warning. See also my comment here: http://www.itthinx.com/plugins/lazy-widget-loader/#comment-173

Looks like something else is interfering here … AFAICS the Warning is thrown because at some place the parameter is turned into a scalar when it’s supposed to be an array. So, I suppose there’s another plugin interfering …

Looks like Widget Logic assumes to use an id if it doesn’t recognize $wp_registered_widget_control[$id][‘params’][0] as an array, this is from widget_logic.php:

function widget_logic_expand_control() {

...

		if (!array_key_exists(0,$wp_registered_widget_controls[$id]['params'])  || is_array($wp_registered_widget_controls[$id]['params'][0]))
			$wp_registered_widget_controls[$id]['params'][0]['id_for_wl']=$id;
		else
		{	// some older widgets put number in to params directly (which messes up the 'templates' in WP2.5)
			array_push($wp_registered_widget_controls[$id]['params'],$id);
			$wp_registered_widget_controls[$id]['height']+=40;					// this is really a pre2.5 thing - discard?
		}

...

}

The condition to set $wp_registered_widget_controls[$id][‘params’][0][‘id_for_wl’] is a logical implication:

The key 0 does not exist in $wp_registered_widget_controls[$id][‘params’] OR $wp_registered_widget_controls[$id][‘params’][0] is an array.

and seems to be motivated to make things compatible with WP2.5? Hmmm … Lazy Widget Loader doesn’t want to be compatible with anything prior 3.0 and requires $wp_registered_widget_controls[$id][‘params’][0] to be an array. That’s where the hiccup comes up 🙂

Without digging deeper … as both plugins add their stuff to widget controls, if you let Lazy Widget Loader do it first (*) it won’t care about what Widget Logic does after, because it doesn’t get affected by it.

(*) by installing it first it get’s a chance to add its handlers before Widget Logic does