All users should download Role Scoper 0.9.15 Beta Revision, which eliminates and cleans up after a nasty bug I introduced in the previous version. In v 0.9.14, it was possible to select as page parent a descendant page. i.e. “Page A is the child of Page B and Page B is the child of Page A.” WordPress was not amused, and slipped into an infinite loop (and then script timeout) on subsequent attempts to manage or edit pages. The invalid database entry continues to confound the WordPress core even if Role Scoper is removed. If you were unfortunate enough to join me in this misery today, the only way back (short of manually editing the page DB record) is to install this Role Scoper revision, which will correct the conflicting parent selections and eliminate that option for future page edits.

This revision also corrects the following bugs:

• fixed: In page edit, Contributors were sometimes allowed to publish inappropriately if they have the Page Editor role assigned for another page.

• fixed: User group membership change via user profile edit was not updating cache.

• fixed: In user profile, user’s WP Role metagroup “membership” was indicated in group count but not listed as a group.

• fixed: various PHP warning messages for undeclared variables.

This is also a worthwhile download for those who haven’t upgrade in a while. The past week’s other bug fixes have corrected a lot of cache update issues and brought much more consistency to post/page-specific editing roles.