alanft

unless your home page is also a category page (which I’m not sure is even possible), that’s never going to be true.

if what you want is it to be true when it is_home OR it is_category, then use OR instead, ||

then the widget will appear when the showing page is your home or when it is a category

looks ok IF you add a ‘;’ at the end of the apply_filters line

right now I can’t update the SVN to add those lines to the DEV version. i’ve just discovered that Mountain Lion doesn’t have SVN by default, and the main way to install it is to download the 1.5GB Xcode install :-/

How about a filter instead of an action and I change the crucial code in WL plugin to

foreach($widget_list as $pos => $widget_id)
{	if (empty($wl_options[$widget_id]))  continue;
	$wl_value=trim($wl_options[$widget_id]);
	if (empty($wl_value))  continue;

	$wl_value=apply_filters( "widget_logic_eval_override", $wl_value )
	if ($wl_value===false)
	{	unset($sidebars_widgets[$widget_area][$pos]);
		continue;
	}
	if ($wl_value===true) continue;

	if (stristr($wl_value,"return")===false)
		$wl_value="return (" . $wl_value . ");";

	if (!eval($wl_value))
		unset($sidebars_widgets[$widget_area][$pos]);
}

so the filter gives you the chance to step in and return a boolean value directly?

what I was getting at is you could put in your logic in the admin interface as the above without altering the WL plugin code, and that would have the same effect. Obviously you’d have to do it for each widget but it looks like you’d be putting something in the WL code anyway? (for your function to use as a param)

I could put in an action that passes through the widget logic, and then does the eval if the result is true/false – I’ll think about which makes more sense.

can i ask why you wouldn’t simply put your function in the widget logic like this:

widget_logic_eval_override('some value for my function')

which would have the effect of calling your function

I’m sorry to hear you are having problems, but I’m sorry I don’t understand the nature of the problem very well. Are you saying that the Publish button isn’t visible in the edit/add new post/page? maybe a screenshot would help, or if you like you could mail me ‘write post’ privilege only login details to your blog if you like

ok, but does the behaviour go if gantry is disabled – if so, then i have a strong clue about where to look and might have a solution

i’m trying to think of ways to help troubleshoot this.

When you save you say the field entirely vanishes – not just the content blanks but the whole text input field goes?

What happens if it’s just 2 plain text widgets – same behaviour? Same regardless of what sort of widget combinations you have, or just when using the one with the “Executable PHP widget” plugin?