That is true but with two (quickly implementable) solutions of:
1. leave it and let the user pick2. ensure your browser mappings are good and fix things that get through to the default later
I would prefer 2. leaving it to the user to choose, especially since the setting is system wide, is going to cause problems.
The best solution would be a per-user setting (using a cookie perhaps?) to let the user pick the style for the portal they would like to view. That isn't going to happen in the current uP3 release so I'm left choosing between options 1 & 2.
-Eric Paul Gazda wrote:
It just occurred to me after my +1, that all the fallback methods that I remember seeing fall back to browser type = 1. What if an unknown WAP browser accesses uPortal. Wouldn't they erroneously be assigned the wrong browser type? That would then require manual intervention to fix just as the wrong browser type assignment by a user now does. 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 Paul Gazda Sent: Wednesday, December 19, 2007 12:49 PM To: [email protected] Subject: RE: [uportal-dev] Remove Browser Mapping Prompt in uP3 +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 uP3Rutgers 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
smime.p7s
Description: S/MIME Cryptographic Signature
