Resources

My Agape try

Your Agape try

News Categories:

Site search

Minor Bug Fixes in Role Scoper 1.0.2

Role Scoper 1.0.2 addresses the various bug reports which have trickled in over the last 6 weeks.  These bugs are all minor in severity and/or affect only a minority of installations.  For details see the change log below.

The only significant new feature is an option to enter usernames or ids (for role assignment) via comma-separated text entry instead of by checkbox selection. This will be a performance and convenience enhancement for installations with over 100 users.

The full change log:

  • BugFix : Template function is_restricted_rs / is_exclusive_rs was non-functional on home page (since rc9.9311)
  • BugFix : With Attachments Filter enabled, attachments larger than 10MB fail to download on some installations
  • BugFix : Fatal Error when viewing a single post entry after RS Options modified to disable front-end filtering
  • BugFix : Auto-delete orphaned role assignments left in DB by previous versions following category / group deletion
  • BugFix : After an empty group was deleted, its role assignments were left in the database
  • BugFix : Event Calendar events without an associated post were not displayed without calendar refresh
  • BugFix : Post Restrictions and Post Roles did not display on PHP 4 servers
  • BugFix : In Post/Page Edit Form, Author selection was inappropriately available to non-editors
  • BugFix : Orphaned role assignments already stored to database will be autodeleted on RS version update
  • BugFix : If the object type of a requested attachment parent cannot be determined, assume post
  • BugFix : Teaser message displayed in header with some themes
  • BugFix : http authentication prompt for RSS feeds with logged administrators on some installations
  • BugFix : Hidden Editing Elements settings were not effective for unpublished posts/pages
  • BugFix : If a memberless group was deleted, any assigned roles were left (orphaned) in the database
  • Plugin : Conflict with WP-Wall plugin caused non-listing or double-listing of wall comments
  • Feature : Option to accept CSV entry for user role assignment
  • Feature : Bottom-right submit button on bulk admin forms if SCOPER_EXTRA_SUBMIT_BUTTON is defined

Posted: May 7th, 2009 under News, Role Scoper, WordPress Plugins.
Comments: 8

Comments

Comment from Ramon van Belzen
Time: May 8, 2009, 8:52 am

Hello Kevin, 1 small problem which occured twice here; after upgrading the plugin doesn`t get re-activated which causes the site to go half down untill i manually enable the plugin again

Comment from Kevin
Time: May 8, 2009, 9:47 am

That would be a major problem, but can you help me confirm what actually happened? How did you do the update? If by manually uploading files, is there a chance you put the new version into a differently named subdirectory? What version of RS were you running before, and what version of WP are you on?

So far I haven't been able to make the re-activation failure happen.

Comment from Ramon van Belzen
Time: May 8, 2009, 10:55 am

I had to problem with going from 1.0.0 to 1.0.1 and 1.0.1 to 1.0.2 on WordPress 2.7.1 (php5 mysql 5) I used wordpress`s built in updating system

Comment from Kevin
Time: May 8, 2009, 11:05 am

Okay, I've confirmed that the WP plugin updater did not re-activate Role Scoper (despite the "re-activated successfully" message). I'm in the process of troubleshooting that.

Comment from baron
Time: May 8, 2009, 12:11 pm

Works great, thank you

Comment from Justin Adie
Time: June 9, 2009, 6:17 am

Hi I am using RS to limit certain categories to certain 'groups' of users. for example i have a head category called client X and under that category many different sub-categories. All client X users can see all client X categories. This works fine but for one thing, if a new category is created under Client X, it does _NOT_ inherit the permissions. This appears to me to a be a bug in the context that it is illogical given the ability to pre-authorise/restrict parent and child categories. What do you think? thanks Justin

Comment from Kevin
Time: June 17, 2009, 1:27 pm

Justin,

I have confirmed that category restrictions are not inherited upon new category creation. Will develop a fix for this soon.

I'm not sure what you mean by illogical. Will it be logical to you once the fix is in place?

Comment from Kevin
Time: June 17, 2009, 1:54 pm

Inheritance of Category Restrictions upon category creation is now fixed in the development snapshot.

Write a comment

(But if your comment is a usage question, bug report or feature request, please post it in the Support Forum instead.)