Page is a draft due to changes in included resources
You are viewing an old version of this page. Return to the latest version.
Version of 16:17, 9 March 2018 by Lsireta
Difference between revisions of "Manual:Extension/BlueSpiceSignHere"
| [unchecked revision] | [unchecked revision] |
(Created page with "__HIDETITLE__ <bs:bookshelf src="Book:User manual" /> __TOC__ ====<span id="Funktionsweise" class="mw-headline">Functionality</span>==== * <span class="mw-headline">There is...") |
Contents
- 1 Functionality
- 2 Visibility (eg views or namespaces)
- 3 Sorting
- 4 Scaling
- 5 Restrictions
- 6 See also
Functionality[edit | edit source]
- There is bs:signhere tag
- When this tag is added to a page, a field to add a signature appears
- When clicked, this field will generate a signature above itself
Visibility
(eg views or namespaces)[edit | edit source]
Will be shown in view mode of an Article. Everyone with edit right will be able to sign.
Sorting[edit | edit source]
Signatures appear in the order they were added.
Scaling[edit | edit source]
All signatures will always be shown.
Restrictions[edit | edit source]
Question of forgery was discussed. Reason is that signatures will be added as text, and therefore could be edited by other users. This is not obvious at first glance (while reading). However, every change will be visible in the log. So it can be known for sure, if the signatures have been changed after the fact.
See also[edit | edit source]
Our reference page.
__HIDETITLE__
<bs:bookshelf src="Book:User manual" />
__TOC__
====<span id="Funktionsweise" class="mw-headline">Functionality</span>======
* <span class="mw-headline">There is bs:signhere tag</span>
* <span class="mw-headline">When this tag is added to a page, a field to add a signature appears</span>
* <span class="mw-headline">When clicked, this field will generate a signature above itself</span>
====<span id="Sichtbarkeit_.28z.B._Ansichten_oder_Namespaces.29" class="mw-headline">Visibility (eg views or namespaces)</span>======
<span class="mw-headline">Will be shown in view mode of an Article. Everyone with edit right will be able to sign.</span>
====<span id="Sortierung" class="mw-headline">Sorting</span>======
<span class="mw-headline">Signatures appear in the order they were added.</span>
====<span id="Skalierung" class="mw-headline">Scaling</span>======
All signatures will always be shown.
===<span id="Restriktionen" class="mw-headline">Restrictions</span>=====
Question of forgery was discussed. Reason is that signatures will be added as text, and therefore could be edited by other users. This is not obvious at first glance (while reading). However, every change will be visible in the log. So it can be known for sure, if the signatures have been changed after the fact.
==See also==
Our [Https://en.help.bluespice.com/wiki/BlueSpiceSignHere| reference page.]| Line 4: | Line 4: | ||
__TOC__ | __TOC__ | ||
| − | == | + | ==Functionality== |
* <span class="mw-headline">There is bs:signhere tag</span> | * <span class="mw-headline">There is bs:signhere tag</span> | ||
* <span class="mw-headline">When this tag is added to a page, a field to add a signature appears</span> | * <span class="mw-headline">When this tag is added to a page, a field to add a signature appears</span> | ||
| Line 11: | Line 11: | ||
| − | == | + | ==Visibility== |
<span class="mw-headline">Will be shown in view mode of an Article. Everyone with edit right will be able to sign.</span> | <span class="mw-headline">Will be shown in view mode of an Article. Everyone with edit right will be able to sign.</span> | ||
| − | == | + | ==Sorting== |
<span class="mw-headline">Signatures appear in the order they were added.</span> | <span class="mw-headline">Signatures appear in the order they were added.</span> | ||
| − | == | + | ==Scaling== |
All signatures will always be shown. | All signatures will always be shown. | ||
| − | == | + | ==Restrictions== |
Question of forgery was discussed. Reason is that signatures will be added as text, and therefore could be edited by other users. This is not obvious at first glance (while reading). However, every change will be visible in the log. So it can be known for sure, if the signatures have been changed after the fact. | Question of forgery was discussed. Reason is that signatures will be added as text, and therefore could be edited by other users. This is not obvious at first glance (while reading). However, every change will be visible in the log. So it can be known for sure, if the signatures have been changed after the fact. | ||
==See also== | ==See also== | ||
| − | Our | + | Our [Https://en.help.bluespice.com/wiki/BlueSpiceSignHere| reference page.] |