I've never worked with Relevanssi nor tested it, and at this point it looks incompatible with Role Scoper. I would need to schedule some consulting time to investigate / address this along with a more serious conflict I discovered.

Hello,

I have a similar problem, even after reading Relevanssi support forum, where they say it's fixed…

After typing a word to search, all related contents are displayed, although if the user clicks on a link to read the complete text, log in is required if the user has no rights to read it.

Does it works with Role Scoper 1.3.44?

Thank yo very much!

@spreed: Yes, .44 is the last version in which it works as expected - I decided to try each version between .44 and .50, and found that .44->.45 is where it seems to break.  However, note that the behavior I'm seeing is NOT the same as you - you say that you can see ALL content (even if a user can't access it).  For me it's the opposite: it's not returning any of the content that the current user should be able to access.

@Kevin: Hasn't user-specific access filtering existed all along, though?  I've been using Relevanssi almost as long as Role-Scoper, and they've always worked wonderfully together - until the 1.3.44->1.3.45 changes…

Here's a video that first shows a search by an anonymous user (for whom a restricted post is not visible), followed by the same search by a logged-in user (for whom the restricted post becomes visible).

I then login and show you the permissions set on that post, and scroll through each tab on Role-Scoper's options page.  Hopefully these are the relevant settings you need, but if not, please let me know and I'll snapshot the others.  Hopefully I scrolled slowly enough that you can pause the video to get a better look at the pages which may be relevant.

<Link Removed>

(Once you've seen/copied it, please remove the video link from this post :))

@spreed: I don't see why you'd need to see a video of my backend permission settings…

@Kevin: Just curious if you happen to've had a chance to look at this?  I emailed you a link to the video, but never heard back so I'm not sure if you got it.  Tried the new v1.3.52 but the same problem persists.

Thanks!

No worries, just checking up…thanks again!

Hey Kevin,

Tried it out, and the Relevanssi conflict indeed seems to be fixed!  However, a new bug has been introduced

I'm now completely unable to post comments to private blog entries.  When logged in as Administrator and viewing a private post (that only I can see), if I try to post a comment it simply seems to be ignored - the page is refreshed and no comment is there (either when viewing the post itself or on the backend admin panel).  If, however, I then revert to 1.3.44 (the last version in which everything worked), the comments I posted with 1.3.53 suddenly become visible.

…It appears to've wiped out the Relvanssi index.  Re-indexing allowed it to work with 1.3.44 as it had before.  Strange :/

metal450 said:

Does simply installing (and subsequently removing) 1.3.53 make some permanent change??

There may be a remaining conflict at play here. But but no, RS makes no change other than calling relevanssi_truncate_cache() and relevanssi_build_index()

I'm not seeing RS deactivation as a repeatable cause of Relevanssi index corruption. As you have noted, re-indexing via Settings > Relevanssi corrects the condition. Let me know if you find a more definite cause.

…It's because of this, in role-scoper_main.php:

if ( $is_administrator ) {

if ( $this->is_front() )

require_once( 'comments-int-administrator_rs.php' );

} else

require_once( 'comments-interceptor_rs.php' );

(i.e. when logged in as an admin, it's now using a different comment interceptor class).  Changing it to check for class 'Scoper' instead works for both versions.