| User | Post |
|
4:38 am
February 18, 2011
|
yagraph
Member
| | | |
|
| posts 4 |
|
|
Hi Kevin, and thanks for your work on Role Scopper
I'm currently using Role Scopper 1.3.27 with WordPress 3.1-RC4, and encounter 2 behavior I suspect to be bugs with pages restrictions :
- With Role Scopper enable and Page restriction enable, the tinyMCE visual editor in pages disapear (the HTML editor replace it). I do not reproduce the bug with Posts, because I do not set any restriction on it.
- Users with a role of (WP)Editors, and full rights on certains pages and sub-pages can't create new sub-pages (In 3.1-RC3 a message displayed saying they have no rights to, and in RC-4, it's a blank page)
The server is quite new, so it may be related to a missing library, or something like that… But I can't figure out which one. PHP version is 5.3.3-7.
Thanks for your support,
Best regards,
yagraph
|
|
|
2:56 pm
February 21, 2011
|
Kevin
Admin
| | | |
|
| posts 2503 |
|
|
I haven't been able to reproduce the first issue. When you say "Page restiction enabled" does that mean the Page Editor role is restricted but editing is being done by a non-Administrator who has Page Editor role assigned?
For the second issue, I suspect you have a default restrictions on the Page Editor and (maybe implicitly) Page Author roles. That means newly created pages will not be editable by their creator (unless creator has a Default Page Role assignment).
The best solution to this admittedly confusing scenario is to avoid default-restricting the Page Author role. If you must still default-restrict the Page Editor role, the Page Author restriction setting must be decoupled from it. Go to Roles > Options > Advanced > Additional Object Role and enable "Page Author". Then go back to Restrictions > Pages and make sure it's not default restricted.
|
|
|
9:09 am
February 22, 2011
|
yagraph
Member
| | | |
|
| posts 4 |
|
|
Thanks a lot for your reply Kevin.
For the first issue, answer to your question is yes.
But on afterthought, it seems to be a "PHP lack of memory" issue : Role Scopper seem to ask a little more memory when allowed pages loads for restricted users, and my server reached the allowed limit. I have contacted the hoster, and hope to fix it soon.
For the second, I confirm, it's confusing ! but with your help, it seem to be resolved now… but I can't either confirm it right now cause of the first issue preventing me to test it.
I keep you in touch, as soon as the hoster contact me !
Best regards,
yagraph
|
|
|
4:32 am
February 24, 2011
|
yagraph
Member
| | | |
|
| posts 4 |
|
|
Hi Kevin,
after few days of resaerches and bug tracking with no succes, I go back to you …
I've updated my wordpress installation to 3.1 final, gone to Roles > Options > Advanced > Additional Object Role and enable "Page Author", unrestricted it, and my issue is still present :
A resticted user (with a role of (WP)Editors, and full rights on certains pages and sub-pages) now can't access a page (it do not load correctly, visuale editor is not loading - screenshot here - in french sorry), and if he try to create a new page, he obtain a blanck page.
Error is : Fatal error: Allowed memory size of 52428800 bytes exhausted (tried to allocate 81 bytes) in /home/wp-iepg/wp-includes/load.php on line 569
So, we tried to increased memory limit in php.ini, from 256 MB to 512 MB… and the bug isn't resolved… 512 MB seem a huge amount of memory for Role Scoper and Wordpress.
Maybe the is a PHP library we lack ?
The bug do not appear with unrestricted objects…
Please tell me more !
Best regards,
yagraph
|
|
|
8:50 am
February 28, 2011
|
Kevin
Admin
| | | |
|
| posts 2503 |
|
|
52428800 bytes = 50MB, not 512.
Memory usage (by both WP and RS) tends to be highest for the Post/Page edit form so it's not surprising that's where you hit the memory limit.
The additional diagnostic info you sent me shows that Role Scoper is using 4 to 5 MB in wp-admin for non-Administrators. That's normal but can be reduced somewhat through the following option settings:
Roles > Options > Features tab > Content Maintenance > "Roles and Restrictions can be set" > by Content Administrators
Roles > Options > Features tab > Content Maintenance > "Filter Users Dropdown" > disable
Roles > Options > Advanced tab > Role Assignment Interface > "Indicate blended roles" > disable
Roles > Options > Realm tab > disable support for any types/taxonomies which will not be affected by RS roles or restrictions
|
|
|
8:12 am
March 1, 2011
|
yagraph
Member
| | | |
|
| posts 4 |
|
|
Post Awaiting Approval by Forum Administrator
|
|
Login
Register
Search 
Forums
Topic RSS 