First of all, I want to thank you for your amazing plugin. I've been looking for a plugin like Role Scope, and now I finally found it…..thank you very much.

After I uploaded and activated the plugin (Role Scoper 1.0.0 Release Candidate I created a few usernames and pages just so I could play around with the plugin and get familiar with it.

However, Now that I'm trying to delete the usernames and pages I keep getting the following error:
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 500001 bytes) in /home/goalfouf/public_html/futbolwallpapers/wp-includes/class-snoopy.php on line 894

My sites URL is - http://www.futbolwallpapers.com - and I have Wordpress 2.6.5.

When I deactivate your plugin I can delete the usernames and pages just fine, without any errors.

I was hoping you would have the answer or at least point me to the right direction. This is great and very usefull plugin and now that I finally found it, I would hate to work without it, because of a small error.

Thank you very much in advance.
Artin

The error message shows that your web server is allowing PHP to consume up to 32MB for each http request. This is the standard allowance which wp-settings.php asks for.

In my tests, WP 2.7 running the default theme uses about 9.1 MB for front end access, 11.5MB for wp-admin. Role Scoper uses about 3.5 MB on the front end and 4.5 MB in wp-admin. That's a lot; by comparison, Simple:Press 3 took 2.8MB, PodPress 1.5MB and NextGenGallery 1MB.

I don't see any single sinkhole that in the code that is wasting memory. Bulk-deleting users or posts increases memory usage slightly due to the role maintenance scripts that run for each affected post, but in my trials that difference was minor. I suspect it's a straw breaking the back situation.

From my perspective, Role Scoper is just a lot of abstract code to meet some ambitious goals for function and flexibility. I'll keep open to ways to reduce that memory usage, especially if future versions of WP add new administrative hooks to make Role Scoper's job easier. I'm going to run some experiments on a feature-reduced version for memory-tight installations. For now, each site administrator will need to decide whether that memory "cost" is worth the benefit RS adds (and whether you can adjust your memory budget accordingly).

Thanks a lot for the replys. I gues this was to good to be true.

Kevin said:

No, just carrying too much to rank a station wagon GVW.

I should have added "…and not fully optimized yet". Now it is, and with the newly updated Role Scoper Development Snapshot, typical memory usage is now:

• 3.6 MB in wp-admin as a non-Administrator
• 3.3 MB in wp-admin as an Administrator
• 2.9 MB on the admin Dashboard as a non-Administrator
• 2.0 MB on the admin Dashboard as an Administrator
• 3.1 MB on the front-end as an Anonymous viewer with default settings
• 2.6 MB on the front-end as an Anonymous viewer with "no front-end admin" option

That's a reduction of 0.85 MB on the front-end and 1.1 MB to 2 MB in wp-admin.

Maybe Role Scoper is light enough to drive down your subdivision now.