+1 on relying on a fallback browser mapping. User choice has always made me uneasy.
Paul Gazda Senior Web Developer Information Technology Services Northern Arizona University [EMAIL PROTECTED] (928) 523-6844 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tuyhang Ly Sent: Wednesday, December 19, 2007 12:11 PM To: [email protected] Subject: Re: [uportal-dev] Remove Browser Mapping Prompt in uP3 Rutgers had this issue in production twice already since 11/12/07. So, we added the following entry at the end of the browser.mappings file to disable this feature: # Default profile .*=1 Thanks, Tuy. Eric Dalquist wrote: > I'm working on cleaning up the creation of the UserInstance, > IUserPreferencesManager and IUserLayoutManager classes in uP3 to > facilitate access to them earlier in the request processing cycle. > While doing this I'm running into an issue with the part of the > initialization of a UserInstance that deals with browser mappings and > prompting the user for their browser mapping. > > After the discussion from a few weeks ago about how bad this 'let the > user pick the profile to use' approach is can I just remove the code > that uses a StandaloneChannelRenderer to render the > CSelectSystemProfile channel from UserInstance and just rely on their > being a fallback browser mapping in the configuration? > > -Eric -- You are currently subscribed to [email protected] as: [EMAIL PROTECTED] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev -- You are currently subscribed to [email protected] as: [EMAIL PROTECTED] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
