EditLive! for IWWCM 6.0+ 3.0.1.55

January 28th, 2007

Bug Fixes

  • Inability to save after installing iFix PK36153: Text loss in the Rich Text Editor. This was released as an individual iFix for version 6.0.0 but has also been released with the cumulative iFix PK35618 for 6.0.0.1.
  • IE7 is now officially supported (once the correct IWWCM updates are installed).

EditLive! for IWWCM 6.0+ 3.0.1.45

January 24th, 2007

New Features

  • An upgrading article has been added to the IWWCM 6.0 integration documentation.

Bug Fixes

  • Installer now works on IWWCM 6.0.0.1
  • Style element was empty causing the document to lose style info
  • @@!IWWCMROOT!@@ had been replaced with an absolute URL to our test IWWCM environment.
  • Installer put the portlet installation files in the wrong directory
  • Documentation for IWWCM 6.0 integration now better explains how to enable config based on user/group
  • IWWCM 6.0 integration now correctly implements config file based on user if the user has a first and last name specified.

EditLive! for IWWCM 6.0+ 3.0.0.66

December 1st, 2006

New Features

  • IWWCM 6.0 documentation now specifies a link to the IBM Information Center so developers can ensure users have installed the required JRE.
  • Documentation for the IWWCM 6.0 integration now includes instructions on how to uninstall the integration.

EditLive! for IWWCM 6.0+ 3.0.0.50

November 27th, 2006

New Features

  • IWWCM integrations (v3.0) now reference EditLive! v6.0.0.1610
  • Automatically install ant script for the IWWCM 6.0 integration modified to add EditLive! to the inline editing interface.
  • Manual installation steps added for the IWWCM 6.0 integration to add EditLive! to the inline editing interface.
  • Current IWWCM user’s name sent to EditLive! to be used by track changes

Fixes

  • EditLive! 6.0 configuration files used for IWWCM integrations now use the 6.0 trial license instead of the 5.0 trial license.
  • Spellcheck and thesaurus configuration file elements commented out (in IWWCM 6.0 config file) to allow the jar location to be automatically generated.