For the fixes and what they fix see the list below.

Use this url http://www-933.ibm.com/support/fixcentral/ to download these new ifixes.

Fix name:     2.0.1.0-LC-Multi-IFLO35859
Release date:     22-Dec-2008
Platforms:     AIX, Linux, Windows
Applies to versions:     2.0.1.0
Severity:     20 – High Impact/Medium Probability of Occurrence
Categories:     Function
Abstract:     Profiles: InLine Business card formats poorly in IE, makes the card unusable.

Fix name:     2.0.1.0-LC-Multi-IFLO35655
Release date:     22-Dec-2008
Platforms:     AIX, Linux, Windows
Applies to versions:     2.0.1.0
Severity:     30 – Moderate Impact/High Probability of Occurrence
Categories:     Compatibility
Abstract:     Allow PNG photos for upload to Profiles.

Fix name:     2.0.1.0-LC-Multi-IFLO36131
Release date:     22-Dec-2008
Platforms:     AIX, Linux, Windows
Applies to versions:     2.0.1.0
Severity:     30 – Moderate Impact/High Probability of Occurrence
Categories:     Function
Abstract:     /activities/service/html/autocompletemembers?member needs to return extid

Fix name:     2.0.1.0-LC-Multi-IFLO35840
Release date:     22-Dec-2008
Platforms:     AIX, Linux, Windows
Applies to versions:     2.0.1.0
Severity:     30 – Moderate Impact/High Probability of Occurrence
Categories:     Function
Abstract:     Modification of CSS styles specific to IE to fix dojo dialog to 400px height

Fix name:     2.0.1.0-LC-Multi-IFLO36188
Release date:     20-Dec-2008
Platforms:     AIX, Linux, Windows
Applies to versions:     2.0.1.0
Severity:     20 – High Impact/Medium Probability of Occurrence
Categories:     Function
Abstract:     Communities: IE browser hangs when posting a topic in Community Discussion Forums.

Fix name:     2.0.1.0-LC-Multi-IFLO35860
Release date:     20-Dec-2008
Platforms:     AIX, Linux, Windows
Applies to versions:     2.0.1.0
Severity:     30 – Moderate Impact/High Probability of Occurrence
Categories:     Function
Abstract:     Profiles: Cache issues in widgets and javlin card. When changing browser’s locale setting from English to French, the UI screens displayed in the new language for the current page, and all other future navigation.

Fix name:     2.0.1.0-LC-Multi-IFLO35887
Release date:     20-Dec-2008
Platforms:     AIX, Linux, Windows
Applies to versions:     2.0.1.0
Severity:     30 – Moderate Impact/High Probability of Occurrence
Categories:     Function
Abstract:     Profiles: For non-default ProfileType (for e.g., profileType=test), the page displays default widgets if the ProfileType does not define its own set of widgets.

Fix name:     2.0.1.0-LC-Multi-IFLO35785
Release date:     15-Dec-2008
Platforms:     AIX, Linux, Windows
Applies to versions:     2.0.1.0
Severity:     30 – Moderate Impact/High Probability of Occurrence
Categories:     Data
Abstract:     This is a change to allow the Connections antivirus software to work with Mcafee and Symantec ICAP scanners. Previously, the code only worked for Symantec.

Fix name:     2.0.1.0-LC-Multi-IFLO35784
Release date:     15-Dec-2008
Platforms:     AIX, Linux, Windows
Applies to versions:     2.0.1.0
Severity:     30 – Moderate Impact/High Probability of Occurrence
Categories:     Data
Abstract:     This is a change to allow the Connections antivirus software to work with Mcafee and Symantec ICAP scanners. Previously, the code only worked for Symantec.

Fix name:     2.0.1.0-LC-Multi-IFLO35783
Release date:     15-Dec-2008
Platforms:     AIX, Linux, Windows
Applies to versions:     2.0.1.0
Severity:     30 – Moderate Impact/High Probability of Occurrence
Categories:     Data
Abstract:     This is a change to allow the Connections antivirus software to work with Mcafee and Symantec ICAP scanners. Previously, the code only worked for Symantec.

