Auf dieser Seite können die Einstellungen zur Protokollierung angepasst und vorhandene Protokolle angezeigt werden.
+
Protokoll Einstellungen
+
Bei aktivierter Debugging-Option werden System-Log Informationen an die Datei in der Protokolldatei im EIngabefeld hinzugefügt. Der Pfad ist relativ zum Hub-Wurzelverzeichnis. Daauf achten, dass diese Datei vom Webserver geschrieben werden kann.
+
Protokollstufe
+
Die Protokollstufe bestimmt, wie viele Informationen an die Protokolldatei angefügt werden. Warnung: Eine hohe Protokollstufe kann sehr schnell die Größe der Protokolldatei anwachsen lassen, vor allem, wenn der Hub viele Mitglieder hat.
+
diff --git a/doc/context/de/admin/queue/help.html b/doc/context/de/admin/queue/help.html
new file mode 100644
index 000000000..e59fdcaee
--- /dev/null
+++ b/doc/context/de/admin/queue/help.html
@@ -0,0 +1,4 @@
+
+
Allgemein
+
Die Warteschlangenstatistik zeigt, wie viele Nachrichten zur Auslieferung an andere Hubs noch in der Warteschlange stehen. Die Priorität steht in Beziehung mit der Anzahl fehlgeschlagener Auslieferungsversuche.
+
diff --git a/doc/context/de/admin/security/help.html b/doc/context/de/admin/security/help.html
new file mode 100644
index 000000000..6465e8f0e
--- /dev/null
+++ b/doc/context/de/admin/security/help.html
@@ -0,0 +1,4 @@
+
+
Allgemein
+
Auf dieser Seite können verschiedene Sicherheitseinstellungen vorgenommen werden. Um geänderte Einstellungen zu speichern, muss der Knopf "Bestätigen" gedrückt werden.
+
diff --git a/doc/context/de/channel/help.html b/doc/context/de/channel/help.html
new file mode 100644
index 000000000..fbfcac3c1
--- /dev/null
+++ b/doc/context/de/channel/help.html
@@ -0,0 +1,8 @@
+
+
Allgemein
+
Auf dieser Seite wird der eigene aktuelle Kanal angezeigt. Dies entspricht ungefähr den Profilseiten in anderen sozialen Netzwerken. Im Kanal veröffentliche Beiträge werden gemäß den Anzeige-Berechtigungen des Betrachters angezeigt.
+
Beitrag anlegen
+
Falls der Betrachter/Besucher die Berechtigung zum Anlegen von Beiträgen besitzt, wird im oberen Bereich der Beitragseditor angezeigt.
Die Tabs für unterschiedliche Kanal-Inhalte zeigen die unterschiedlichen veröffentlichten Inhalte des Kanals an. The Über Tab verweist auf das Profil des Kanals. Der Fotos Tab verweist auf die Foto-Gallerien des Kanals. Der Dateien Tab verweist auf allgemeine vom Kanal veröffentlichte und geteilte Dateien.
+
diff --git a/doc/context/de/chat/help.html b/doc/context/de/chat/help.html
new file mode 100644
index 000000000..ba355365f
--- /dev/null
+++ b/doc/context/de/chat/help.html
@@ -0,0 +1,8 @@
+
+
Allgemein
+
Chaträume können angelegt und für die Echtzeit-Kommunikation verwendet werden. Die Zugriffskontrolle verwendet dabei das Hubzilla-Berechtigungssystem.
+
Chatraum anlegen
+
Über den Knopf "Neu anlegen" wird ein neuer Chatraum eröffnet. Hierfür einen Namen und angeben, wie lange Nachrichten aufbewahrt werden sollen.
+
Chatten
+
Die Nachricht in der der Nachrichtenbox eingeben und "Bestätigen" drücken. Über den Menüknopf neben "Bestätigen" kann ein Anwesenheitsstatus gesetzt werden. Andere Teilnehmer am Chatraum werden im Seitenpanel unter "Chatmitglieder" angezeigt.
+
diff --git a/doc/context/de/cloud/help.html b/doc/context/de/cloud/help.html
new file mode 100644
index 000000000..e72ad1743
--- /dev/null
+++ b/doc/context/de/cloud/help.html
@@ -0,0 +1,6 @@
+
+
Allgemein
+
Diese Seite zeigt die veröffentlichten und geteilten Dateien des Kanals an. Welche Dateien ein Besucher sehen kann, wird über die individuellen Dateiberechtigungen bestimmt, die vom Kanal-Besitzer bestimmt werden. Wurde die Berechtigung zum Anlegen/Hochladen von Dateien vergeben, werden die entsprechenden Steuerungsknöpfe angezeigt.
Die Tabs für unterschiedliche Kanal-Inhalte zeigen die unterschiedlichen veröffentlichten Inhalte des Kanals an. The Über Tab verweist auf das Profil des Kanals. Der Fotos Tab verweist auf die Foto-Gallerien des Kanals. Der Dateien Tab verweist auf allgemeine vom Kanal veröffentlichte und geteilte Dateien.
+
diff --git a/doc/context/de/connections/help.html b/doc/context/de/connections/help.html
new file mode 100644
index 000000000..61789ea38
--- /dev/null
+++ b/doc/context/de/connections/help.html
@@ -0,0 +1,8 @@
+
Jeder Eintrag in der Liste zeigt die Details einer Verbindung. Ein durchsichtiges (ausgegrautes) Avatar-Bild zeigt archivierte Verbindungen an (diese konnten min. 30 Tage nicht erreicht werden).
+
Verbindungsstatus
+
Eine Verbindung kann sich in verschiedenen Stati befinden:
Archiviert
Ignoriert
Blockiert
Versteckt
+
diff --git a/doc/context/de/connections/ifpending/help.html b/doc/context/de/connections/ifpending/help.html
new file mode 100644
index 000000000..3e55b34c3
--- /dev/null
+++ b/doc/context/de/connections/ifpending/help.html
@@ -0,0 +1,8 @@
+
Jeder Eintrag in der Liste zeigt die Details einer Verbindung. Ein durchsichtiges (ausgegrautes) Avatar-Bild zeigt archivierte Verbindungen an (diese konnten min. 30 Tage nicht erreicht werden).
+
Verbindungsstatus
+
Eine Verbindung kann sich in verschiedenen Stati befinden:
Archiviert
Ignoriert
Blockiert
Versteckt
+
diff --git a/doc/context/de/events/help.html b/doc/context/de/events/help.html
new file mode 100644
index 000000000..b0dc95b3e
--- /dev/null
+++ b/doc/context/de/events/help.html
@@ -0,0 +1,8 @@
+
+
Allgemein
+
Auf dieser Seite wird ein Kalender mit eigenen und von anderen verbundenen Kanälen geteilte Ereignisse angezeigt.
Die Monats-, Wochen- und Tagesansicht des Kalenders kann im Panel ausgewählt werden.
+
Export/Import
+
Kalendereinträge können Eim Standard-Format iCalendar (.ics) exportiert oder importiert werden.
+
diff --git a/doc/context/de/mail/help.html b/doc/context/de/mail/help.html
new file mode 100644
index 000000000..b89135d8c
--- /dev/null
+++ b/doc/context/de/mail/help.html
@@ -0,0 +1,12 @@
+
+
Allgemein
+
Die Privaten Nachrichten sind nur für den Kanal-Besitzer und den Empfänger sichtbar.
+
Konversationen
+
Über Konversationen kann eine vollständige fortlaufene Ansicht einer Konversation angezeigt werden. Verfügbare Konversationen werden unter dem Punkt Konversationen im Panel angezeigt.
+
Eingang/Ausgang
+
Einzelne versandte Nachrichten kännen über den Punkt Ausgang und empfangene Nachrichten über Eingang gefiltert dargestellt werden.
+
Neue Nachricht
+
Über Neue Nachricht kann eine neue Nachricht erstellt werden.
+
Sonstiges
+
Über das Menü einzelner Nachrichten können besondere Funktionen ausgelöst werden: Zustellungsbericht kann abgerufen werden, Nachrichten (die noch nicht angesehen wurden!) können widerrufen und gelöscht werden.
+
diff --git a/doc/context/de/network/help.html b/doc/context/de/network/help.html
new file mode 100644
index 000000000..6590f597d
--- /dev/null
+++ b/doc/context/de/network/help.html
@@ -0,0 +1,10 @@
+
+
Allgemein
+
Auf der Netzwerkseite wird der Strom von Beiträgen und Konversationen angezeigt. Typischerweise wird nach kürzlich aktualisierten Beiträgen sortiert. Diese Seite kann sehr weitgehend angepasst werden.
Im oberen Bereich der Seite wird eine Textbox "Teilen" angezeigt. Nach Klick in diese Box wird der Beitragseditor angezeigt. Der Beitragseditor kann angepasst werden; in den Basiseinstellungen stehen Felder für Inhalt und einem optionalen Titel bereit. Knöpfe unterhalb des Inhaltes erleichtern die Eingabe von Formatierungen, Links, Bildern und anderen Daten im Beitrag. Über die Knöpfe im rechten Bereich kann eine Vorschau aktiviert, Berechtigungen gesetzt und der Beitrag abgesendet werden.
Die Zugriffskontrollliste (Access Control List; ACL) steuert, wer den Beitrag sehen darf. Nach Klick auf das Schloß neben dem Knopf "Teilen" öffnet sich ein Dialog, in dem Kanäle oder Gruppen ausgewählt werdenkönnen, die diesen Beitrag sehen dürfen. s kann auch gezielt verboten werden, dass ein Kanal oder eine Gruppe den Artikel sehen darf (nützlich beispielsweise für die Planung einer Überraschungsparty in einer Gruppe, in der der Überraschte Mitglied ist).
+
diff --git a/doc/context/de/photos/help.html b/doc/context/de/photos/help.html
new file mode 100644
index 000000000..437d2c369
--- /dev/null
+++ b/doc/context/de/photos/help.html
@@ -0,0 +1,6 @@
+
+
Allgemein
+
Diese Seite zeigt die veröffentlichten und geteilten Fotos des Kanals an. Welche Fotos ein Besucher sehen kann, wird über die individuellen Berechtigungen bestimmt, die vom Kanal-Besitzer bestimmt werden. Wurde die Berechtigung zum Anlegen/Hochladen von Bildern vergeben, werden die entsprechenden Steuerungsknöpfe angezeigt.
Die Tabs für unterschiedliche Kanal-Inhalte zeigen die unterschiedlichen veröffentlichten Inhalte des Kanals an. The Über Tab verweist auf das Profil des Kanals. Der Fotos Tab verweist auf die Foto-Gallerien des Kanals. Der Dateien Tab verweist auf allgemeine vom Kanal veröffentlichte und geteilte Dateien.
+
diff --git a/doc/context/de/profile/help.html b/doc/context/de/profile/help.html
new file mode 100644
index 000000000..ece33457d
--- /dev/null
+++ b/doc/context/de/profile/help.html
@@ -0,0 +1,6 @@
+
+
Allgemein
+
Dies ist die Profilseite eines Kanals. Hier werden typischerweise Informationen angezeigt, die den Kanal beschreiben. Wenn der Kanal beispielsweise eine Person in einem sozialen Netzwerk repräsentiert, könnten Kontaktinformationen und andere persönliche Details hier veröffentlicht werden. Kanäle können mehrere Profile besitzen, die abhängig vom Betrachter/Besucher angezeigt werden.
Die Tabs für unterschiedliche Kanal-Inhalte zeigen die unterschiedlichen veröffentlichten Inhalte des Kanals an. The Über Tab verweist auf das Profil des Kanals. Der Fotos Tab verweist auf die Foto-Gallerien des Kanals. Der Dateien Tab verweist auf allgemeine vom Kanal veröffentlichte und geteilte Dateien.
';
}
+function bb_definitionList($match) {
+ // $match[1] is the markup styles for the "terms" in the definition list.
+ // $match[2] is the content between the [dl]...[/dl] tags
+
+ $classes = '';
+ if (stripos($match[1], "b") !== false) $classes .= 'dl-terms-bold ';
+ if (stripos($match[1], "i") !== false) $classes .= 'dl-terms-italic ';
+ if (stripos($match[1], "u") !== false) $classes .= 'dl-terms-underline ';
+ if (stripos($match[1], "l") !== false) $classes .= 'dl-terms-large ';
+ if (stripos($match[1], "m") !== false) $classes .= 'dl-terms-monospace ';
+ if (stripos($match[1], "h") !== false) $classes .= 'dl-horizontal '; // dl-horizontal is already provided by bootstrap
+ if (strlen($classes) === 0) $classes = "dl-terms-plain";
+
+ // The bbcode transformation will be:
+ // [*=term-text] description-text =>
term-text
description-text
+ // then after all replacements have been made, the
remaining the start of the
+ // string can be removed. HTML5 allows the missing end tag.
+ // Using '(?\n";
+ $listElements = preg_replace(
+ '/\[\*=([[:print:]]*?)(?$1
',
+ $match[2]
+ );
+ // Unescape any \] inside the
tags
+ $listElements = preg_replace_callback('/
(.*?)<\/dt>/ism', 'bb_definitionList_unescapeBraces', $listElements);
+
+ // Remove the extra at the start of the string, if there is one.
+ $firstOpenTag = strpos($listElements, '
', $Text);
+
+ // [dl] tags have an optional [dl terms="bi"] form where bold/italic/underline/mono/large
+ // etc. style may be specified for the "terms" in the definition list. The quotation marks
+ // are also optional. The regex looks intimidating, but breaks down as:
+ // "[dl" "]" "[/dl]"
+ // where optional-termStyles are: "terms="
+ $Text = preg_replace_callback('/\[dl[[:space:]]*(?:terms=(?:"|")?([a-zA-Z]+)(?:"|")?)?\](.*?)\[\/dl\]/ism', 'bb_definitionList', $Text);
}
if (strpos($Text,'[th]') !== false) {
$Text = preg_replace("/\[th\](.*?)\[\/th\]/sm", '
$1
', $Text);
diff --git a/view/js/autocomplete.js b/view/js/autocomplete.js
index 21ce2d150..ca51230df 100644
--- a/view/js/autocomplete.js
+++ b/view/js/autocomplete.js
@@ -265,7 +265,7 @@ function string2bb(element) {
$.fn.bbco_autocomplete = function(type) {
if(type=='bbcode') {
- var open_close_elements = ['bold', 'italic', 'underline', 'overline', 'strike', 'superscript', 'subscript', 'quote', 'code', 'open', 'spoiler', 'map', 'nobb', 'list', 'ul', 'ol', 'li', 'table', 'tr', 'th', 'td', 'center', 'color', 'font', 'size', 'zrl', 'zmg', 'rpost', 'qr', 'observer'];
+ var open_close_elements = ['bold', 'italic', 'underline', 'overline', 'strike', 'superscript', 'subscript', 'quote', 'code', 'open', 'spoiler', 'map', 'nobb', 'list', 'ul', 'ol', 'dl', 'li', 'table', 'tr', 'th', 'td', 'center', 'color', 'font', 'size', 'zrl', 'zmg', 'rpost', 'qr', 'observer'];
var open_elements = ['observer.baseurl', 'observer.address', 'observer.photo', 'observer.name', 'observer.webname', 'observer.url', '*', 'hr', ];
var elements = open_close_elements.concat(open_elements);
diff --git a/view/theme/redbasic/css/style.css b/view/theme/redbasic/css/style.css
index 290a1a697..e1076a79f 100644
--- a/view/theme/redbasic/css/style.css
+++ b/view/theme/redbasic/css/style.css
@@ -1827,6 +1827,27 @@ nav .badge.mail-update:hover {
margin-top:-3px;
}
+dl.bb-dl > dt {
+ /* overriding the default dl style from bootstrap, as bootstrap's
+ style of a bold unindented line followed by a plain unindented
+ line is already acheivable in bbcode without dl */
+ font-weight: normal;
+}
+dl.dl-terms-monospace > dt { font-family: monospace; }
+dl.dl-terms-bold > dt { font-weight: bold; }
+dl.dl-terms-italic > dt { font-style: italic; }
+dl.dl-terms-underline > dt { text-decoration: underline; }
+dl.dl-terms-large > dt { font-size: 120%; }
+dl.bb-dl:not(.dl-horizontal) > dd {
+ display: block;
+ margin-left: 2em;
+}
+dl.bb-dl > dd > li {
+ /* adding some indent so bullet-list items will line up better with
+ dl descriptions if someone wants to be impure and combine them */
+ margin-left: 1em;
+}
+
.bootstrap-tagsinput .tag:before {
/* Copied from icon-asterisk, is there a better way to do it? */
font-family: FontAwesome;
--
cgit v1.2.3
From b5b21ecad7b164168fbc75792c7285700cee5c9f Mon Sep 17 00:00:00 2001
From: Treer
Date: Sat, 30 Apr 2016 02:03:38 +1000
Subject: improve whitespace control around definition list ([dl]) bbcode
---
include/bbcode.php | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/include/bbcode.php b/include/bbcode.php
index 1640307f8..5bd5301cc 100644
--- a/include/bbcode.php
+++ b/include/bbcode.php
@@ -360,14 +360,16 @@ function bb_definitionList($match) {
// The bbcode transformation will be:
// [*=term-text] description-text =>
term-text
description-text
- // then after all replacements have been made, the
remaining the start of the
- // string can be removed. HTML5 allows the missing end tag.
+ // then after all replacements have been made, the extra at the start of the
+ // first line can be removed. HTML5 allows the tag to be missing from the end of the last line.
// Using '(?\n";
+ $eatLeadingSpaces = '(?: |[ \t])*'; // prevent spaces infront of [*= from adding another line to the previous element
+ $listElements = preg_replace('/^(\n| )/', '', $match[2]); // ltrim the first newline
$listElements = preg_replace(
- '/\[\*=([[:print:]]*?)(?$1
',
- $match[2]
+ $listElements
);
// Unescape any \] inside the
tags
$listElements = preg_replace_callback('/
(.*?)<\/dt>/ism', 'bb_definitionList_unescapeBraces', $listElements);
--
cgit v1.2.3
From e7fbf1b017989459379e596511b602c982b5d4d3 Mon Sep 17 00:00:00 2001
From: Treer
Date: Sat, 30 Apr 2016 02:42:28 +1000
Subject: clean up some doc/ formatting
---
doc/hidden_configs.bb | 308 +++++++++++++++-----------------------------------
doc/permissions.bb | 108 +++++++-----------
2 files changed, 128 insertions(+), 288 deletions(-)
diff --git a/doc/hidden_configs.bb b/doc/hidden_configs.bb
index 5bb7454ec..6e093dbfc 100644
--- a/doc/hidden_configs.bb
+++ b/doc/hidden_configs.bb
@@ -1,10 +1,7 @@
-[b]Advanced Configurations for Administrators[/b]
-
+[h1]Advanced Configurations for Administrators[/h1]
$Projectname contains many configuration options hidden from the main admin panel.
-These are generally options considered too niche, confusing, or advanced for
-the average member. These settings can be activated from the the top level web
-directory with the syntax
+These are generally options considered too niche, confusing, or advanced for the average member. These settings can be activated from the the top level web directory with the syntax
[code]util/config cat key value[/code]
for a site configuration, or
@@ -13,221 +10,96 @@ for a site configuration, or
for a member configuration.
This document assumes you're an administrator.
+[h2]pconfig[/h2][dl terms="mb"]
+ [*= system.always_my_theme ] Always use your own theme when viewing channels on the same hub. This will break in some quite imaginative ways when viewing channels with theme dependent Comanche.
+ [*= system.blocked ] An array of xchans blocked by this channel. Technically, this is a hidden config and does belong here, however, addons (notably superblock) have made this available in the UI.
+ [*= system.default_cipher ] Set the default cipher used for E2EE items.
+ [*= system.display_friend_count ] Set the number of connections to display in the connections profile widget.
+ [*= system.do_not_track ] As the browser header. This will break many identity based features. You should really just set permissions that make sense.
+ [*= system.forcepublicuploads ] Force uploaded photos to be public when uploaded as wall items. It makes far more sense to just set your permissions properly in the first place. Do that instead.
+ [*= system.network_page_default ] Set default params when viewing the network page. This should contain the same querystring as manual filtering.
+ [*= system.paranoia ] Sets the security level of IP checking. If the IP address of a logged-in session changes apply this level to determine if the account should be logged out as a security breach.
+Options are:
+ 0 — no IP checking
+ 1 — check 3 octets
+ 2 — check 2 octets
+ 3 — check for any difference at all
-[b]pconfig[/b]
- [b]system.user_scalable[/b]
- Determine if the app is scalable on touch screens. Defaults to on, to
- disable, set to zero - real zero, not just false.
- [b]system.always_my_theme[/b]
- Always use your own theme when viewing channels on the same hub. This
- will break in some quite imaginative ways when viewing channels with
- theme dependent Comanche.
- [b]system.paranoia[/b]
- Sets the security level of IP checking. If the IP address of a logged-in session changes
- apply this level to determine if the account should be logged out as a security breach.
- Options are:
- 0 - no IP checking
- 1 - check 3 octets
- 2 - check 2 octets
- 3 - check for any difference at all
- [b]system.prevent_tag_hijacking[/b]
- Prevent foreign networks hijacking hashtags in your posts and directing them at its own resources.
- [b]system.blocked[/b]
- An array of xchans blocked by this channel. Technically, this is a
- hidden config and does belong here, however, addons (notably
- superblock) have made this available in the UI.
- [b]system.default_cipher[/b]
- Set the default cipher used for E2EE items.
- [b]system.network_page_default[/b]
- Set default params when viewing the network page. This should contain
- the same querystring as manual filtering.
- [b]system.display_friend_count[/b]
- Set the number of connections to display in the connections profile
- widget.
- [b]system.taganyone[/b]
- Requires the config of the same name to be enabled. Allow the @mention tagging
- of anyone, whether you are connected or not. This doesn't scale.
- [b]system.startpage[/b]
- Another of those technically hidden configs made available by addons.
- Sets the default page to view when logging in. This is exposed to the
- UI by the startpage addon.
- [b]system.forcepublicuploads[/b]
- Force uploaded photos to be public when uploaded as wall items. It
- makes far more sense to just set your permissions properly in the first
- place. Do that instead.
- [b]system.do_not_track[/b]
- As the browser header. This will break many identity based features.
- You should really just set permissions that make sense.
-
-[b]Site config[/b]
- [b]system.taganyone[/b]
- Allow the @mention tagging of anyone whether you are connected or not.
- [b]system.directorytags[/b]
- Set the number of keyword tags displayed on the directory page. Default is 50 unless set to a
- positive integer.
- [b]system.disable_directory_keywords[/b]
- If '1', do not show directory keywords. If the hub is a directory server, prevent returning
- tags to any directory clients. Please do not set this for directory servers in the RED_GLOBAL realm.
- [b]system.disable_dreport[/b]
- If '1', don't store or link to delivery reports
- [b]system.startpage[/b]
- Set the default page to be taken to after a login for all channels at
- this website. Can be overwritten by user settings.
- [b]system.projecthome[/b]
- Set the project homepage as the homepage of your hub. (Obsolete)
- [b]system.auto_channel_create[/b]
- Add the necessary form elements to create the first channel on the account registration page, and create it
- (possibly following email validation or administrator approval). This precludes the ability to import a channel
- from another site as the first channel created on this site for a new account.
- Use with system.default_permissions_role to streamline registration.
- [b]system.default_permissions_role[/b]
- If set to a valid permissions role name, use that role for
- the first channel created by a new account and don't ask for the "Channel Type" on
- the channel creation form. Examples of valid names are: 'social', 'social_restricted', 'social_private',
- 'forum', 'forum_restricted' and 'forum_private'.
- Read more about permissions roles [zrl=[baseurl]/help/roles]here[/zrl].
- [b]system.default_photo_profile[/b]
- Set the profile photo that new channels start with. This should contain the name of a directory located
- under [font=courier]images/default_profile_photos/[/font], or be left unset. If not set then 'rainbow_man' is assumed.
- [b]system.workflow_channel_next[/b]
- The page to direct new members to immediately after creating a channel.
- [b]system.workflow_register_next[/b]
- The page to direct members to immediately after creating an account (only when auto_channel_create or UNO is enabled).
- [b]system.max_daily_registrations[/b]
- Set the maximum number of new registrations allowed on any day.
- Useful to prevent oversubscription after a bout of publicity
- for the project.
- [b]system.tos_url[/b]
- Set an alternative link for the ToS location.
- [b]system.block_public_search[/b]
- Similar to block_public, except only blocks public access to
- search features. Useful for sites that want to be public, but
- keep getting hammered by search engines.
- [b]system.proc_run_use_exec[/b]
- If 1, use the exec system call in proc_run to run background tasks. By default
- we use proc_open and proc_close. On some (currently rare) systems this does not work well.
- [b]system.paranoia[/b]
- As the pconfig, but on a site-wide basis. Can be overwritten
- by member settings.
- [b]system.transport_security_header[/b]
- if non-zero and SSL is being used, include a strict-transport-security header on webpages
- [b]system.poke_basic[/b]
- Reduce the number of poke verbs to exactly 1 ("poke"). Disable other verbs.
- [b]system.openssl_conf_file[/b]
- Specify a file containing OpenSSL configuration. Needed in some Windows installations to
- locate the openssl configuration file on the system.
- Read the code first. If you can't read the code, don't play with it.
- [b]system.optimize_items[/b]
- Runs optimise_table during some tasks to keep your database nice and
- defragmented. This comes at a performance cost while the operations
- are running, but also keeps things a bit faster while it's not.
- There also exist CLI utilities for performing this operation, which you
- may prefer, especially if you're a large site.
- [b]system.expire_limit[/b]
- Don't expire any more than this number of posts per channel per
- expiration run to keep from exhausting memory. Default 5000.
- [b]system.dlogfile[/b]
- Logfile to use for logging development errors. Exactly the same as
- logger otherwise. This isn't magic, and requires your own logging
- statements. Developer tool.
- [b]system.authlog[/b]
- Logfile to use for logging auth errors. Used to plug in to server
- side software such as fail2ban. Auth failures are still logged to
- the main logs as well.
- [b]system.hide_in_statistics[/b]
- Tell the red statistics servers to completely hide this hub in hub lists.
- [b]system.reserved_channels[/b]
- Don't allow members to register channels with this comma separated
- list of names (no spaces)
- [b]system.auto_follow[/b]
- Make the first channel of an account auto-follow channels listed here - comma separated list of webbies (member@hub addresses).
- [b]system.admin_email[/b]
- Specifies the administrator's email for this site. This is initially set during install.
- [b]system.cron_hour[/b]
- Specify an hour in which to run cron_daily. By default with no config, this will run at midnight UTC.
- [b]system.minimum_feedcheck_minutes[/b]
- The minimum interval between polling RSS feeds. If this is lower than the cron interval, feeds
- will be polled with each cronjob. Defaults to 60 if not set. The site setting can also be over-ridden
- on a channel by channel basis by a service class setting aptly named 'minimum_feedcheck_minutes'.
- [b]system.blacklisted_sites[/b]
- An array of specific hubs to block from this hub completely.
- [b]system.ignore_imagick[/b]
- Ignore imagick and use GD, even if imagick is installed on the server. Prevents some issues with PNG files in older versions of imagick.
- [b]system.no_age_restriction[/b]
- Do not restrict registration to people over the age of 13. This carries legal responsibilities in
- many countries to require that age be provided and to block all personal information from minors,
- so please check your local laws before changing.
- [b]system.override_poll_lockfile[/b]
- Ignore the lock file in the poller process to allow more than one process to run at a time.
- [b]system.projecthome[/b]
- Display the project page on your home page for logged out viewers.
- [b]system.sellpage[/b]
- A URL shown in the public sites list to sell your hub - display service classes, etc.
- [b]randprofile.check[/b]
- When requesting a random profile, check that it actually exists first
- [b]randprofile.retry[/b]
- Number of times to retry getting a random profile
- [b]system.photo_cache_time[/b]
- How long to cache photos, in seconds. Default is 86400 (1 day).
- Longer time increases performance, but it also means it takes longer for changed permissions to apply.
- [b]system.poco_rating_enable[/b]
- Distributed reputation reporting and data collection may be disabled. If your site does not participate
- in distributed reputation you will also not be able to make use of the data from your connections on
- other sites. By default and in the absence of any setting it is enabled. Individual members can opt out
- by restricting who can see their connections or by not providing any reputation information for their
- connections.
- [b]system.register_link[/b]
- path to direct to from the "register" link on the login form. On closed sites this will direct to
- 'pubsites'. For open sites it will normally redirect to 'register' but you may change this to a
- custom site page offering subscriptions or whatever.
- [b]system.max_import_size[/b]
- If configured, the maximum length of an imported text message. This is normally left at 200Kbytes
- or more to accomodate Friendica private photos, which are embedded.
- [b]system.tempdir[/b]
- Place to store temporary files (currently unused), default is defined in the PHP configuration
- [b]system.uploaddir[/b]
- Location to upload files (default is system.tempdir, currently used only by js_upload plugin)
- [b]system.disable_discover_tab[/b]
- This allows you to completely disable the ability to discover public content from external sites.
- [b]system.sys_expire_days[/b]
- How many days to keep discovered public content from other sites
- [b]system.openssl_encrypt[/b]
- Use openssl encryption engine, default is false (uses mcrypt for AES encryption)
- [b]system.max_tagged_forums[/b]
- Spam prevention. Limits the number of tagged forums which are recognised in any post.
- Default is 2. Only the first 'n' tags will be delivered as forums, the others will not cause any delivery.
- [b]system.hide_help[/b]
- Don't display help documentation link in nav bar
- [b]system.expire_delivery_reports[/b]
- Expiration in days for delivery reports - default 10
- [b]system.platform_name[/b] *
- What to report as the platform name in webpages and statistics. (*) Must be set in .htconfig.php
- [b]system.hide_version[/b] *
- If true, do not report the software version on webpages and tools. (*) Must be set in .htconfig.php
- [b]system.hidden_version_siteinfo[/b]
- If true, do not report the software version on siteinfo pages (system.hide_version also hides
- the version on these pages, this setting *only* hides the version on siteinfo pages).
- [b]system.email_notify_icon_url[/b]
- URL of image (32x32) to display in email notifications (HTML bodies).
-
-[b]Directory config[/b]
-[b]Directory search defaults[/b]
- [b]directory.safemode[/b]
- 0 or 1.
- [b]directory.globaldir[/b]
- 0 or 1. Default 0. If you visit the directory on a site you'll just see the members of that site by default. You have to go through an extra step to see the people in the rest of the network; and by doing so there's a clear delineation that these people *aren't* members of that site but of a larger network.
- [b]directory.pubforums[/b]
- 0 or 1. Public forums *should* be default 0.
-[b]Directory server configuration (see [zrl=[baseurl]/help/directories]help/directories[/zrl])[/b]
- [b]system.directory_server[/b]
- [b]system.directory_primary[/b]
- [b]system.directory_realm[/b]
- [b]system.realm_token[/b]
- [b]system.directory_mode[/b]
-
-
+ [*= system.prevent_tag_hijacking ] Prevent foreign networks hijacking hashtags in your posts and directing them at its own resources.
+ [*= system.startpage ] Another of those technically hidden configs made available by addons. Sets the default page to view when logging in. This is exposed to the UI by the startpage addon.
+ [*= system.taganyone ] Requires the config of the same name to be enabled. Allow the @mention tagging of anyone, whether you are connected or not. This doesn't scale.
+ [*= system.user_scalable ] Determine if the app is scalable on touch screens. Defaults to on, to disable, set to zero - real zero, not just false.
+[/dl]
+[h2]Site config[/h2][dl terms="mb"]
+ [*= randprofile.check ] When requesting a random profile, check that it actually exists first
+ [*= randprofile.retry ] Number of times to retry getting a random profile
+ [*= system.admin_email ] Specifies the administrator's email for this site. This is initially set during install.
+ [*= system.authlog ] Logfile to use for logging auth errors. Used to plug in to server side software such as fail2ban. Auth failures are still logged to the main logs as well.
+ [*= system.auto_channel_create ] Add the necessary form elements to create the first channel on the account registration page, and create it (possibly following email validation or administrator approval). This precludes the ability to import a channel from another site as the first channel created on this site for a new account. Use with system.default_permissions_role to streamline registration.
+ [*= system.auto_follow ] Make the first channel of an account auto-follow channels listed here - comma separated list of webbies (member@hub addresses).
+ [*= system.blacklisted_sites ] An array of specific hubs to block from this hub completely.
+ [*= system.block_public_search ] Similar to block_public, except only blocks public access to search features. Useful for sites that want to be public, but keep getting hammered by search engines.
+ [*= system.cron_hour ] Specify an hour in which to run cron_daily. By default with no config, this will run at midnight UTC.
+ [*= system.default_permissions_role ] If set to a valid permissions role name, use that role for the first channel created by a new account and don't ask for the "Channel Type" on the channel creation form. Examples of valid names are: 'social', 'social_restricted', 'social_private', 'forum', 'forum_restricted' and 'forum_private'. Read more about permissions roles [zrl=[baseurl]/help/roles]here[/zrl].
+ [*= system.default_photo_profile ] Set the profile photo that new channels start with. This should contain the name of a directory located under [font=courier]images/default_profile_photos/[/font], or be left unset. If not set then 'rainbow_man' is assumed.
+ [*= system.directorytags ] Set the number of keyword tags displayed on the directory page. Default is 50 unless set to a positive integer.
+ [*= system.disable_directory_keywords ] If '1', do not show directory keywords. If the hub is a directory server, prevent returning tags to any directory clients. Please do not set this for directory servers in the RED_GLOBAL realm.
+ [*= system.disable_discover_tab ] This allows you to completely disable the ability to discover public content from external sites.
+ [*= system.disable_dreport ] If '1', don't store or link to delivery reports
+ [*= system.dlogfile ] Logfile to use for logging development errors. Exactly the same as logger otherwise. This isn't magic, and requires your own logging statements. Developer tool.
+ [*= system.email_notify_icon_url ] URL of image (32x32) to display in email notifications (HTML bodies).
+ [*= system.expire_delivery_reports ] Expiration in days for delivery reports - default 10
+ [*= system.expire_limit ] Don't expire any more than this number of posts per channel per expiration run to keep from exhausting memory. Default 5000.
+ [*= system.hidden_version_siteinfo ] If true, do not report the software version on siteinfo pages (system.hide_version also hides the version on these pages, this setting *only* hides the version on siteinfo pages).
+ [*= system.hide_help ] Don't display help documentation link in nav bar
+ [*= system.hide_in_statistics ] Tell the red statistics servers to completely hide this hub in hub lists.
+ [*= system.hide_version ] If true, do not report the software version on webpages and tools. (*) Must be set in .htconfig.php
+ [*= system.ignore_imagick ] Ignore imagick and use GD, even if imagick is installed on the server. Prevents some issues with PNG files in older versions of imagick.
+ [*= system.max_daily_registrations ] Set the maximum number of new registrations allowed on any day. Useful to prevent oversubscription after a bout of publicity for the project.
+ [*= system.max_import_size ] If configured, the maximum length of an imported text message. This is normally left at 200Kbytes or more to accomodate Friendica private photos, which are embedded.
+ [*= system.max_tagged_forums ] Spam prevention. Limits the number of tagged forums which are recognised in any post. Default is 2. Only the first 'n' tags will be delivered as forums, the others will not cause any delivery.
+ [*= system.minimum_feedcheck_minutes ] The minimum interval between polling RSS feeds. If this is lower than the cron interval, feeds will be polled with each cronjob. Defaults to 60 if not set. The site setting can also be over-ridden on a channel by channel basis by a service class setting aptly named 'minimum_feedcheck_minutes'.
+ [*= system.no_age_restriction ] Do not restrict registration to people over the age of 13. This carries legal responsibilities in many countries to require that age be provided and to block all personal information from minors, so please check your local laws before changing.
+ [*= system.openssl_conf_file ] Specify a file containing OpenSSL configuration. Needed in some Windows installations to locate the openssl configuration file on the system. Read the code first. If you can't read the code, don't play with it.
+ [*= system.openssl_encrypt ] Use openssl encryption engine, default is false (uses mcrypt for AES encryption)
+ [*= system.optimize_items ] Runs optimise_table during some tasks to keep your database nice and defragmented. This comes at a performance cost while the operations are running, but also keeps things a bit faster while it's not. There also exist CLI utilities for performing this operation, which you may prefer, especially if you're a large site.
+ [*= system.override_poll_lockfile ] Ignore the lock file in the poller process to allow more than one process to run at a time.
+ [*= system.paranoia ] As the pconfig, but on a site-wide basis. Can be overwritten by member settings.
+ [*= system.photo_cache_time ] How long to cache photos, in seconds. Default is 86400 (1 day). Longer time increases performance, but it also means it takes longer for changed permissions to apply.
+ [*= system.platform_name ] What to report as the platform name in webpages and statistics. (*) Must be set in .htconfig.php
+ [*= system.poco_rating_enable ] Distributed reputation reporting and data collection may be disabled. If your site does not participate in distributed reputation you will also not be able to make use of the data from your connections on other sites. By default and in the absence of any setting it is enabled. Individual members can opt out by restricting who can see their connections or by not providing any reputation information for their connections.
+ [*= system.poke_basic ] Reduce the number of poke verbs to exactly 1 ("poke"). Disable other verbs.
+ [*= system.proc_run_use_exec ] If 1, use the exec system call in proc_run to run background tasks. By default we use proc_open and proc_close. On some (currently rare) systems this does not work well.
+ [*= system.projecthome ] Display the project page on your home page for logged out viewers.
+ [*= system.projecthome ] Set the project homepage as the homepage of your hub. (Obsolete)
+ [*= system.register_link ] path to direct to from the "register" link on the login form. On closed sites this will direct to 'pubsites'. For open sites it will normally redirect to 'register' but you may change this to a custom site page offering subscriptions or whatever.
+ [*= system.reserved_channels ] Don't allow members to register channels with this comma separated list of names (no spaces)
+ [*= system.sellpage ] A URL shown in the public sites list to sell your hub - display service classes, etc.
+ [*= system.startpage ] Set the default page to be taken to after a login for all channels at this website. Can be overwritten by user settings.
+ [*= system.sys_expire_days ] How many days to keep discovered public content from other sites
+ [*= system.taganyone ] Allow the @mention tagging of anyone whether you are connected or not.
+ [*= system.tempdir ] Place to store temporary files (currently unused), default is defined in the PHP configuration
+ [*= system.tos_url ] Set an alternative link for the ToS location.
+ [*= system.transport_security_header ] if non-zero and SSL is being used, include a strict-transport-security header on webpages
+ [*= system.uploaddir ] Location to upload files (default is system.tempdir, currently used only by js_upload plugin)
+ [*= system.workflow_channel_next ] The page to direct new members to immediately after creating a channel.
+ [*= system.workflow_register_next ] The page to direct members to immediately after creating an account (only when auto_channel_create or UNO is enabled).
+[/dl]
+[h2]Directory config[/h2]
+[h3]Directory search defaults[/h3][dl terms="mb"]
+ [*= directory.globaldir ] 0 or 1. Default 0. If you visit the directory on a site you'll just see the members of that site by default. You have to go through an extra step to see the people in the rest of the network; and by doing so there's a clear delineation that these people *aren't* members of that site but of a larger network.
+ [*= directory.pubforums ] 0 or 1. Public forums [i]should[/i] be default 0.
+ [*= directory.safemode ] 0 or 1.
+[/dl]
+[h3]Directory server configuration[/h3][i](see [zrl=[baseurl]/help/directories]help/directories[/zrl])[/i]
+[dl terms="mb"]
+ [*= system.directory_mode ]
+ [*= system.directory_primary ]
+ [*= system.directory_realm ]
+ [*= system.directory_server ]
+ [*= system.realm_token ]
+[/dl]
-
#include doc/macros/main_footer.bb;
diff --git a/doc/permissions.bb b/doc/permissions.bb
index bcf3c43e0..ceb3fec17 100644
--- a/doc/permissions.bb
+++ b/doc/permissions.bb
@@ -1,7 +1,7 @@
-[b]Permissions[/b]
-
+[h1]Permissions[/h1]
Permissions in the $Projectname are more complete than you may be used to. This allows us to define more fine graded relationships than the black and white "this person is my friend, so they can do everything" or "this person is not my friend, so they can't do anything" permissions you may find elsewhere.
+
[b]Default Permissions[/b]
On your settings page, you will find a list of default permissions. These permissions are automatically applied to everybody unless you specify otherwise. The scope of these permissions varies from "Only me" to "Everybody" - though some scopes may not be available for some permissions. For example, you can't allow "anybody on the internet" to send you private messages, because we'd have no way to identify the sender, therefore no way to reply to them.
@@ -13,89 +13,57 @@ Be aware that altering the scope of who can see your "public" items is a more or
A more useful privacy setup is to leave "public" items visible to anybody on the internet; but force everything you create to be restricted. This can be done on your Channel Settings page by selecting the role "Social - restricted". This ensures a Default Privacy Group for all new contacts, and sets your Default Post Permissions to restrict all your posts to that group. We use the Default Post Permissions for everything you create - posts, photos, events, webpages, and everything else. However you can then edit the permissions when you create any individual thing and remove your default privacy group to make just that item visible to anybody.
+[dl terms="l"]
+[*= The scopes of permissions are:]
+[dl terms="i"]
+ [*= Nobody Except Yourself ] This is self explanatory. Only you will be allowed access.
+
+ [*= Only those you specifically allow ] By default, people you are not connected to, and all new contacts will have this permission denied. You will be able to make exceptions for individual channels on their contact edit screen.
+
+ [*= Anybody in your address book ] Anybody you do not know will have this permission denied, but anybody you accept as a contact will have this permission approved. This is the way most legacy platforms handle permissions.
+
+ [*= Anybody On This Hub ] Anybody using the same hub as you will have permission approved. Anybody who registered at a different hub will have this permission denied.
+
+ [*= Anybody in this network ] Anybody in the $Projectname will have this permission approved. Even complete strangers. However, anybody not logged in/authenticated will have this permission denied.
+
+ [*= Anybody authenticated ] This is similar to "anybody in this network" except that it can include anybody who can authenticate by any means - and therefore may include visitors from other networks.
+
+ [*= Anybody on the internet ] Completely public. This permission will be approved for anybody at all.
+[/dl]
+[*= The individual permissions are:]
+[dl terms="i"]
+ [*= Can view my "public" stream and posts. ] This permision determines who can view your channel "stream" that is, the non-private posts that appear on the "home" tab when you're logged in.
-The scopes of permissions are:
-
-[li]Nobody Except Yourself. This is self explanatory. Only you will be allowed access.[/li]
-
-[li]Only those you specifically allow. By default, people you are not connected to, and all new contacts will have this permission denied. You will be able to make exceptions for individual channels on their contact edit screen.[/li]
-
-[li]Anybody in your address book. Anybody you do not know will have this permission denied, but anybody you accept as a contact will have this permission approved. This is the way most legacy platforms handle permissions.[/li]
-
-[li]Anybody On This Hub. Anybody using the same hub as you will have permission approved. Anybody who registered at a different hub will have this permission denied.[/li]
-
-[li]Anybody in this network. Anybody in the $Projectname will have this permission approved. Even complete strangers. However, anybody not logged in/authenticated will have this permission denied.[/li]
-
-[li]Anybody authenticated. This is similar to "anybody in this network" except that it can include anybody who can authenticate by any means - and therefore may include visitors from other networks.[/li]
-
-[li]Anybody on the internet. Completely public. This permission will be approved for anybody at all.[/li]
-
-The individual permissions are:
-
-[i]Can view my "public" stream and posts.[/i]
-
-This permision determines who can view your channel "stream" that is, the non-private posts that appear on the "home" tab when you're logged in.
-
-[i]Can view my "public" channel profile.[/i]
-
-This permission determines who can view your channel's profile. This refers to the "about" tab
-
-[i]Can view my "public" photo albums.[/i]
-
- This permission determines who can view your photo albums. Individual photographs may still be posted to a more private audience.
-
-[i]Can view my "public" address book.[/i]
-
-This permission determines who can view your contacts. These are the connections displayed in the "View connections" section.
-
-[i]Can view my "public" file storage.[/i]
-
-This permission determines who can view your public files stored in your cloud.
-
-[i]Can view my "public" pages.[/i]
-
-This permission determines who can view your public web pages.
-
-[i]Can send me their channel stream and posts.[/i]
-
-This permission determines whose posts you will view. If your channel is a personal channel (ie, you as a person), you would probably want to set this to "anyone in my address book" at a minimum. A personal notes channel would probably want to choose "nobody except myself". Setting this to "Anybody in the network" will show you posts from complete strangers, which is a good form of discovery.
-
-[i]Can post on my channel page ("wall").[/i]
-
-This permission determines who can write to your wall when clicking through to your channel.
-
-[i]Can comment on my posts.[/i]
-
-This permission determines who can comment on posts you create. Normally, you would want this to match your "can view my public stream and posts" permission
-
-[i]Can send me private mail messages.[/i]
+ [*= Can view my "public" channel profile. ] This permission determines who can view your channel's profile. This refers to the "about" tab
-This determines who can send you private messages (zotmail).
+ [*= Can view my "public" photo albums. ] This permission determines who can view your photo albums. Individual photographs may still be posted to a more private audience.
-[i]Can post photos to my photo albums.[/i]
+ [*= Can view my "public" address book. ] This permission determines who can view your contacts. These are the connections displayed in the "View connections" section.
-This determines who can post photographs in your albums. This is very useful for forum-like channels where connections may not be connected to each other.
+ [*= Can view my "public" file storage. ] This permission determines who can view your public files stored in your cloud.
-[i]Can forward to all my channel contacts via post tags.[/i]
+ [*= Can view my "public" pages. ] This permission determines who can view your public web pages.
-Using @- mentions will reproduce a copy of your post on the profile specified, as though you posted on the channel wall. This determines if people can post to your channel in this way.
+ [*= Can send me their channel stream and posts. ] This permission determines whose posts you will view. If your channel is a personal channel (ie, you as a person), you would probably want to set this to "anyone in my address book" at a minimum. A personal notes channel would probably want to choose "nobody except myself". Setting this to "Anybody in the network" will show you posts from complete strangers, which is a good form of discovery.
-[i]Can chat with me (when available).[/i]
+ [*= Can post on my channel page ("wall"). ] This permission determines who can write to your wall when clicking through to your channel.
-This determines who can join the public chat rooms created by your channel.
+ [*= Can comment on my posts. ] This permission determines who can comment on posts you create. Normally, you would want this to match your "can view my public stream and posts" permission
-[i]Can write to my "public" file storage.[/i]
+ [*= Can send me private mail messages. ] This determines who can send you private messages (zotmail).
-This determines who can upload files to your public file storage, or 'cloud'.
+ [*= Can post photos to my photo albums. ] This determines who can post photographs in your albums. This is very useful for forum-like channels where connections may not be connected to each other.
-[i]Can edit my "public" pages.[/i]
+ [*= Can forward to all my channel contacts via post tags. ] Using @- mentions will reproduce a copy of your post on the profile specified, as though you posted on the channel wall. This determines if people can post to your channel in this way.
-This determines who can edit your webpages. This is useful for wikis or sites with multiple editors.
+ [*= Can chat with me (when available). ] This determines who can join the public chat rooms created by your channel.
-[i]Can administer my channel resources.[/i]
+ [*= Can write to my "public" file storage. ] This determines who can upload files to your public file storage, or 'cloud'.
-This determines who can have full control of your channel. This should normally be set to "nobody except myself".
+ [*= Can edit my "public" pages. ] This determines who can edit your webpages. This is useful for wikis or sites with multiple editors.
+ [*= Can administer my channel resources. ] This determines who can have full control of your channel. This should normally be set to "nobody except myself".
+[/dl][/dl]
[i]Note:[/i]
Plugins/addons may provide special permission settings, so you may be offered additional permission settings beyond what is described here.
--
cgit v1.2.3
From 83a0e82d5cba8d3e241c51e3c2e9fd2466183b72 Mon Sep 17 00:00:00 2001
From: Mario Vavti
Date: Fri, 29 Apr 2016 20:01:54 +0200
Subject: css fix
---
view/css/bootstrap-red.css | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/view/css/bootstrap-red.css b/view/css/bootstrap-red.css
index aa8b40365..73d77bb93 100644
--- a/view/css/bootstrap-red.css
+++ b/view/css/bootstrap-red.css
@@ -21,7 +21,8 @@ nav .badge {
}
}
-#navbar-collapse-1 i {
+#navbar-collapse-1 i,
+.navbar-header i {
font-size: 14px;
}
--
cgit v1.2.3
From 931a4fafe316b23bacf92ac1ff35f9b8467415dd Mon Sep 17 00:00:00 2001
From: Mario Vavti
Date: Fri, 29 Apr 2016 21:38:36 +0200
Subject: get rid of the unused ispublic variable
---
Zotlabs/Module/Cal.php | 2 +-
Zotlabs/Module/Editpost.php | 1 -
Zotlabs/Module/Photos.php | 2 +-
include/conversation.php | 1 -
view/js/acl.js | 5 +----
view/js/mod_photos.js | 4 ----
view/js/mod_settings.js | 3 ---
view/tpl/jot-header.tpl | 11 -----------
view/tpl/jot.tpl | 2 +-
9 files changed, 4 insertions(+), 27 deletions(-)
diff --git a/Zotlabs/Module/Cal.php b/Zotlabs/Module/Cal.php
index 89967bca1..958ce5aa6 100644
--- a/Zotlabs/Module/Cal.php
+++ b/Zotlabs/Module/Cal.php
@@ -38,7 +38,7 @@ class Cal extends \Zotlabs\Web\Controller {
head_set_icon(\App::$data['channel']['xchan_photo_s']);
- \App::$page['htmlhead'] .= "" ;
+ \App::$page['htmlhead'] .= "" ;
}
diff --git a/Zotlabs/Module/Editpost.php b/Zotlabs/Module/Editpost.php
index fd9912fe9..1c2c2a30b 100644
--- a/Zotlabs/Module/Editpost.php
+++ b/Zotlabs/Module/Editpost.php
@@ -83,7 +83,6 @@ class Editpost extends \Zotlabs\Web\Controller {
}
$x = array(
- 'ispublic' => ' ',
'nickname' => $channel['channel_address'],
'editor_autocomplete'=> true,
'bbco_autocomplete'=> 'bbcode',
diff --git a/Zotlabs/Module/Photos.php b/Zotlabs/Module/Photos.php
index 15a1f4d9c..2b7f5525f 100644
--- a/Zotlabs/Module/Photos.php
+++ b/Zotlabs/Module/Photos.php
@@ -42,7 +42,7 @@ class Photos extends \Zotlabs\Web\Controller {
head_set_icon(\App::$data['channel']['xchan_photo_s']);
- \App::$page['htmlhead'] .= "" ;
+ \App::$page['htmlhead'] .= "" ;
}
diff --git a/include/conversation.php b/include/conversation.php
index 14fee19b2..b1b47df39 100644
--- a/include/conversation.php
+++ b/include/conversation.php
@@ -1175,7 +1175,6 @@ function status_editor($a, $x, $popup = false) {
'$pretext' => ((x($x,'pretext')) ? $x['pretext'] : ''),
'$geotag' => $geotag,
'$nickname' => $x['nickname'],
- '$ispublic' => ((x($x,'ispublic')) ? $x['ispublic'] : t('Visible to everybody')),
'$linkurl' => t('Please enter a link URL:'),
'$term' => t('Tag term:'),
'$whereareu' => t('Where are you right now?'),
diff --git a/view/js/acl.js b/view/js/acl.js
index 65f1009ed..7940a9bdc 100644
--- a/view/js/acl.js
+++ b/view/js/acl.js
@@ -196,16 +196,13 @@ ACL.prototype.update_view = function() {
$('#jot-perms-icon').removeClass('icon-lock').addClass('icon-unlock');
$('#jot-public').show();
$('.profile-jot-net input').attr('disabled', false);
- if(typeof editor !== 'undefined' && editor !== false) {
- $('#profile-jot-desc').html(ispublic);
- }
} else {
that.showall.removeClass("btn-warning").addClass("btn-default");
/* jot acl */
$('#jot-perms-icon').removeClass('icon-unlock').addClass('icon-lock');
$('#jot-public').hide();
$('.profile-jot-net input').attr('disabled', 'disabled');
- $('#profile-jot-desc').html(' ');
+
}
$("#acl-list-content .acl-list-item").each(function() {
$(this).removeClass("groupshow grouphide");
diff --git a/view/js/mod_photos.js b/view/js/mod_photos.js
index 34e2e3f25..8af75b4eb 100644
--- a/view/js/mod_photos.js
+++ b/view/js/mod_photos.js
@@ -1,10 +1,6 @@
/**
* JavaScript used by mod/photos
*/
-
-// is this variable used anywhere?
-var ispublic = aStr.everybody;
-
$(document).ready(function() {
$("#photo-edit-newtag").contact_autocomplete(baseurl + '/acl', 'p', false, function(data) {
diff --git a/view/js/mod_settings.js b/view/js/mod_settings.js
index 3fd57995a..9a7550ac1 100644
--- a/view/js/mod_settings.js
+++ b/view/js/mod_settings.js
@@ -2,9 +2,6 @@
* JavaScript used by mod/settings
*/
-// is this used anywhere?
-var ispublic = aStr.everybody;
-
$(document).ready(function() {
$('form').areYouSure({'addRemoveFieldsMarksDirty':true, 'message': aStr['leavethispage'] }); // Warn user about unsaved settings
diff --git a/view/tpl/jot-header.tpl b/view/tpl/jot-header.tpl
index 085710f55..bdcca71ac 100755
--- a/view/tpl/jot-header.tpl
+++ b/view/tpl/jot-header.tpl
@@ -1,7 +1,6 @@
diff --git a/library/font_awesome/src/_includes/ads/fusion.html b/library/font_awesome/src/_includes/ads/fusion.html
new file mode 100644
index 000000000..c49a9f42c
--- /dev/null
+++ b/library/font_awesome/src/_includes/ads/fusion.html
@@ -0,0 +1 @@
+
diff --git a/library/font_awesome/src/_includes/brand-adblock-warning.html b/library/font_awesome/src/_includes/brand-adblock-warning.html
new file mode 100644
index 000000000..9f4ddd8b6
--- /dev/null
+++ b/library/font_awesome/src/_includes/brand-adblock-warning.html
@@ -0,0 +1,5 @@
+
Warning!
+Apparently, Adblock Plus can remove Font Awesome brand icons with their "Remove Social
+Media Buttons" setting. We will not use hacks to force them to display. Please
+report an issue with Adblock Plus if you believe this to be
+an error. To work around this, you'll need to modify the social icon class names.
diff --git a/library/font_awesome/src/_includes/brand-license.html b/library/font_awesome/src/_includes/brand-license.html
index 07dea295a..79696801e 100644
--- a/library/font_awesome/src/_includes/brand-license.html
+++ b/library/font_awesome/src/_includes/brand-license.html
@@ -1,4 +1,5 @@
-
+
All brand icons are trademarks of their respective owners.
The use of these trademarks does not indicate endorsement of the trademark holder by Font Awesome, nor vice versa.
+
Brand icons should only be used to represent the company or product to which they refer.
- Print this page to PDF for the complete set of vectors. Or to use on the desktop, install FontAwesome.otf and copy
- and paste the icons (not the unicode) directly into your designs.
-
-{% endcapture %}
-{% include stripe-ad.html %}
-
-
Every Font Awesome {{ site.fontawesome.version }} Icon, CSS Class, & Unicode
Please search to see if your icon request already exists.
+
Please search to see if your bug was already reported.
Before opening any issue, please read the generic issue
guidelines, by Nicolas Gallagher.
diff --git a/library/font_awesome/src/_includes/community/requesting-new-icons.html b/library/font_awesome/src/_includes/community/requesting-new-icons.html
index d710e2bb1..e73f41c35 100644
--- a/library/font_awesome/src/_includes/community/requesting-new-icons.html
+++ b/library/font_awesome/src/_includes/community/requesting-new-icons.html
@@ -7,21 +7,23 @@
Please be nice. Font Awesome is a happy place.
-
Please search to see if your icon request already exists.
+
Please search to see if your icon request already exists. If a request is found, please +1 that one.
+
+ Please make requests for single icons, unless you are requesting a couple of strictly related icons (e.g., thumbs-up/thumbs-down).
+
Please and thank you if you include the following:
- Title your new issue
- Icon request: icon-name.
+ Title your new issue
+ Icon request: icon-name (e.g., Icon request: icon-car).
Include a few use cases for your requested icon. How do you plan on using it?
Attach a single color image or two that represent the idea you're going for.
- Concrete objects make good icons, since abstract concepts are, well, abstract. It's harder to make an icon
- to represent happiness. It's easier to make a smiley face.
+ Request concrete objects: it's harder to make an icon to represent happiness, it's easier to make a smiley face.
Found a way to solve a bug in Font Awesome? Want to contribute new features? Here are a few things to remember:
+
Please do not submit new icons.
Please submit all pull requests against *-wip branches.
-
All pull requests submitted against master will be sumarily closed and this guide referenced.
+
All pull requests submitted against master will be summarily closed and this guide referenced.
After doing everything above, feel free to
submit a pull request.
diff --git a/library/font_awesome/src/_includes/examples.html b/library/font_awesome/src/_includes/examples.html
deleted file mode 100644
index 0598e28be..000000000
--- a/library/font_awesome/src/_includes/examples.html
+++ /dev/null
@@ -1,24 +0,0 @@
-{% capture stripe_ad_content %}
-
- After you get up and running, you can place Font Awesome icons just about
- anywhere with the <i> tag.
- Many examples appreciatively re-used from the Bootstrap documentation.
-
-{% endcapture %}
-{% include stripe-ad.html %}
-
-{% include examples/new.html %}
-
-{% include examples/inline-icons.html %}
-{% include examples/larger-icons.html %}
-{% include examples/bordered-pulled.html %}
-{% include examples/buttons.html %}
-{% include examples/button-groups.html %}
-{% include examples/button-dropdowns.html %}
-{% include examples/bulleted-lists.html %}
-{% include examples/navigation.html %}
-{% include examples/form-inputs.html %}
-{% include examples/animated-spinner.html %}
-{% include examples/rotated-flipped.html %}
-{% include examples/stacked.html %}
-{% include examples/custom.html %}
diff --git a/library/font_awesome/src/_includes/examples/accessible.html b/library/font_awesome/src/_includes/examples/accessible.html
new file mode 100644
index 000000000..2f51aed9c
--- /dev/null
+++ b/library/font_awesome/src/_includes/examples/accessible.html
@@ -0,0 +1,109 @@
+
+
+ With our thoughts on icon accessibility in mind, If an icon only adds some extra decoration or branding, it does not need to be announced to users as they are navigating your site or app aurally. Alternatively, if an icon conveys meaning in your content or interface, ensure that this meaning is also conveyed to assistive technologies through alternative displays or text.
+
+
+ Loading example (with fa-spinner icon)
+
+
+ Loading (with fa-circle-o-notch icon)
+
+
+ Loading example (with fa-refresh icon)
+
+
+ Loading example (with fa-cog icon)
+
+
+ Loading example (with fa-spinner icon)
+
+
+
+
+ Use the fa-spin class to get any icon to rotate, and use fa-pulse to have it rotate
+ with 8 steps. Works well with fa-spinner, fa-refresh, and fa-cog.
+
+ Note:
+ Some browsers on some platforms have issues with animated icons resulting in a jittery wobbling effect. See
+ issue #671
+ for examples and possible workarounds.
+
+ You can place Font Awesome icons just about anywhere using the CSS Prefix fa and the icon's
+ name. Font Awesome is designed to be used with inline elements (we like the <i> tag for
+ brevity, but using a <span> is more semantically correct).
+
+{% highlight html %}
+ fa-camera-retro
+{% endhighlight %}
+
+
+
+
+ Example: basic icon
+ If you change the font-size of the icon's container, the icon gets bigger. Same things goes for color,
+ drop shadow, and anything else that gets inherited using CSS.
+
- Use icon-border and pull-right or pull-left for easy pull quotes or
- article graphics.
+
+ …tomorrow we will run faster, stretch out our arms farther… And then one fine morning—
+ So we beat on, boats against the current, borne back ceaselessly into the past.
-
-
-
- Use a few of the new styles together, and you've got easy pull quotes or a great introductory article image.
- Or spinning icons for loading and refreshing content. Or fun big icons in multi-line buttons. You can combine all
- of them in any combination to get lots of new possibilities.
-
-{% highlight html %}
-
-Use a few of the new styles together ... lots of new possibilities.
-{% endhighlight %}
-
-
- Use a few of the new styles together, and you've got easy pull quotes or a great introductory article image.
- Or spinning icons for loading and refreshing content. Or fun big icons in multi-line buttons. You can combine all
- of them in any combination to get lots of new possibilities.
-
+
+
+ Use fa-border and fa-pull-right or fa-pull-left for easy pull quotes or
+ article icons.
+
{% highlight html %}
-
-Use a few of the new styles together ... lots of new possibilities.
+
+...tomorrow we will run faster, stretch out our arms farther...
+And then one fine morning— So we beat on, boats against the
+current, borne back ceaselessly into the past.
{% endhighlight %}
+ Use fa-fw to set icons at a fixed width. Great to use when different icon widths throw off alignment.
+ Especially useful in things like nav lists & list groups.
+
+
+
+
- icon-twitter on icon-check-empty
-
-
-
+ fa-twitter on fa-square-o
+
+
+
- icon-flag on icon-circle
-
-
-
+ fa-flag on fa-circle
+
+
+
- icon-terminal on icon-sign-blank
-
-
-
+ fa-terminal on fa-square
+
+
+
- icon-camera on icon-ban-circle
+ fa-ban on fa-camera
+
+
+
+ To stack multiple icons, use the fa-stack class on the parent, the fa-stack-1x
+ for the regularly sized icon, and fa-stack-2x for the larger icon. fa-inverse
+ can be used as an alternative icon color. You can even throw larger icon classes on the parent
+ to get further control of sizing.
+
{% highlight html %}
-
-
-
+
+
+
-icon-twitter on icon-check-empty
-
-
-
+fa-twitter on fa-square-o
+
+
+
-icon-flag on icon-circle
-
-
-
+fa-flag on fa-circle
+
+
+
-icon-terminal on icon-sign-blank
-
-
-
+fa-terminal on fa-square
+
+
+
-icon-camera on icon-ban-circle
+fa-ban on fa-camera
{% endhighlight %}