Für den Inhalt verantwortlich

Kreisfeuerwehrverband Konstanz e.V.

Vorsitzender Helmut Richter

Hohentwielstr. 28

78315 Radolfzell

Vorsitzender@KFV-Konstanz.de

 

Eingetragen im Vereinsregister des Amtgerichts Radolfzell am Bodensee

 

Tätig für den Inhalt und das Layout:

Udo Artinger, Staufenstr. 2, 78224 Singen

Web-Orga@KFV-Konstanz.de

 

 

Hinweis zu Links

Per Gericht wurde entschieden,  dass durch eine Verlinkung auf Seiten Dritter, unter Umständen eine Mitverantwortlichkeit für deren Inhalte besteht. Laut Urteil kann dies nur dadurch verhindert werden, dass der Anbieter des Links sich ausdrücklich von den Inhalten Dritter distanziert.

Es gilt daher für alle Links auf unserer Seite: Der Kreisfeuerwehrverband Konstanz e.V. lehnt jegliche Verantwortung für die Inhalte von Seiten Dritter ab, auf die mittels eines Links verwiesen wird. Wir distanzieren uns ausdrücklich von den dort publizierten Inhalten und weisen daraufhin, dass lediglich die Webmaster der entsprechenden Seiten die Möglichkeit haben, Einfluss auf deren Gestaltung und die Inhalte zu nehmen.

 

  November 2017  
Montag Dienstag Mittwoch Donnerstag Freitag Samstag Sonntag
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
 
 
 

Freiwillige Feuerwehr Aach

Kontakt
files/Hegaubilder/Wappen/aach-wappen.gif  

Rathaus Stadt Aach
-Freiwillige Feuerwehr Aach-
Hauptstraße 16
78267 Aach

Tel.:  07774 / 92 99 74
Fax:  --

Mail: info@feuerwehr-stadt-aach.de
Web: www.feuerwehr-stadt-aach.de
Kommandant

Uwe Machui

Im Grund 29
78267 Aach

kommandant@feuerwehr-stadt-aach.de

Tel.: 07774 / 84 22
Fax: 07731 / 92 17 34

Gerätehaus

 

 

 

 

 

 

Besonderheiten

mietbares 60 kVA Aggregat

Why do we need roles?

Imagine that you and a friend of yours are managing a website. Maybe you are a successful web designer whereas your friend has no idea about CSS but is a committed writer. Therefor, you have decided to share the work. In the future, you will be doing the design and administration of the website and your friend will be writing articles. This is a basic principle of any CMS by the way - separation of content and design.

Now, as both of you have to have access to the back end, your friend would still be able to edit the look of the website or to create new user accounts, although he is actually not responsible for design or administration. Therefor, you want to disable these functions for his account. At this point, you have created a role (although it exists in your mind only) that you could name "editor" or "author".

To learn how user permissions can be restricted, let's take a closer look at the roles of our example users.

Access denied!

You are not allowed to access the requested page!

Maybe you are not logged in correctly?

If a user tries to access a protected page without permission, a special error_403 page will be called. In this case you can either display an error message (like we are doing now) by simply creating an article on this page, or you can redirect the user to another page (e.g. the welcome page).

Accordingly, if a user tries to access a page that does not exist, a special error_404 page will be called. Again, you can either display an error message or redirect the user to another page.
There are three ways to relate to a page: as the user who owns the page, as the group who owns the page or as someone else. Each role has its own set of permissions (similar to the UNIX chmod utility).

Of course, page Elements of Jazz Piano belongs to Mr. Wilson and he is the only user who is allowed to do something with it (remember that administrators have access to all pages and modules at any time).
Our example page Elements of Jazz Piano is only visible to members of the group Piano students. You will not be able to access the page when you are logged in as Donna Evans or when you are not logged in at all.