Summary & Highlights

Welcome to Linchpin Essentials 1.2!

The Linchpin Essentials 1.2 release contains several patches for Linchpin. We introduced some new features, improved some more features and took care of several bugs.

We prepared a short summary of the most important changes, so you can keep track of them. If you want more info about a specific function, use the navigation to jump to this function's release notes.

Let's begin with Linchpin User Profiles and probably the biggest change in this release. We completely reworked the profile editor (within the configuration). It is now more intuitive, easier to use and it's also a lot faster. The creation of profile fields and section (formerly known as groups) now happens in a sidebar so you never have to leave the editor.

We also removed the formerly deprecated "Phone" profile field. It is replaced by the "Phone with number validation" field type which was already introduced in LUP 2.20. Furthermore, we opened the user profile API to read and write data into profile fields.

Navigation menus received support for internal links with query parameters and we fixed a bug in Linchpin Theme concerning small issues with the sidebar icons and tooltips in some environments.

Theme

Linchpin Theme received some small bugfixes and improvements. We fixed an issue concerning sidebar icons and adjusted the default theme's app name to show that it is part of the Linchpin Theme.

Bugfixes

• There have been small issues in the sidebar regarding icons and tooltips in some environments. These have been fixed.
• We adjusted the default theme's app name to show that it is part of the Linchpin Theme.
• 1.2.1 We fixed a bug where the correct vCard was not displayed when hovering over a space creator within the space directory.
  
• 1.2.2 The "Spaces" macro of the Linchpin Space Directory now doesn't break column layouts in Internet Explorer 11 anymore.
  

Navigation

In this release we added support for internal links with query parameters within Navigation Menus.

New features

• Added support for internal links with query parameters in Navigation Menus.

User profiles

User Profiles received a massive overhaul! We completely renewed the profile editor. It is now faster, easier and much more usable. Make sure to check out the documentation regarding an update to see what changed and what to pay attention to. Furthermore, we opened the user profile API to write data into profiles (in addition to read permissions). And the "Phone" profile field is gone now. It was replaced with the "Phone with validation" field type introduced in 2.20.

New features

• We opened the user profile API to not only read but also to write data into profiles. See the current state of the API documentation here: https://info.seibert-media.net/display/DOC/Developer+Guide#cbd62d33fff647b78823cd8d5a7c54e4
  We are very happy to hear from you if you plan to use the API. Feedback gives us the chance to learn about your use cases and to improve our solution.
• 1.2.1 When using an XML data source for select or multi-select fields, there's no need to create all field options manually anymore.
  
  
  • Users that are not included in the XML file can still edit these fields themselves. They now can choose from all imported values. This also works in Linchpin Assistant and Onboarding.
  • People directory filters for these fields now also show all imported values.

    Known issue
    When importing XML into a multi-select field, we currently don't support multiple XML tags like <node>A</node><node>B</node>. As a workaround, use JSON array strings in a single tag like <node>["A","B"]</node>.

Improvements

• We have completely renewed the profile configuration to be faster, easier and much more usable. Attention: Please read this notice before updating: https://seibert.biz/lup222
• We removed the deprecated field type "Phone". It is replaced by the field type "Phone validated" we introduced in 2.20. Please read this notice before updating: https://seibert.biz/lup222
• 1.2.2 We added support for the umlauts and special characters (ä, å, æ, á, à, â, etc.) within the user search.

Bugfixes

• The "customized" mode of the "Profile" macro now properly displays the configured fields.
• The "Content Responsibility" macro now works correctly, even if collaborative editing is turned off.
• You can sort the "Customized User List" macro by fields that are not displayed.
• Filtering country select fields in the people directory works correctly now.
• We fixed several issues with required and/or validated phone fields when using Linchpin Assistant or Onboarding.
• 1.2.1 The subline configuration for vcards in INFO mode now works as expected.
• 1.2.1 The status icon for Skype users is now displayed correctly as circle.
• 1.2.1 Links from linked profile fields are now shown correctly and clickable in profile macro and vcard.
• 1.2.1 The filter of the Custom User Search macro now supports linked fields correctly.
• 1.2.1 The values for Dependent Field mappings are now correctly displayed in the profile editor.
• 1.2.1 The ordering of profile sections is now always correct.
• 1.2.1 Profile and avatar pictures are now always displayed correctly and not distorted.
• 1.2.1 We fixed issues regarding compatibility with Refined Theme.
• 1.2.1 Values of multiselect fields are now displayed correctly in profile headers.

