Latest fixes for Lotus Connections 2.0

A list of the fixes that IBM released after fixpack 1 of Lotus Connections 2.0.

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.

This entry was posted in lotus connections and tagged . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

Please leave these two fields as-is:

Protected by Invisible Defender. Showed 403 to 807,320 bad guys.