Todays morning I released a new version of my “IWG Hide Dashboard” Plugin for WordPress.
The new version is tested and running on version 2.5.1 of WordPress too.
I’ve made some changes to handle better the header already sent ... problem, reported only by some users. Now this problem should be fixed completely. ( I hope so 
)
am 07.05.2008 um 17:33 Uhr:
hallo thomas!
danke fuer dein plugin. - habs heute in zwei weblogs eingebaut. - eine kurze anregung haette ich noch:
da dein plugin als security-erweiterung dient, finde ich, dass das ausschlusssprinzip zur anwendung kommen sollte: (den design principals von saltzer and schroeder folgend)
statt das dashboard explicit mit deinem code zu verbieten,
if ( current_user_can('hide_dashboard') ) {wuerde ich eher die zusaetzliche faehigkeit der rollen erweitern, um das dashboard anzuzeigen.
if ( !current_user_can('show_dashboard') ) {du koenntest deine user auch in eine etwaige aenderung miteinzubeziehen, indem du einfach beides mit einem
orerlaubst…danke & lg berny
am 27.05.2008 um 19:15 Uhr:
I have just activated this plugin in a wp 2.5.1 environment with role manager.
What I want is to have the “admin” user access the dashboard and the “std” user with a custom role NOT to access the dashboard.
With your plugin a new capability “Edit Dashboard” was added and granted for “admin” and denied for every other user.
1. Testing the login, WP behaves equal to any user, and let them access the dashboard.
2. When I look into your Your iwg_hide_dashboard.php script, it states
3. Changing this part of the script to
I notice a difference in the behaviour.
4. It just seems to work the other way around. So when denying the “Edit Dashboard” to the admin user, and granting it to the other user, it works as expected.