- Created by Administrator, last modified on Sep 29, 2023
Documentation's navigation
On this page
Sadly, we aren't perfect, but we are trying to get there! Since Microblog 5.0 was a release with big changes, some minor bugs might appear. We are actively working on the bugs listed here.
Linchpin Essentials
SOLVED IN 1.5.2
The "Atlassian Troubleshooting and Support Tools" app in version 1.32.1 causes problems for the Linchpin Intranet Suite.
For more information, follow the link below:
Linchpin User Profiles
Already fixed issues
| Fixed in | Issue Type | Description of the Issue |
|---|---|---|
| General issue | The "Atlassian Troubleshooting and Support Tools" app in version 1.32.1 causes problems for the Linchpin Intranet Suite. For more information, follow the link below: | |
| Usability issue | After creating a new Extranet user, profile editor fields are missing. After manually creating a new Extranet user, said user, once logged in, won't be seeing restricted profile fields from the profile editor or will see them although they shouldn't. Workaround: Please clear all caches found under | |
SOLVED | Usability issue | Parentheses in filters are treated incorrectly. Since we have introduced complex filters for your custom landing pages, parentheses in filters are treated as logical characters. Your filter might break if you try to filter by attributes which contain parentheses. Workaround: Use the wildcard '?' instead of a parenthesis. |
SOLVED | Usability issue | Multi-select profile field doesn't support multiple XML tags When importing XML into a multi-select field, we currently don't support multiple XML tags like <node>A</node><node>B</node>. Workaround: use JSON array strings in a single tag like <node>["A","B"]</node>. See the corresponding section in our documentation for details about this. |
SOLVED | Usability issue | There are problems with profile picture uploads with Internet Explorer. In some server configurations, a problem can occur when you upload profile pictures via Internet Explorer. This problem leads to a page with the text "Loading...", and the user is unable to resize the picture. Solution: If this happens, the following snippet can be added to the Apache configuration, which should solve the issue (example for .png-files): <LocationMatch ".*\.png$"> ForceType image/png Header set Content-Disposition inline Header set Content-Type image/png;charset=UTF-8 </LocationMatch> |
SOLVED | Usability issue | People Search and List Macro (PSL) and Codeblock (CB) are partially incompatible while editing a page. If there is a CB macro on a page and you also insert a PSL macro and want to configure the list view the page freezes -> reload necessary. Workaround: To have both PSL and CB on one page and configure the list view of the PSL, first insert the PSL macro and configure the list view. Then insert the CB macro. |
Other known issues
| Issue Type | Description of the Issue |
|---|---|
| Usability issue | The 'My Contacts' macro isn't being displayed in PDF exports. Currently, the 'My Contacts' macro isn't being displayed when you export a page to a PDF file. |
| Usability issue | Links which contain single quotation marks do not work properly. Inside the configuration of LUP, some links may be broken if they contain the single quotation mark ('). |
| Usability issue | "Profile Updated" by Anonymous due to Confluence Synchronization When Confluence synchronizes against any external user management, all of the newly created and updated users will be displayed under the "All Updates" section of the 'Recently Updated' macro on the Confluence dashboard. Considering the amount of users Confluence will create or update from the synchronization, it would be better to be excluded from "All Updates" section or Confluence should provide the option to exclude these updates. Since Confluence 5.5, you can add the following argument in your JVM options to prevent updates to user information appearing in the dashboard: -Dconfluence.dashboard.recentlyupdate.filtertypes=page,comment,blogpost,attachment,spacedesc,personalspacedesc,status |
| Usability issue | Copying content and the 'Content Responsibility' macro The 'Content Responsibility' macro maintains its own data structure separate from Confluence content (pages, blog posts or dashboards). As a result, when you copy content including the macro (manually or through third-party apps like bitvoodoo's Templates for Blog Posts for Confluence), the resulting pages will require you to fill out the responsible user(s) again and save/update the content. The macro settings will carry over. Embedding the 'Content Responsibility' macro in blueprints is supported, but the created pages will also need to be saved/updated once for the data to be handled correctly. |
Usability issue | The "Date input" field gets corrupted on mobile devices. 3.0.0 MOBILE 4.2.0 The "Date input" field can be corrupted (saving the field would result in an error 400) when another user profile field uses an empty space as an ending character. |
| Visual / UI issues | Sometimes the profile editor displays Skype configuration options for the XMPP instant messenger field type. If a Skype IM field was created first, and then a XMPP IM field is created, the profile editor will still display the configuration for Skype instead the one for XMPP. |
| Visual / UI issues | The 'Customized User List' macro displays horizontal lines double. The horizontal lines separating profile fields are displayed double inside the macro. |
| Visual / UI issues | If a second Skype for Business instant messenger fields is configured to show the online status, a wrong message appears. If a second Skype for Business instant messenger field is inserted into a profile and it's configured to show the online status, a message asking to replace profile field data will be displayed (this should not be the case). |
Have you found another issue or do you have a stronger need to fix one of these issues? Tell us here.
Simply visit our feedback board in Canny and create a feature idea, vote for existing posts or discuss your ideas with other customers.
Linchpin Theme
Already fixed issues
| Fixed in | Issue Type | Description of the Issue |
|---|---|---|
General issue | The "Atlassian Troubleshooting and Support Tools" app in version 1.32.1 causes problems for the Linchpin Intranet Suite. For more information, follow the link below: Knowledge Base: "Atlassian Troubleshooting and Support Tools" app causes health checks to freeze and blocks the creation of support zips | |
SOLVED | General issue | The Confluence site logo image causes a "to many open files" issue. CONFL. BUG Even after increasing the open file limit as described here Too many open files error, it does not prevent Confluence to crash. Actually, the issue is based on the Confluence platform itself even though it appears that the Linchpin Theme app is involved. The data storage of the logo which is uploaded via the Linchpin theme configuration (/admin/linchpin/theme/configure.action) is always a Base64-encoded string, i.e. it is not a file nor attachment and ultimately not stored in the file system. However, the Linchpin theme also sets the regular site logo of Confluence as well using a standard Confluence API method. That site logo can be seen even without an active or applied Linchpin theme (e.g. in the admin area on the top left). As a matter of fact, that Confluence site logo is an attachment file, i.e. a file in the file system which can be affected by the stated issue. Solution: As we learned through our customer support case, the Confluence system has been upgraded to version 7.16.2 while using Java 8. Once they've updated their system to Java 11 the customer was able to fix the problem. |
SOLVED | Usability issue | Caches sometimes freeze. CONFLUENCE 7.10 LTP 2.23.3 We noticed that Linchpin Theme sometimes has an issue with the cache. Solution: Clear your cache. This should solve this issue. |
SOLVED | Usability issue | Theme reset to Confluence default after upgrade of Linchpin apps. Updating Linchpin Theme disables the theme for a brief period. If the Confluence system is accessed by another user during this time, it detects a "missing" theme and resets Confluence to the default theme. Solution: To repair this, simply activate the theme again. Starting with Confluence 6.15 this is not an issue anymore, so we suggest updating. |
SOLVED | Visual issue | Sidebar icons break when a system is migrated from HTTP to HTTPS. If you migrate your system from HTTP to HTTPS, the sidebar might display broken icons. The issue exists because the sidebar uses the base URL of the system to load faster. Sadly, the sidebar does not flush the cache automatically, that's why you have to do it yourself after performing a migration. Workaround: To fix this issue, please navigate to Confluence administration → Cache management. Look for the net.seibertmedia.confluence.linchpin-sidebar.cache.sidebar.v2 key and click on the Flush button. |
SOLVED | Usability issue | Settings for not showing the menu in space themes get reset. When using space themes with deactivated menu and upgrading to Linchpin Theme 2.19.x or Linchpin Suite 2.x, the settings for the menu get reset to default. That means that the spaces using those space themes will show the menu. Workaround: The setting has to be corrected once after the upgrade, from then on they keep their settings. |
Other known issues
| Issue Type | Description of the Issue |
|---|---|
| Usability issue | Teaser images are missing in PDF exports. Teaser images are missing when a page is exported to a PDF. |
| Usability issue | A time-out leads to lost changes in menu configuration. Changes in the menu configuration can disappear when the admin times-out. |
| Visual issue | A 1/3 page layout makes the Spaces macro disappear. The Spaces macro can disappear when displayed in a 1/3 page layout. |
| Visual issue | Pop-ups are displayed in wrong positions. The login page sometimes can cause pop-ups to appear in wrong positions. This is fixed with Linchpin Theme 2.20.4. |
| Visual issue | Text inside the header might appear cut-off. Text inside the action drawer (header) can appear cut-off when it's displayed in two rows. |
| Visual issue | The placeholder text inside the search bar might appear cut-off. The placeholder text inside the search bar (for example: "Type to use the search") can appear cut-off. |
| Compatibility Issue | The following apps and versions are known to have compatibility issues with the Linchpin Theme. These might have been addressed by a more recent release of the third party apps.
|
Have you found another issue or do you have a stronger need to fix one of these issues? Tell us here.
Simply visit our feedback board in Canny and create a feature idea, vote for existing posts or discuss your ideas with other customers.
Link to this page: https://seibert.biz/linchpinessentials-known-issues