portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 25538] - How to entirely block access to the customizer
Date Tue, 13 Jan 2004 15:17:55 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25538>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25538

How to entirely block access to the customizer

paul-apache@mansfield.co.uk changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WORKSFORME                  |



------- Additional Comments From paul-apache@mansfield.co.uk  2004-01-13 15:17 -------
sorry to be a PITA, but maybe I screwed up something, but, I've revisited this 
and I still can't block access to the customizer.

I've even been as far as manually edited the xreg files to make lots of internal 
things visible and tweak access to those.

Is the customizer a portlet, and if so which one?

I also have a problem that I want to solely use role-based psml files, and yet I 
seem to get a new directory for each user that I create, when that user logs in.

I think I might try starting with a new fresh jetspeed1.4 webapp built from 
scratch and see whether I can solve my problems, and then put in my portlets.

thanks for your time,
Paul

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org


Mime
View raw message