Skip to main content

Add offset to community overview anchor links

Our users are often building Highlights and Overview pages within HCL Connections Communities, where they link from one description widget to RTE or from one RTE widget to another.

We found that these anchor links often disappear behind the top navigation bar and the users wonder what happened.

I created a customization file in <SHARED DIRECTORY>/customization/themes/hikariTheme/applications/communities.css with the following content:

html {
  scroll-padding-top: 250px;
}

Changed the versionStamp in LotusConnections-config.xml and restarted the application servers. Now when we click the link in Communities Overview:

Community Highlights
#

The same offset can be seen in the Highlights App and the solution above will solve it there too.

Christoph Stoettner
Author
Christoph Stoettner
I work at Vegard IT GmbH as a senior consultant, focusing on collaboration software, Kubernetes, security, and automation. I primarily work with HCL Connections, WebSphere Application Server, Kubernetes, Ansible, Terraform, and Linux. My daily work occasionally leads to technical talks and blog articles, which I share here more or less regularly.

Related

KB: PushNotification broken after upgrading to CFix.65CR1.2201

Yesterday I updated a Connections environment to the latest CFix. In other environments I found that PushNotification Cluster was not started after the update, like described in the knowledge base document PushNotification broken after upgrading to CFix.65CR1.2201. In this update the application and cluster were running, but not working at all. Browser console.log showed the error: Error connecting to push auth sync service /servic/info: RequestError: Unable to load https://cnx-fqdn/push/service/info status: 500

Change the Connections editor on the fly

·256 words·2 mins
When I test topics with the different Connections editors (CKEditor, Textbox.io and TinyMCE), I always used multiple users in my test environment, installed the editor selector ear and then gave each of the test users a different editor. That’s easy with the different j2ee roles, but I always had to use multiple browsers or sandboxes to see them next to each other.