Plugin: search reloaded

Bug report:
posts_per_page can be set to -1. If this is the case, search reloaded creates an invalid LIMIT clause in sql queries.

I hard-coded an override in mine:
after:

if ( !$posts_per_page )
$posts_per_page = get_settings('posts_per_page');

I added:

if ( $posts_per_page == -1 )
$posts_per_page = 18446744073709551615;


In reality, if posts_per_page is set to -1, there should be no LIMIT, but this is the workaround suggeted by the MySQL Documentation. Interesting number.

On a side note, search reloaded doesn’t seem to play nicely with wpPaginate. I have version .2.2 of wpPaginate “for wp 1.5”.

Oh yeah, nice plugin. Thanks for all the work Denis-de-Bernardy.

thanks for the bug report.

v.0.6 removes the limit statement when posts_per_page is -1.

what’s the difference between paginate and custom posts per page?

Maybe I’m totally dumb, but I can’t get the plugin to work. I installed it, activated it and tried a search but got no search results.

Any ideas?
D.

as admin, try running yourblog.com/?flush=1, visit a couple of page (it indexes 100 posts per page view), and try again

i’ve just uploaded v.1.0, which fixes a security hole

One more problem:
When Search Reloaded is activated a search for the string “page” won’t find posts which include “frontpage”. Without Search Reloaded they will be found.

?

yup, it’s normal: the plugin searches for full words, as opposed to a %like%

Are there any possibilities to do truncated searches with Search Reloaded?

if you mean to find ‘apple’ in ‘apples’, not at the moment — but I’ll likely be exploring this in the future.

I think for naive users like me it would be nice to include the following facts into Search Reloaded’s documentation:

– Run “https://yourblog.com/?flush=1” as admin to initialize the plugin after first installation, otherwise searching will be impossible.
– No %like% searches possible in contrast to standard WP search mechanism.

Cheers
D.

Paginate creates a set of links: one for each page of results (like the o’s at the bottom of Gooooooogle’s results).

Custom posts per page allows one to set post_per_page dependant on type of query (category, author, date, etc…)…I think…

Oh yeah, a little more info on the paginate problem:

wpPaginate runs two queries, one slightly modified (with posts_per_page=-1, and paged=1) for the purpose of determining the total number of posts returned (which is then used to determine the number of pages).

The problem is in the result of this first query. Here’s a snippet of the code in question:

$tempposts = query_posts($tempquery_string);
$num_of_pages = ceil(count($tempposts)/$num);


The problem being that count($tempposts) is always 1 when search reloaded is activated.

I’ll post here if/when I learn more.

$num above is posts_per_page. The rest is (I think) fairly self explanatory.