Well, when there's no read permission, selected plugin is not even opened and user sees an error in the control panel. When there are no write permissions, we usually open our plugin and just disable the editable content, but without any message. I've added shared partial missing_write_permissions, which you can use to render from your code and that provides the common warning message. It requires permissions hash as parameters (see webclient commit 013155be3559c8c73d842106b96b50a0e644ec49). Feel free to adapt the text or css style if there's anything wrong with it. Jiri -- Jiri Suchomel SUSE LINUX, s.r.o. e-mail: jsuchome@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Praha 9, Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org