3.2.0-RC1

Jasig is proud to announce the first Release Candidate of uPortal 3.2.0. This release is feature complete with the exception of some minor CSS refactoring and will be undergoing additional testing and bugfixes over the next week before a second release candidate is cut. The uPortal 3.2 release includes many new features contributed back by uPortal adopters along with the updates from nearly a year of production use. At this time parties interested in new uPortal deployments are encouraged to strongly consider starting with uPortal 3.2.

New Feature

• UP-1615 - Administer uncategorized channels via the Channel Manager
• UP-1885 - Add ability to disable portlets
• UP-2046 - Add DETACHED WindowState for portlets
• UP-2426 - Login Servlet should redirect to original URL
• UP-2427 - Support scoping theme messages by institution key
• UP-2452 - Admin portlet to reset a user's layout.
• UP-2505 - Aggregate CSS & JS used by skin/theme
• UP-2506 - Move XSLT cache to EhCache
• UP-2507 - Add a Cache Management flow
• UP-2510 - Create new administrative links portlet
• UP-2563 - CONFIG PortletMode Support

Improvement

• UP-933 - Support for multi-valued attributes in User Info Map
• UP-1941 - Add constants to PortalApplicationContextLocator for bean names
• UP-2050 - Fix hard-coded string for path to theme skin files
• UP-2087 - Upgrade uPortal CAS Client to Jasig CAS Client for Java
• UP-2162 - Add an interface to publish a channel in Quicklinks
• UP-2172 - Replace RDBMChannelRegistryStore and ChannelRegistryManager
• UP-2188 - Make layout import/export smart enough to handle arbitrary layers of nesting (e.g. subtabs)
• UP-2189 - Add optional support for UP_PERSON_DIR data to User entities in Import/Export
• UP-2340 - FragmentDefinitionDao should have a JPA unit test
• UP-2380 - Add comments to uportal-impl/test/resources/properties/contexts/*
• UP-2389 - Renaming skin files shouldn't be required
• UP-2402 - Make import & export tasks fail-fast
• UP-2406 - Overhaul Import/Export of layouts
• UP-2428 - Upgrade uPortal to Fluid 1.1.2
• UP-2440 - Move ear deployer and ant tasks to seperate project
• UP-2458 - Tweak Flyout menus to support right flyouts (necessary when tabs are aligned to the right)
• UP-2463 - Improve people search flow UI
• UP-2494 - Majority of deafult layouts should be fragment based
• UP-2495 - Cleanup the default Groups and Categories
• UP-2504 - Switch flyouts to be positioned relative to the tab li
• UP-2509 - Update portal administration portlets to use new CSS classes
• UP-2513 - Change default location of portal log file, CAS and all portlet-overlay portlets
• UP-2517 - Create portlet replacement for CSqlChannel
• UP-2520 - Enhance layout Import/Export to preserve existing STRUCT_IDs for layouts of fragment owners
• UP-2531 - Please decrease padding for .portlet-msg-* classes in uPortal-provided skins to avoid overlap
• UP-2532 - Create portlet replacement for CLocaleSelector
• UP-2535 - Create portlet replacement for CSnoop
• UP-2538 - Allow fragment owners to subscribe to uncategorized channels
• UP-2543 - Add example for MySQL to rdbm.properties
• UP-2544 - Upgrade to maven-ant-tasks 2.0.10
• UP-2545 - Thread pool check should log at warn, not error, needs message
• UP-2546 - Create portlet replacement for CImage
• UP-2547 - Create portlet replacement for CIframe
• UP-2549 - Add periodic output buffer flushing
• UP-2558 - mediating bean to allow JNDI configured LDAP groups to be handled from command line

Task

• UP-2309 - Evaluate and update default layout for the general release
• UP-2352 - student users gets logged in fragment administator
• UP-2388 - Bump Cernunnos version to 1.1.0
• UP-2424 - Add example request person attribute dao
• UP-2551 - Require JDK6 to compile and run

Bug

• UP-1787 - Detached windows share portlet instance with undetached ones causing odd behaviour
• UP-2095 - Unfriendly AJAX messages when user's session times out
• UP-2223 - Applets with ajax preferences, the AjaxUserPreference menu appear behind applets
• UP-2235 - USER_NAME stylesheet parameter is not populated in universality.xml
• UP-2247 - Users with rows in UP_LAYOUT_STRUCT with type="dlm:*" and name="width" or name="name" don't export their layouts
• UP-2255 - Import scripts don't deal with dlm-delete in layout files
• UP-2259 - Muliple profile support fails for new users
• UP-2272 - JNDI session tracking fails during cross-context access
• UP-2307 - JPA/Hibernate impl of DLM ConfigurationLoader generates DDL with column names that are reserved words on Oracle
• UP-2355 - import-preferences should check that the dlm path ref is not null
• UP-2358 - Export and Import scripts do not fully support all DLM layout functions
• UP-2360 - Guest rendering incorrect after session timeout.
• UP-2369 - import-layout_v3-0.crn no longer imports the THEME_SS_ID correctly
• UP-2377 - User locale isn't passed to theme stylesheet
• UP-2379 - Import/Export tasks should fail if import or export of any entity fails
• UP-2381 - Errant icon in Forgot password link of CLogin
• UP-2390 - Import operations broken in ImportExportPortlet
• UP-2393 - Remove vestigle xsl:if around query initialization
• UP-2403 - Exporting preferences for transient portlets fails
• UP-2405 - RSS channel fails on http: or https: UTF-8 feeds that begin with Unicode BOM
• UP-2407 - problem locking fragment and/or individual portlets in layout
• UP-2408 - incorrect table rendering in group manager
• UP-2409 - Export operations may generate file names that are invalid on Windows
• UP-2410 - DLM ProcessingPipe is a singleton
• UP-2411 - Groups Manager paging controls don't display
• UP-2413 - incorrect column rendering
• UP-2414 - MySQL generates error when creating index UPPERM_IDX on UP_PERMISSION: Specified key was too long; max key length is 1000 bytes
• UP-2417 - WebProxyPortlet channel publishing document in uPortal 3.1.0 is broken
• UP-2419 - If first call to a portlet is an action normal rendering is done
• UP-2420 - EXCLUSIVE fname links don't work
• UP-2421 - Null user attribute value causes NPE in CPersonAttributes
• UP-2422 - Handle null IAuthorizationPrincipal in XalanAuthorizationHelperBean
• UP-2423 - Portlets targeted by fname don't recieve parameters from the URL
• UP-2433 - [Regression] New fluid design does not support arbitrary column widths
• UP-2438 - Flyout navigation uses ID attribute which can produce elements with the same ID
• UP-2441 - database event logging is on by default
• UP-2443 - findbugs automated code review: (possible) null pointer dereferences
• UP-2449 - Main navigation not formatted as a widget when rendered in the sidebar
• UP-2453 - Incorrect property name in ldapContext.xml
• UP-2459 - Portal registration portlet fails to recognise some top level domains in email address
• UP-2461 - USER_INFO map returns the "null" String instead of the null value when no value is there
• UP-2462 - When using MS SQL, InitPortal does not create UP_CHANNEL_MDATA
• UP-2466 - Users are unable to 'Add Members' to groups in which they have permisson ADD/REMOVE members
• UP-2490 - SafeFileNamePhrase removes valid i18n characters
• UP-2491 - PortletEntityRegistryImpl should validate the IPortletEntity before returning it
• UP-2511 - Probable Thread Safety issue with ChannelManager.systemCache
• UP-2512 - HttpSession stack traces when interacting with AJAX portlets
• UP-2514 - Portal not honoring portlet display name as specified in the portlet.xml
• UP-2518 - UP-2047 doesn't seem to work when the portal is configured as the ROOT context
• UP-2519 - No form valiation on channel functional name
• UP-2524 - Add Content dialog - cateogory and portlet lists are blank, search does not function in IE7
• UP-2530 - SmartLdapGroupStore needs to handle null Attribute Maps
• UP-2539 - Calling channels by fname results in a stack trace
• UP-2548 - ''Add Content' modal window does not resize correctly when Search tab selected
• UP-2555 - Install fails on setting application context to ROOT
• UP-2559 - Source encoding not set in pom
• UP-2562 - Portlets randomly fail to render when encoding URLs

This release is indented to be feature complete with the exception of the CSS work. That said there is always the possibility that a bug fix in a RC could cause incompatibility with the GA release.

If you find an issue with this RC please report it in Jira, issues in Jira are how we ensure the bugs are actually addressed.

Important Upgrading Note
uPortal 3.2.0 has had database changes that are incompatible with the previous releases. Upgrading to uPortal 3.2.0 will require using the crn-export scripts in your current install and then the crn-import scripts in your new uPortal 3.2.0 install. Pointing a uPortal 3.2.0 release at an older database will very likely not work and could cause database corruption.

Downloads are available from: http://www.jasig.org/uportal/download/uportal-320-RC1
Release notes are available at: http://www.ja-sig.org/wiki/display/UPC/3.2.0-RC1

uPortal Project Lead,
-Eric Dalquist