• 1.2.1 We fixed the user group restriction configuration for profile sections.
  

• 1.2.2 We fixed compatibility issues with the "Custom Space User Management (CSUM)" app.
• 1.2.2 We fixed the mobile view in Confluence > 7.x.
• 1.2.2 We fixed the usability issue within the profile field configuration.

• 1.2.2 Validated phone numbers, which are imported via XML file, no longer block saving the profile if they are invalid.
  

Complete changelog

Here is a complete overview of all of the changes that we've implemented in our Linchpin Essentials release.

New features

• Added support for internal links with query parameters in Navigation Menus.
• We opened the user profile API to not only read but also to write data into profiles. See the current state of the API documentation here: https://info.seibert-media.net/display/DOC/Developer+Guide#cbd62d33fff647b78823cd8d5a7c54e4
  We are very happy to hear from you if you plan to use the API. Feedback gives us the chance to learn about your use cases and to improve our solution.
• 1.2.1 When using an XML data source for select or multi-select fields, there's no need to create all field options manually anymore.
  
  
  • Users that are not included in the XML file can still edit these fields themselves. They now can choose from all imported values. This also works in Linchpin Assistant and Onboarding.
  • People directory filters for these fields now also show all imported values.

    Known issue
    When importing XML into a multi-select field, we currently don't support multiple XML tags like <node>A</node><node>B</node>. As a workaround, use JSON array strings in a single tag like <node>["A","B"]</node>.

Security

• 1.2.3 We fixed a potential security risk within the edit mode of profile fields. Some field types could be used to inject unwanted scripts. 
  For more information please see our knowledge base article: https://seibert.biz/vulnerability-notification-2020-09-11

Improvements

• We have completely renewed the profile configuration to be faster, easier and much more usable. Attention: Please read this notice before updating: https://seibert.biz/lup222
• We removed the deprecated field type "Phone". It is replaced by the field type "Phone validated" we introduced in 2.20. Please read this notice before updating: https://seibert.biz/lup222
• 1.2.2 We added support for the umlauts and special characters (ä, å, æ, á, à, â, etc.) within the user search.
• 1.2.3 Linchpin App Usage received support for read only-mode.
• 1.2.3 We removed the favorite button and the favorite view within the space directory and the "Spaces" macro for anonymous users.

Bugfixes

• There have been small issues in the sidebar regarding icons and tooltips in some environments. These have been fixed.
• We adjusted the default theme's app name to show that it is part of the Linchpin Theme.
• The "customized" mode of the "Profile" macro now properly displays the configured fields.
• The "Content Responsibility" macro now works correctly, even if collaborative editing is turned off.
• You can sort the "Customized User List" macro by fields that are not displayed.
• Filtering country select fields in the people directory works correctly now.

• We fixed several issues with required and/or validated phone fields when using Linchpin Assistant or Onboarding.
  

• 1.2.1 The subline configuration for vcards in INFO mode now works as expected.
• 1.2.1 The status icon for Skype users is now displayed correctly as circle.
• 1.2.1 Links from linked profile fields are now shown correctly and clickable in profile macro and vcard.
• 1.2.1 The filter of the Custom User Search macro now supports linked fields correctly.
• 1.2.1 The values for Dependent Field mappings are now correctly displayed in the profile editor.
• 1.2.1 The ordering of profile sections is now always correct.
• 1.2.1 Profile and avatar pictures are now always displayed correctly and not distorted.
• 1.2.1 We fixed issues regarding compatibility with Refined Theme.
• 1.2.1 Values of multiselect fields are now displayed correctly in profile headers.

• 1.2.1 We fixed the user group restriction configuration for profile sections.

• 1.2.1 We fixed a bug where the correct vCard was not displayed when hovering over a space creator within the space directory.
  

