lxg

I had the same issue today, I solved it like this: On the plugin settings page, go to the “Galleries” tab and select “Use a custom expression to apply FancyBox”. Then paste the following code into the textarea:

var gCount = 0;
jQuery('div.gallery').each(function(k, $gallery){
    ++gCount;
    jQuery(thumbnails).each(function(k2, thumb){
        var $thumb = jQuery(thumb);
        if ($thumb.closest($gallery).length)
        {
            $thumb.addClass("fancybox").attr("rel","fancybox"+gCount).getTitle();
        }
    });
});

NB: There are dozens of forum post related to this issue, however they relate to different implementations of Fancybox plugins for WP. This fix refers only to the “Fancybox for WordPress” plugin found at http://wordpress.org/extend/plugins/fancybox-for-wordpress/.

Sorry for digging up a 7 months old post, but this issue seems to bother quite a lot of people, so I thought a fix might be helpful.

Bit of an old post, but I think that there are enough people with the same problem, so I’ll just post the solution.

You must know that this behaviour is on purpose. But the solution is quite simple. Put the following code into a file named dontsearchpages.php, upload it to your plugins directory and activate it on the Plugins page of your blog.

<?php

/*
Plugin Name: Don't search pages
Plugin URI: http://lxg.de
Description: Disable searching of pages.
Version: 0.1
Author: Alex Günsche
Author URI: http://lxg.de
*/

function lxg_dontsearchpages($query)
{
	if (is_search())
		$query = str_replace
			("AND wp_posts.post_type != 'revision'",
			"AND wp_posts.post_type != 'revision' AND wp_posts.post_type != 'page'",
			$query);

	return $query;
}

add_filter('posts_where', 'lxg_dontsearchpages');

?>

Tested with WP 2.9.1 – may not work with earlier or later versions, as this is quite a dirty hack.

Inspired by an early WordPress plugin called Search Pages – which did the opposite of this one, back when WordPress didn’t search posts. 🙂

Just to support Ashley a bit … 😉 The same problem with SuperCache occurs at a customer of mine.

Use single quotes, elsewise "$foo" will output the value of the variable $foo.

Maybe the plugins eat too much memory, and/or your host has too few memory for PHP.

jnt72: This is nonsense.

The DB tables are prefixed because this allows having tables for more than one application in one database. It is merely a bonus for people who have limited hosting ressources.

The PHP functions/variables/etc. don’t have to be prefixed, as those descriptors don’t collide with other applications. And it’s up to the theme/plugin authors to prefix their descriptors, as they write code based on the core system.

Other solution would be to encapsulate the whole WordPress-thingy in a class (yes, a bit like $wpdb) and ONE single, global instance provides all methods/data. Would be a much cleaner interface imho.

Go home, kid.