Check your database – do the Relevanssi tables exist? There should be couple of tables with names beginning with wp_relevanssi. If the tables don’t exist, Relevanssi can’t index.
When you click “Build index”, is there anything in the browser javascript console? Any error messages?
Thread Starter
1db
(@1db)
The database does have Relevanssi tables. I didn’t see any error messages in the console.
It gets stranger. I use custom fields (ACF) almost exclusively, and I have the custom fields setting at “Visible.” This is what I usually do. Still, clicking “Build Index” does nothing, and “State of the Index” says “0 documents.”
I went to one of the pages and duplicated the content of a WYSIWYG field in the main edit box (wp_content), saved the page, and checked Relevanssi. Now it says, “1 document.” But it also still shows the alert at the top of the page, “You do not have an index!”
I went to another page, and once again entered some text in the main edit box, saved, and checked Relevanssi. “2 documents.” But the alert is still there, and clicking the “Build Index” button still does nothing…at least, that I can tell.
(BTW, I also deregistered JQuery and loaded 3.1.1 through the header. It was loading 1.12.4, and I’ve had problems before with that version. Changing versions accomplished nothing.)
I am having this problem also. However, it happened on my production site, and now my search is not working! (Yes, bad practice for me to do this on production, but I haven’t had an issue with Relevanssi for many years.)
I clicked ‘Build the Index’, and my index was wiped out with 0 documents added back in. I’ve tried deactivating and activating as well as deleting and reinstalling. Yes, there are Relevanssi tables in the db. I deactivated Yoast. It was working fine until I clicked ‘Build the Index.’
Thread Starter
1db
(@1db)
I was able to get the plugin working by deleting it and installing 4.2.0. Then I updated it to make sure, the update wouldn’t work, and I rolled it back again. But now it won’t complete the index, so I’m wondering if the real problem might be my hosting service, since it was slow and flaky all day long.
Thanks for the update. I’ll try rolling back Relevanssi, this time on my staging site since I restored production.
Are you perhaps using a relevanssi_indexing_restriction filter function? Note that the filter changed in the latest version, and the filter functions need to be updated.
If you’re using the most common attachment type filters, the new versions can be found here: https://www.relevanssi.com/knowledge-base/controlling-attachment-types-index/
Thread Starter
1db
(@1db)
No, and one of the first things I tried was a very bare-bones functions.php that had nothing in it but support for menus. Besides, I also switched to other themes, and the problem never went away.
Could this be related to PHP version, or some setting on the server?
(BTW: just updated to 5.4, and that didn’t help. But it sure took a long time.)
Mikko’s point about the relevanssi_indexing_restriction did it for me. Thanks!
PHP version is likely not related. Relevanssi should work just fine with any PHP version that’s new enough to be safe to use.
Check the Network tab in the browser console. When you click “Build the index”, that should fire a bunch of requests to admin-ajax.php. First one with the action relevanssi_truncate_index, then relevanssi_count_posts, then relevanssi_index_posts until it’s done. Does any of these requests happen?
Thread Starter
1db
(@1db)
Request to admin-ajax.php results in a “500 Internal Server Error,” and the timer just counts up forever while stuck on “Wiping out the index…”
Thread Starter
1db
(@1db)
Okay, an update: after performing the above test, I once again deleted Relevanssi and reinstalled it, version 4.2.0. I activated it, saved the settings I needed, and successfully built the index in 2 seconds. Four requests to admin-ajax.php, all of them OK.
One very strange thing, however: on the plugins page, there is no indication that there is a newer version of Relevanssi, no update prompt at all.
Ok, now that’s progress. If requesting admin-ajax.php leads to a 500 Internal Server Error, that usually means there’s an error reported in the server error log, and knowing what that is will help a lot – so is there something in the server PHP error log?
Hi,
I have the same issue, whereby clicking “Build the index” has just wiped all pages, i.e. searching for delivers no results.
I checked my php-errors.log and found some errors. Do you need them?
Incidentally, have downloaded relevanssi.4.7.0.zip and uploaded this version, building the index works here no problem.
Thread Starter
1db
(@1db)
I checked the error log, but I’m not anything like an expert in interpreting this. There were plentiful errors associated with admin-ajax.php, and every one of them says “File not found.” The file, of course, is there, and has been all along, so I have no idea why the server couldn’t find it.