• 1.2.2 The "Spaces" macro of the Linchpin Space Directory now doesn't break column layouts in Internet Explorer 11 anymore.
  

• 1.2.2 We fixed compatibility issues with the "Custom Space User Management (CSUM)" app.
• 1.2.2 We fixed the mobile view in Confluence > 7.x.
• 1.2.2 We fixed the usability issue within the profile field configuration.

• 1.2.2 Validated phone numbers, which are imported via XML file, no longer block saving the profile if they are invalid.

• 1.2.3 We fixed a bug which restricted the access to admin REST resources within Linchpin App Usage.

Linchpin Essentials 1.2.1

Version 1.2.1 of Linchpin Essentials is a patch release.

We introduced a new feature for Linchpin User Profiles - XML import of profile field data does not require a manual creation of all fields anymore.

Furthermore we fixed some bugs, most of which affected user profiles in one way or another - like the bug affecting the sorting of profile sections or the bug which prevented profile pictures to be displayed correctly.

New feature

• When using an XML data source for select or multi-select fields, there's no need to create all field options manually anymore.

• Users that are not included in the XML file can still edit these fields themselves. They now can choose from all imported values. This also works in Linchpin Assistant and Onboarding.
• People directory filters for these fields now also show all imported values.

  Known issue
  When importing XML into a multi-select field, we currently don't support multiple XML tags like <node>A</node><node>B</node>. As a workaround, use JSON array strings in a single tag like <node>["A","B"]</node>.

Bugfixes

• The subline configuration for vCards in INFO mode now works as expected.
• The status icon for Skype users is now displayed correctly as circle.
• Links from linked profile fields are now shown correctly and clickable in profile macro and vCard.
• The filter of the Custom User Search macro now supports linked fields correctly.
• The values for Dependent Field mappings are now correctly displayed in the profile editor.
• The ordering of profile sections is now always correct.
• Profile and avatar pictures are now always displayed correctly and not distorted.
• We fixed issues regarding compatibility with Refined Theme.
• Values of multiselect fields are now displayed correctly in profile headers.

• We fixed the user group restriction configuration for profile sections.

• We fixed a bug where the correct vCard was not displayed when hovering over a space creator within the space directory.

Linchpin Essentials 1.2.2

Version 1.2.2 of Linchpin Essentials is a patch release. We provide fixes to some bugs, like the broken User Profiles mobile view or the "Spaces" macro breaking the Space Directory layout, and furthermore we also added support for the Germanic umlaut within the user search.

Improvements

• We added support for the umlauts and special characters (ä, å, æ, á, à, â, etc.) within the user search.

Bugfixes

• We fixed compatibility issues with the "Custom Space User Management (CSUM)" app.
• We fixed the mobile view in Confluence > 7.x.
• We fixed the usability issue within the profile field configuration.
• Validated phone numbers, which are imported via XML file, no longer block saving the profile if they are invalid.
• The "Spaces" macro of the Linchpin Space Directory now doesn't break column layouts in Internet Explorer 11 anymore.

Linchpin Essentials 1.2.3

Version 1.2.3 of Linchpin Essentials is a patch release.

We fixed a potential security risk within Linchpin User Profiles. It was potentially possible that users with edit permissions could edit profile field values via the browser console. But we took care of it now.

Security

• We fixed a potential security risk within the edit mode of profile fields. Some field types could be used to inject unwanted scripts. 
  For more information please see our knowledge base article: https://seibert.biz/vulnerability-notification-2020-09-11

Improvements

• Linchpin App Usage received support for read only-mode.
• We removed the favorite button and the favorite view within the space directory and the "Spaces" macro for anonymous users.

Bugfixes

• We fixed a bug which restricted the access to admin REST resources within Linchpin App Usage.

Linchpin Essentials 1.2.4

Version 1.2.4 of the Linchpin Essentials is a patch release.

In this release, we fixed a potential security risk within Linchpin User Profiles. During our internal testing, we found a potential security risk within the validated phone number profile field. 

Security

• We fixed a potential security risk within the validated phone number profile field. It could have been potentially used to inject unwanted scripts.
  For more information please see our knowledge base article: https://seibert.biz/kbsecuritynotice239