|
|||
Lines: 1-11 | Lines: 1-12 | ||
- | {maketoc} |
+ | The Tiki Category feature allows to manage and classify content being created on the fly, by different groups with different access permissions, and make navigation and indexing much easier. |
- | + | ^This page ((needs review))^ !Categories Admin | |
Category can be used together with ((groups)) to hide objects/pages from specific groups of users, creating "private" areas that may even look different from the rest of the site. | Category can be used together with ((groups)) to hide objects/pages from specific groups of users, creating "private" areas that may even look different from the rest of the site. | ||
- | Are categories the right tool for you? |
+ | Are categories the right tool for you? See: ((How to organize your content)) |
+ | __To access__: Click the __Categories__ icon {icon name="sitemap" rotate="270" title="Image may vary depending on icon set in use."} on the ((Admin Panels|Admin Panel)) %%% or Access __http://example.org/tiki-admin.php?page=categories__ | ||
!!Creating categories and sub-categories | !!Creating categories and sub-categories | ||
Lines: 36-41 | Lines: 37-68 | ||
^::{img src="img/wiki_up/categories_admin_06.png" }::^ | ^::{img src="img/wiki_up/categories_admin_06.png" }::^ | ||
+ | !!Creating categories in batch from CSV files | ||
+ | ^Also see attached MS Word and PDF files that describe how to create categories in batch | ||
+ | by uploading CSV files^ | ||
+ | {file name="Tiki 3 - How to Create Categories In Batch by Uploading a CSV File.pdf"} | ||
+ | {file name="Tiki 3 - How to Create Categories In Batch by Uploading a CSV File.doc"} | ||
+ | !!!!Step 1 : Create A CSV File that Describes Your Categories | ||
+ | ^{img src="tiki-download_file.php?fileId=126" alt="Categories description CSV file"} ^ | ||
+ | !!!!Step 2 : Navigate to [[http://<server-name>/tiki/tiki-admin_categories.php]] | ||
+ | and use the ''Batch upload'' panel to select your Category CSV file and upload it | ||
+ | to your Tiki [[replace <server-name> with the name of your server, such as "localhost"]] | ||
+ | ^{img src="tiki-download_file.php?fileId=127" alt=""} ^ | ||
+ | !!!!Step 3 : Verify that your new categories have been created | ||
+ | ^{img src="tiki-download_file.php?fileId=129" alt=""} ^ | ||
But imagine that you would like that all content is readable only by registered users of your site, and only the content categorized as "__7.Validated__" is readable by anonymous. You could achieve that using __category permissions__ (see following section). | But imagine that you would like that all content is readable only by registered users of your site, and only the content categorized as "__7.Validated__" is readable by anonymous. You could achieve that using __category permissions__ (see following section). | ||
!! Assigning permissions to categories | !! Assigning permissions to categories | ||
Lines: 44-51 | Lines: 71-78 | ||
The category permission system follows the following rules. | The category permission system follows the following rules. | ||
# Categories are treated as objects, just like wiki pages and forums, etc. | # Categories are treated as objects, just like wiki pages and forums, etc. | ||
- | # Category perms are |
+ | # Category perms are hierarchical, unless you override the "& all children" option. Child objects will automatically inherit permissions from their parents. |
# If there is a conflict between child and parent perms, permissions assigned to child objects take precedence over permissions assigned to parent objects. | # If there is a conflict between child and parent perms, permissions assigned to child objects take precedence over permissions assigned to parent objects. | ||
- | # If a category allows (or does not disallow) user access to an object, the user's (( # If no permissions are assigned to an object and any of its ancestor objects, global permissions for that users |
+ | # If a category allows (or does not disallow) user access to an object, the user's ((Groups)) permissions must also allow access to that kind of object. # If no permissions are assigned to an object and any of its ancestor objects, global permissions for that users Groups are applied. |
# Objects can be placed in more than one category. | # Objects can be placed in more than one category. | ||
# Multiple category permissions: In the case where an object belongs to more than one category, the user must have permissions in ''all'' of the applied categories to perform that action. In other words, the category where the user had the lowest permissions takes precedence when considering if user can perform the action or not. | # Multiple category permissions: In the case where an object belongs to more than one category, the user must have permissions in ''all'' of the applied categories to perform that action. In other words, the category where the user had the lowest permissions takes precedence when considering if user can perform the action or not. | ||
Lines: 137-143 | Lines: 164-167 | ||
Show Category Objects|Show the objects sorted by categories and object types that are in the same categories of the object at the bottom of a page | Show Category Objects|Show the objects sorted by categories and object types that are in the same categories of the object at the bottom of a page | ||
Category used in tpl|If you plan to use the category in the templates, you need to activate this feature. This will slow down you application as all the categories are looked for for the current object|| | Category used in tpl|If you plan to use the category in the templates, you need to activate this feature. This will slow down you application as all the categories are looked for for the current object|| | ||
-=Related documentation pages=- | -=Related documentation pages=- | ||
Lines: 146-147 | Lines: 170-173 | ||
* ((Categories Details)) | * ((Categories Details)) | ||
+ | !!Alias | ||
+ | *(alias(Categories-Admin)) |