Edit: Oops sorry, should have read your post better, it sounds like you already tried the deactivating, reactivating and then rebuilding.
Maybe try the procedure of disabling all other plugins and switching to the default wordpress theme and see if you still get the same problem.
I suppose conflict with another plugin is a feasible explanation. If you have the PHP skills, figuring out where the search process fails would be most helpful. I can help you with that, if you know PHP enough.
Thread Starter
acy
(@acy)
If you have the PHP skills, figuring out where the search process fails would be most helpful. I can help you with that, if you know PHP enough.
Thanks msaari! I think a have basic php skills… I’ll do my best. 🙂
I upgraded to 3.0.1 but Relevanssi is still not working. I rebuild the index and there are 0 documents in the index. I also get an error message:
Warning: set_time_limit() has been disabled for security reasons in /var/www/domain/html/wp-content/plugins/relevanssi/lib/indexing.php on line 7
I downgraded back to 2.9.14 and now it works fine again. So I better stay with the old version, till this bug is fixed.
Owcv, since I don’t know what the bug is, I can’t really fix it. I can add a check to see if the set_time_limit() function is available, if that’s the source of the problem.
Acy,
Find lib/search.php in the Relevanssi plugin directory. Line 38 is:
$posts = relevanssi_do_query($wp_query);
After that line, add
var_dump($posts);
and run a search. Do you see a dump of search results?
If not, find line 715, which is:
$hits = $return['hits'];
and after that line, add
var_dump($hits);
Again, do you see a dump of hits found?
If not, find line 377, which is:
$matches = $wpdb->get_results($query);
and after that, add:
var_dump($matches);
What do you get?
@msaari:
With the new version, rebuilding the index seem to work now, but the error message still occurs. But now at least search seem to work again. Not sure, if properly…
Do you mean the set_time_limit() error? If so, I added some safeguards to that, but apparently your host is set up in a different way.
Thread Starter
acy
(@acy)
Hey mikko! I just updated to the latest version (problem still occurs) and that is the result after adding var_dump() as mentioned – only var_dump($matches) returned something… The rest was empty.
http://pastebin.com/K8qc9X9G
Hmm, so you have matches, but no hits. Odd.
After line 476, which is
if ($post_ok) {
add
var_dump($match);
What do you get?
Thread Starter
acy
(@acy)
I get no return. Even no array(0) { } as before…
Are you using Role-Scoper? If so, that’s why the search is not working.
Thread Starter
acy
(@acy)
oh yes, I’m using it 🙂 Any workaround?
Hi Mikko,
you are right, i am combining the relevansii and role-scoper plugins and both are working.
The issue which is under the relevansii release is that I am using 2.9. not the 3.0 cause no results were sent back.
I do not really search deeply cuz i googled and found that version works. So if you want me to help pliz tell me which files, queries or anything to test. I was just waiting for the “repaired” release but providing any help don’t bother me not at all.
Yes, there’s a workaround. Hopefully the next version of Role-Scoper will fix it, meanwhile you need to change one file. Get it here: http://www.relevanssi.com/release-notes/free-3-0-2/
Tnaks Mikko i gonna try it right now so hopefully i will tell you al soon as possible, maximun on monday ok? (depende on my boss)
I think role scoper works perfectly under its phylosophy, but dealing so much info is really hard so i understand kevinB’s difficulties. Lets just wait what he is preparing to surprise us.
Meanwhile, i also did not checked the code but Mikko make the light and so us where the issue was located or the main prob pliz =)
