Ok, well I think I've figured out a way to achieve at least part of what I'm trying to do.
If I simply empty the _user/template directory, I realize the portal behavior that I want, that is, all users see the same view, as controlled by the admin and constraints. Each user still has a directory created under _user, which I'd prefer to avoid if possible, but I can live with that if it is not possible or convenient to prevent. cheers, Linus > -----Message d'origine----- > De : Linus Kamb [mailto:[email protected]] > Envoyé : Tuesday, March 02, 2010 11:08 AM > À : 'Jetspeed Users List' > Objet : self-registration portlet, user trees, and subsites > > Hi, > > > > I apologize for a bunch of newbie questions here, but I've taken over a > portal site and we're > trying to upgrade from 2.1.3 to 2.2.0, and rebuilding the site from scratch, > so a lot of stuff that > was put in place before I got here (by someone no longer here) needs to be > put back, and I'm at a > bit of a loss for some of the items. > > > > In our current 2.1.3 site, self-registration was apparently "broken" so they > have had to add all > the users by hand. This is not acceptable going forward, but it had the > consequence of all users > seeing a single view of the portal site (which is what we want.) That is, > if the admin changes > the content of the site or of a particular page, that is reflected for > everyone. In addition, > there is not a directory tree created for every user. We don't need or want > individual users > changing things, and don't need subsites. When new users are created they > all see basically what > the admin has laid out. (Admin vs user views and a couple of guest vs user > views are controlled > through constraints, which I think I understand.) > > > > Perhaps this is not the way it's supposed to be, but it has been working for > us. > > > > Now, upgrading to 2.2.0, I would like to make the self-registration portlet > work in more-or-less > the same manner. I've been poking at it in various ways, including editing > the new user defaults > in the security admin pages, as well as the self-registration defaults, but > all I've managed to do > is either not affect anything (eg, new folder for each user, new user pages > are from the > user/template tree,) or else break it with various errors including NPE and > "destination already > exists." > > > > So, in summary, what I would like is for the admin to be able to make changes > in one place (using > the portal page-editing tools), and have all users, including self-registered > new users, see those > pages and changes. > > > > Is this reasonable? Doable? And if so, how do I go about affecting it? > > > > I admit I don't fully understand the profiling rules, so I don't know if they > come in to play here. > > > > thanks a lot, > > Linus > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