Fix name:     2.0.1.0-LC-Multi-IFLO35782
Release date:     12-Dec-2008
Platforms:     AIX, Linux, Windows
Applies to versions:     2.0.1.0
Severity:     30 – Moderate Impact/High Probability of Occurrence
Categories:     Data
Abstract:     This is a change to allow the Connections antivirus software to work with Mcafee and Symantec ICAP scanners. Previously, the code only worked for Symantec.

Fix name:     2.0.1.0-LC-Multi-IFLO35377
Release date:     01-Dec-2008
Platforms:     AIX, Linux, Windows
Applies to versions:     2.0.1.0
Upgrades to version:     2.0.1.0
Severity:     30 – Moderate Impact/High Probability of Occurrence
Categories:     Data
Abstract:     There are two problems here, 1) It required the client to provide a ’slug’ header in order to upload a file, which should be optional, so the fix is to make this optional. When slug header is not provided a random file name will be generated. 2) when the slug header is provided, the file separator ‘.’ is missing so, instead of <slug>.extension you get <slug>extension, fix is to add the ‘.’.

Fix name:     2.0.1.0-LC-Multi-IFLO35376
Release date:     01-Dec-2008
Platforms:     AIX, Linux, Windows
Applies to versions:     2.0.1.0
Upgrades to version:     2.0.1.0
Severity:     30 – Moderate Impact/High Probability of Occurrence
Categories:     Data
Abstract:     The problem here is that the feed/entries/atom Atom feed supports tag filtering, however, it only works when ONE tag is provided, if using multiple tags then the filter will fail. This iFix is for supporting mutliple tags filtering.

You can download them at the fixcentral of IBM at the following
url -> http://www-933.ibm.com/eserver/support/fixes/fixcentral

Below a list of the fixes and what they are fixing .

LO32241: Keyword search (tagged by) does not work in Profiles

When tagging is enabled in Profiles, users can tag themselves and other users. Users can search a profile using the name of the tag. Due to Lucene indexing, this tag is not indexed so the user is unable to find those profiles. No error information is logged; however, it does not work properly.

Apply this fix to resolve the keyword search by tags.

LO32153: Blog comments spam problem

Connections blog requires users to be authenticated to post a comment. However, hackers can figure out a way to send an empty or invalid authentication header and post a comment without being authenticated.

With this fix, the hacker should not be able to post comments without authentication.

LO32651: ProfilesAPI: Compatibility: HCARD format changed in 2.0

In 1.0.2, the HCARD formatted the users telephone numbers as a series of <div class=”tel”>, all at the same level, without nesting.

The same information in 2.0 is formatted differently. The elements for cell, fax, and other numbers are nested within the div for the work number. This breaks API clients programmed to expect the following behavior.

<div class=”tel”>
<abbr class=”type” title=”work”>Work:</abbr>
<span class=”value”>
</span>
</div>
<div class=”tel”>
<abbr class=”type” title=”cell”>Cell:</abbr>
<span class=”value”>
</span>
</div>
<div class=”tel”>
<abbr class=”type” title=”fax”>Fax:</abbr>
<span class=”value”>
</span>
</div>
<div class=”tel”>
<abbr class=”type” title=”x-ip”>IP:</abbr>
<span class=”value”>
</span>
</div>
<div class=”tel”>
<abbr class=”type” title=”pager”>Pager:</abbr>
<span class=”value”>
</span>
<span class=”x-pager-id”>
</span>
<span class=”x-pager-type”>
</span>
<span class=”x-pager-provider”>
</span>
</div>

Note: This iFix also fixes the “About me missing from API response” issue. If the Background field is empty in a user’s Profile, both the “About Me” and “Background” fields are empty in the XML feed, even though there is content stored in the “About Me” field (which is visible through the web interface). Two actual feeds received are provided below. Both Profiles contain the string “Profile x.x” in the About Me field. The 1.0 server feed properly includes the About Me content, while the About Me field is empty in the 2.0 server feed.

