Add offset to community overview anchor links

Last Update:

Author: Christoph Stoettner
Read in about 1 min · 164 words

Glass Orb with Patterns

Photo by Michael Dziedzic | Unsplash

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.

The link on the left top points to an anchor link on the right side of the Overview

Now the anchor link was clicked, and you see the target anchor is not visible

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:

Now the target anchor is visible

Community Highlights

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

Highlights with a link pointing to an anchor link

Link clicked with default setting

Link clicked with the deployed communities.css

Add a comment
There was an error sending your comment, please try again.
Thank you!
Your comment has been submitted and will be published once it has been approved.

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

Suggested Reading
Card image cap

The official documentation, “Migrating data from MongoDB 3 to 5”, wants to dump the MongoDB databases in 3.6 and then restore this data into the newly deployed MongoDB 5.

One issue with this process is that we can’t run the two MongoDB versions in parallel on Kubernetes because the provided helm charts and container for MongoDB 3.6 stop running after Kubernetes 1.21. On the other side, the helm chart providing MongoDB 5 can’t be installed on those old Kubernetes versions. So the process to update is:

Migration process

  1. Dump databases in MongoDB 3.6 (version delivered with Connections 7)
  2. Update Kubernetes to 1.25 or 1.27
  3. Restore MongoDB databases to version 5.0
Last Update:
Read in about 6 min
Card image cap

After updating HCL Connections to 8CR3 and Tiny Editors to the lines of tables are no longer visible during editing.

Here is the edit form with Tiny Editors

Created: Read in about 2 min
Card image cap

During a troubleshooting session in Component Pack, I checked the Kubernetes events.

Created: Read in about 3 min