I am actually having a somewhat related problem. I am using Mailpress for newsletter subscription, which is very similar to Subscribe2. THe trouble is that when I send messages through this system, they are sent and received, but are blank. The Mailpress program lists them as sent with all contents, but by the time it reaches my inbox there is no content. The reason I think Role Scoper might be in play here is a certain error code I am getting in the logs. I won't paste it all here, but here is a snippet:

2008-11-06 17:16:09 000000 — PHP [E_STRICT] 2048 : Non-static method
ScoperHardway::flt_recent_comments() cannot be called statically in /
home/content/*/html/blog/wp-includes/plugin.php at

Does this ScoperHardway sound familiar to you? THe author of Maipress is at aloss to what it is and I thought I might run it by you. The plugin has been working great otherwise. THanks for your help.

J said:

so, i installed Subscribe2 (http://subscribe2.wordpress.com), which seems to work fine, as long as the user is an administrator. 'Las, apparently, when he's a suscriber (according wordpress role), he doesn't see the list of categories he can (un)subscribe to.

This is probably due to how Subscribe2 queries categories.  Anything that uses the WordPress get_categories or get_terms function should be filtered by Role Scoper.  I'll look into it when I get a chance.

Hi Kevin,

Actually I had / have problems with Subscribe2 as well. My live blogs are using 0.9.27 but I did try and use at least one of the betas of RS1.0.

Two of my blogs are fine, I have a few users who are allowed only to post or read in certain cetegories. I use Subscribe2 and it works fine! I think it didn't when I first set things up - bit old age may be getting the better of me - and I played around deleting and editing the various section settings, and somehow it started working. But I couldn't reproduce these conditions. But now, when the user looks at their subscriptions, they are presented with the option to subscribe to only those categories they can be authors in. Everything is as you might hope Role Scoper would behave.

But on a thrid blog, try as I might, I cannot get any of the categories to display, for users who are not admins, as reported above by J.

Confused!

Not yet.

This week my programming time has been devoted to some "Premium Support" to a paying client.  Soon everyone will benefit from the resulting bug fixes, including some significant issues with the assignment of default / propagating roles and restrictions on page / category creation.

I plan to take a look at the Subscribe2 category issue early next week.

I have included a fix for this in the newly updated Role Scoper development snapshot.  This is very close to a 1.0.0 RC2 release, and also includes a number of other fixes (noted in changelog.txt) which i won't list here.

Hi Kevin,

Subscribe2-RoleScoper seems to be broken for me now. I have tried the latest RS RC2b and I just noticed (not sure how long it might have been doing it, but at some point it was previously displaying only "allowed" categories) that my users can now see all categories listed under the Subscribe2 category listing, not just those they are restricted to read (and the users at set up so they can also write to these cats at the same time). If I role this blog back just be reinstalling RS 0.9.27 then the subscribe2 restriction does seem to come back as those categories the user can write to. Using WP 2.6.5 on this particular blog, but I also saw the same effect on a WP2.7RC1 blog.

Thanks

YikYak

YikYak said:

Subscribe2-RoleScoper seems to be broken for me now. I have tried the latest RS RC2b and I just noticed (not sure how long it might have been doing it, but at some point it was previously displaying only “allowed” categories) that my users can now see all categories listed under the Subscribe2 category listing, not just those they are restricted to read

Confirmed, I didn't get Subscribe2 plugin compatibility quite right in RC2 (or RC2b).  You are welcomed to help test the fix in the updated Role Scoper development snapshot.  This RC3-dev version also includes a number of other fixes as described in its changelog.txt.  The Subscribe2 issue was not WP 2.7-related, but most of the other new fixes are.

First of all, best wishes to everyone : Merry Christmas, and happy 2009 !

i upgraded to WP 2.7, and it seems to me that RC4 and RC5 (i tested both) are acting a bit :

i can associate a group of user to a certain category ; when one specific user logs in, he doesn't necessarily see the category. log in/log out, a couple of times … and *pouf* there it is … but if i remove the association category/group, a user of the previous assigned group to the category can still see the posts of that category.

And in subscribe 2 subscription panel, categories remain, no matter if change the group-category association, a user of that group will always be registered to the category.

RS was working fine, till RC3, and with WP 2.6x - i *think* it was even ok with WP 2.7 … what happened since then, and is RS or WP who's responsible ? i don't think it's subscribe 2, is it ?

Thank you !

J.

I've disabled the persistent cache in 1.0.0-RC6 and won't reinstate it until we can explain these symptoms.

Hello Kevin,

I tried to be as systematic as possible, to try and explain more precisely what is going on. Here's the sequence :
1. i create a new category Test01. by default, “group01″ is automatically assigned as reader to that category
2. i added a post 01, which i assigned to the specific category Test01
3. i logged as user01, member of group01. he can see the category, and the post
4. i logged in as user02 (member of group02) - he can't see anything
So far, everything is fine ^^
5. in the role panel, i assign group02 as reader to the Test01 category
6. i log as user02, ! he can't see the category
7. i log as user01, he can see the post
8. in the role panel, i remove the reading capability of the category Test01 from group01
9. i log as user01,  ! he still can see the category, but not the post, as when i click the category, it refreshes the page and hides the category, and says the post was not found
10. if i log as user02 again, he can then see the category, and the post
11. i remove the post reading capability from group02, and refresh the page without logging user02 out. he still can see the category as the post
12. i log him out, and back in, he still could see the category and the post, despite no group is assigned anymore as reader of the Test01 category

Then, i flushed the cache, deleting the “…..12345abcde124xyz….” folder from wp-content\cache.

13. i logged in as user01 and user02, they couldn't see anything
14. i create a new category Test02. by default, “group01″ is automatically assigned as reader to that group
15. i add a post 02, which i assigned to the specific category Test02
16. i logged in as user01, member of group01. he can *not* see the category, nor the post, even i refreshed the page, logged in and out
17. i logged as an admin, and could see them all
18. i add group02 as reader of the test02 category
19. i log in as user01 first, and ! he could see the post !
20. i log in as user02, and he could see the post
21. i remove from group01 the capability to read Test02 category
22. i log in as user02, he still can see the post02, which is fine
23. i log in as user01, ! he still can see the category, and can access the post

Well, i hope it is helpful as such, and it gives some hints as about what goes on ^^
the logic, though there seems to be one, is a bit obscure to me

Condition of the test :
i used firefox 3, where i was logged with a user having an admin role to create the category, and write the post, change the roles, and internet explorer 7 to log in/out the different users, and see what they could read or not.