3.2.3

Oct/07/10

uPortal 3.2.3 GA announcement

Jasig is proud to announce the general audience release of uPortal 3.2.3. uPortal 3.2.3 is the recommended version with which to start a new uPortal deployment.

The following issues have been addressed for 3.2.3:

Bug

  • UP-2765 - Sitemap tab links make you "stuck" on the selected tab
  • UP-2768 - Fix List<IPortletPreference> persistence to reduce DB churn
  • UP-2781 - uPortal Error When Changing Skin
  • UP-2795 - Unicon News portlet pointed at broken RSS feed
  • UP-2797 - Portal Administrator lacks permission to access Password Management channel
  • UP-2816 - JPA Channel Definition code is poorly cached
  • UP-2828 - JavaScript Error - 'script.parentNode is null or not an object' - upgrade Fluid to 1.2.1 or 1.1.3
  • UP-2829 - Portlet output cache not invalidation when chrom control clicked
  • UP-2830 - QueueingEventHandler dispose throws exceptions if there are queued events
  • UP-2832 - Don't remove guest layout from cache
  • UP-2833 - Gracefully handle poorly configured dlm.xml
  • UP-2834 - Portlet FName URLs ignore additional parameters
  • UP-2835 - Framework webflow portlets don't minimize
  • UP-2839 - Lifecycle options don't display for portlets with no categories
  • UP-2840 - Logging of XML in StaticRenderingPipeline uses inconsistent checks

Improvement

  • UP-2258 - Add name to iframe channel
  • UP-2762 - Handle orphaned/corrupt channel SUBSCRIBE permissions more gracefully in export-channel.crn (Import/Export)
  • UP-2777 - Enhance SmartLdap to refresh group relationships without a server restart
  • UP-2804 - Improve uPortal 3.x performance by avoiding the persistence of unused portlet entities.
  • UP-2817 - Check JDK Version in quickstart ant script
  • UP-2838 - Lengthen default channel rendering timeout from 500ms to 5,000ms
  • UP-2841 - Allow CDATA to be used in .channel files

Important 3.2 Upgrading Note

uPortal 3.2 has had database changes that are incompatible with the previous releases. Upgrading to uPortal 3.2 from 3.1 or older will require using the crn-export scripts in your current install and then the crn-import scripts in your new uPortal 3.2 install. Pointing a uPortal 3.2 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-323
Release notes are available at: https://wiki.jasig.org/display/UPC/3.2.3

-Eric Dalquist

Deployer Notes

  • Requires Servlet API 2.5 to run. Tomcat 6.0 is the first version of Tomcat to support Servlet 2.5
  • Requires JDK 6.0
  • Data export and import is required when upgrading.

Bugs known to afflict uPortal 3.2.3

priority key summary

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Issues addressed in uPortal 3.2.3

type priority key summary

Unable to locate Jira server for this macro. It may be due to Application Link configuration.