BlueSpice 5/Content changes

The following content changes may affect your wiki. Please review them and make any adjustments to your wiki as needed.

Blog functionality

Blog entries are now displayed differently than in previous versions. Your existing blog posts from a previous BlueSpice version will remain available, but the display and permissions have changed.

If you frequently used these features in previous versions, please speak to your project manager before updating your system to evaluate any necessary display adjustments, for example, on your portal pages, before upgrading.

The following features are no longer available or have changed:

• Teaser text: The blog feature now automatically shows a certain number of characters on the blog parent page for each blog entry.
• Page association: There is no field for adding associated page names for a blog entry. Since blog entries are now wiki pages, pages can be associated via categories or semantic properties.
• Recommend: There is no recommendation feature for blog posts.
• Blog permissions for embedded blogs: It is no longer possible to embed blogs into other wiki pages with individual group permissions for each blog. Permissions are now set on the namespace Blog and apply to all blog entries. Only user blogs have special permissions, since they can only edited by each user themselves.

Discussions

Discussions are now handled by the extension CommentStreams and are called "Comments". Your existing discussion from a previous BlueSpice version will remain available, but watch out for some changes.

The following features are no longer available or have changed:

• Behavior switch __NODISCUSSION__: To hide the comments section on a single page, you now need to use the tag <no-comment-streams />.
• CSS to hide the discussion area in namespaces or the entire wiki (e.g. on page MediaWiki:Common.css): This CSS no longer applies. Disable the Comments feature for a namespace in the namespace manager.
• Closing a discussion topic: It is not possible to close a page comment.

PDF export

PDF templates

• Cloud wikis: Make sure to read the documentation on how to copy your template customization to the new template pages. Your customization will still work in BlueSpice 5 after moving it to the new pages. In addition, you now have much more flexibility, because you can now set up more than one template.
• On-premise wikis: Before upgrading your wiki, talk to your project manager about migrating your custom PDF templates from the server directory to the wiki.

Parser tags

The following parser tags are no longer supported and will be visible to users in view mode if you do not remove or replace them.

Important!If pages use the approval-feature and are in approved state, replacing the tags will trigger a new draft version.

PDF parser tag changes

Parser tag in BlueSpice 4	Replacement in BlueSpice 5
<bs:uemeta body-class="noglossary" />	Go to the PDFCreator page for your PDF template. You can use any css class in your PDF slots and style them from the "Styles" tab.
<bs:ueparams template="softwarecatalog" />	This tag allowed to determine a specific template for the PDF export of a wikipage. You can use the content droplet "PDF link" to replace this tag. Since this droplet produces a visible link on the page, you need to wrap it in another content droplet "Exclude content in PDF" (This is best accomplished in source editing mode).
<bs:uenoexport>..excluded content here....</bs:uenoexport />	These tags were also inserted by the Content droplet Exclude content in pdf. The start and end tags for excluding page content from the PDF-export are now replaced with: <pdfexcludestart />...excluded content here....<pdfexcludeend /> They can be inserted with Visual editor: for highlighted text: from Insert > Exclude content in PDF as empty content placeholder: from Content droplets > Exclude content in PDF

---

To submit feedback about this documentation, visit our community forum.