Advanced plugin settings
You can configure settings on a space level at Space tools > Scroll Add-ons, and then pressing the ALT key to make a menu entry for Advanced Plugin Settings appear.
|Key||Description||Allowed Values||Default Value|
Indicates that some tweaks are enabled that may help, if Confluence/Viewport is running behind an Apache front-end server with mod_proxy, that messes up the forwarded URL (Google for the
From the Apache mod_proxy docs:
|enableViewportInfoForSpaceAdmins||Indicates that an info about Scroll Viewport should be displayed to space admins in spaces that have not yet a viewport configured.||true/false||true|
|Indicates that performance logging is allowed. Note that in the current implementation clients still need to set the corresponding HTTP request header to trigger logging for a specific request.||true/false||false|
The old approach for generating page slugs had a few deficiencies if the page titles contained characters like question marks. Our new solution ensures that the page titles will always consist of simple characters that don't need any percent encoding. This should improve the looks of your URLs.
Of course we are aware of the fact that you might want to keep the old approach now that your page has already been indexed by search engines. We've added a plugin setting that let's you revert to the classic behavior.
A global Runtime PluginSetting that allows administrators to control the amount of search results per page.
This property can be used to switch the HTTP response code for redirects when a user is redirected from the confluence UI to the Viewport. By default, Viewport sends a temporary redirect (HTTP 302), but this setting can be used to send permanent redirects (HTTP 301) instead.
Possible values are "302" and "301". The default value is "302". This is a global setting, it affects all Viewports in the Confluence instance.