[Plugin: Relevanssi – A Better Search] Conflict Relevanssi v3.0 and Role Scoper

I’ll have to investigate if I broke the Role-Scoper compatibility somehow in the update. Are you using the latest version of Role-Scoper?

Yes. The lastest version 1.3.55

Curious – I’ve been trying this on Relevanssi Premium 1.8.3, which is essentially the same as free 3.0, and it works just fine. I’ll have to check with the free version to be sure, though.

I desinstalled role scoper and deleted the tables in database, and I reinstalled RS and Relevanssi but nothing changes.

Hmm, anything particular in your Role-Scoper settings that could cause the problem? The thing is, I now have 3.0 installed on my test blog and Role-Scoper is enabled, yet everything works just fine. In order to fix what’s wrong, I need to know what’s breaking it…

I’m using Relevanssi 3.0 and Role Scoper 1.3.55 and no search results are showing too. By simple disabling Role Scoper I can get correct Relevanssi result; by enable RS, the search page shows a 404 error.

As a test, I’ve reverted the Role Scoper to Default values (on plugin’s main page exists a button called “Revert to Defaults”) and the incompatibility persists…

I use the default settings in Role Scoper. And I tested the 2 plugins on another website (quite simple, without custom post types, taxonomies, fields…), with default settings, and the search produces no results. The same with a test blog, with only these 2 plugins installed.

I don’t know how Relevanssi and RS together can produce a 404 on search page. That sounds like a very unlikely result, the worst-case scenario should be just no results.

The thing is, I can’t make the combination break, no matter what I try. The both plugins work together with no problems. Unless I can get it to break, I won’t know how to fix the problem.

To be sure, I just did a clean install of Role-Scoper and Relevanssi to a new blog from the repository, and it works.

No 404 for me but no results. It could come from the server settings ?

I’ve been having the same issue with the current versions of Relevanssi and Role Scoper.
I took a peek and I saw the following:

relevanssi_default_post_ok() has two arguments, the second of which is the post ID, which gets added to the relevanssi_post_ok filter.

Role Scoper has a file called “relevanssi-helper-front_rs.php” that REMOVES relevanssi_default_post_ok from the filter replaces it with it’s own relevanssi_post_ok() function, which only takes one argument – the post ID.

That is, Role Scoper replaces a function that takes 2 arguments with a function that takes only 1.

In my case at least, it looks like relevanssi_post_ok() is always returning false because every time it’s called it’s trying to use $post_ok (which evaluates to 1 each time) as the post ID. Maybe the search works on your fresh installation because, unlike in my case, you have a visible post whose ID is 1.

That’s all I had time for today, but I hope that helps.

Yeah. I modified a post in my database with ID=1 and now the search with RS enabled produces results. Thanks Daniel !

I’m glad that worked as a temporary solution. Just to be clear though, having a visible post with ID = 1 doesn’t truly solve the issue, it just uses the miscommunication between the plugins to trick them into thinking ALL posts should be shown instead of NONE.

My guess is that your searches are now returning all posts for all users, including posts that shouldn’t be visible.

Ah, it’s the same old problem —?I was under the assumption that this was already fixed in Role-Scoper, but it appears it isn’t. Well, in that case next version of Role-Scoper should fix it, as I’ve notified the Role-Scoper developer about it.

You can also download a fixed version of the Role-Scoper helper file here: https://www.relevanssi.com/relevanssi-helper-front_rs.txt

Just save that with a .php ending and use it to replace the old file.