Note: the “About Me” field is tagged as <div class=”x-description”> in the feeds.

Install this iFix to resolve HCARD format change in 2.0 and XML Feed from API response.

LO32615: WorkLocation city/state do not get shown in Job Information section

A number of attributes are not displayed in the Lotus Connections profile even though they are configured for display and populated in the database. These fields are:

Address 1
Address 2
City
State
Postal code

LO31730: Intermittent org.xml.sax.SAXParseException’s on Activities Server start

Activities will intermittently fail to start because of SAXParseExceptions received by the VenturaConfigurationProvider when the LCUserDataConstraintFilter is requesting the value of a parameter from LotusConnections-config.xml.

Because of the intermittent nature, IBM believes that the cause is some non-thread-safe logic in one of the org.apache.xerces packages and is investigating concurrency protection at the VenturaConfigFileValidator.validateConfigurationFile method.

org.xml.sax.SAXParseException: The version is required in the XML declaration.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util
.ErrorHandlerWrapper.fatalError(Unknown Source)
at org.apache.xerces.impl
.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl
.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl
.XMLScanner.reportFatalError(Unknown Source)
at org.apache.xerces.impl
.XMLScanner.scanXMLDeclOrTextDecl(Unknown Source)
at org.apache.xerces.impl
.XMLDocumentFragmentScannerImpl.scanXMLDeclOrTextDecl(Unknown Source)
at org.apache.xerces.impl
.XMLDocumentScannerImpl$XMLDeclDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl
.scanDocument(Unknown Source)
at org.apache.xerces.impl.xs.opti
.SchemaParsingConfig.parse(Unknown Source)
at org.apache.xerces.impl.xs.opti
.SchemaParsingConfig.parse(Unknown Source)
at org.apache.xerces.impl.xs.opti
.SchemaDOMParser.parse(Unknown Source)
at org.apache.xerces.impl.xs.traversers.XSDHandler
.getSchemaDocument(Unknown Source)
at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaLoader
.loadSchema(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaLoader
.processJAXPSchemaSource(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator
.findSchemaGrammar(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator
.handleStartElement(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator
.startElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl
.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher
.scanRootElementHook(Unknown Source)
at org.apache.xerces.impl
.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl
.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration
.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration
.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser
.parse(Unknown Source)
at com.ibm.ventura.internal.config.VenturaConfigFileValidator
.parseDocument(VenturaConfigFileValidator.java:124)
at com.ibm.ventura.internal.config.VenturaConfigFileValidator
.validateDoc(VenturaConfigFileValidator.java:100)
at com.ibm.ventura.internal.config.VenturaConfigFileValidator
.validateConfigurationFile(VenturaConfigFileValidator.java:65)
at com.ibm.ventura.internal.config.VenturaConfigurationProviderImpl
.getConfiguration(VenturaConfigurationProviderImpl.java:303)
at com.ibm.ventura.internal.config.VenturaConfigurationProviderImpl
.getGlobalConfiguration(VenturaConfigurationProviderImpl.java:270)
at com.ibm.lconn.core.web.auth.LCUserDataConstraintFilter
.init(LCUserDataConstraintFilter.java:114)

LO31863: Discussion Forum topics greater than 2K of text not displaying properly

Scenario:

- Create a new Community
- Create a discussion Forum Topic. Paste in some text (more than 2K of text). Copy and past the text from the file.
- Save the topic.

Because the topic contains text greater than 2K, you can see that it does store the information in the “forum content store” subdirectory (which is specified in forum-config.xml). That (content store) appears to be working properly.

However, when you look at the Discussion topic in the browser, you can see that there is information missing; the topic is cut off. Activities also does this; however, it also displays a “More” link, so that you can click on it and load the remainder of the topic.

With this fix, a Discussion Forum can also be seen in the same implementation as Activities. You would see the “More” link if the topic is greater than 2K.