The Oracle Portal 10.1.4 upgrade was sucessfully implemented but there are still a few outstanding issues

Oracle Portal 10.1.4 Upgrade Outstanding Issues at 27 April 2006

• Issue: Cannot display members of large groups
  Status: Known Oracle bug - with Oracle to resolve
  Workaround: The Web Team can add or remove group members for you, or check the groups to which an individual user belongs. Email any such requests to the Service Desk
  
  
• Issue: Cannot overwrite Content Items larger than 4000 characters
  Status: Expected to be fixed in Friday 28/4/2006 update. 19/5/2006 - now fixed.
  Workaround: The Web Team changed the way the Content Editor worked when saving large content items so that it ALWAYS created a new version, even if you specified 'Overwrite'. Here are instructions for removing unwanted versions.
  
  
• Issue: On PWP home pages, the information bottom right was not shown.
  Status: Expected to be fixed in Friday 28/4/2006 update. 2/5/2006 - now fixed.
  Workaround: The information is available on the Personal Information pages of PWPs.
  
  
• Issue: Filtered searches of CMS sites do not return any pages from the sites. They do return linked documents e.g. PDFs.
  Status: Expected to be fixed in Friday 28/4/2006 update. 2/5/2006 - now fixed.
  Workaround: Site owners could direct visitors to the main search until the filtered searches are restored.
  
  
• Issue: In Navigator, if you use Find to locate a site, then click on Sub-pages, you get an error message 400 Bad Request
  Status: We have registered this bug with Oracle and are waiting on a patch from them.
  Workaround: In Navigator, locate the required site by using Next and Previous to go through the list of sites instead of using Find.
  
  
• Issue: When assigning permissions and you select a user or group from the displayed list, the user or group name is not inserted into the permission field. This is a bug brought forward from the previous version of Oracle Portal.
  Status: We have registered this bug with Oracle and are waiting on a patch from them. December 2006 - fixed when new architecture implemented.
  Workaround: Once you have identified the user login or group name, copy or type it into the permission field.