was created to power free_site
-s, it is possible to configure it to restrict certain actions from all or some users by changing the following variables in your configuration file chiq.cf
- Private Pages: No_Index_Page, $noindex_site
Chiq_Chaq does not support read restriction per se, but you can protect pages from indexing by search engines by tagging them as No_Index_Page. This does not prevent people from reading them, but it significantly lowers the probability of outsiders getting to know about them.
You can have an entire group not indexed by setting the configuration variable $noindex_site to 1;
- Read-Only Pages: @static_titles
To make certain pages static, add their titles to the @static_titles list. Users will only be able to view these pages, but not change them.
- Read-Only Site: $static_site
You can make all the pages static by setting $static_site to 1.
You can also convert an entire Chiq_Chaq site to static HTML files with the tool chiq2html, available at http://sourceforge.net/projects/chiqchaq
- Partial Permissions: @disabled_actions
You can prevent users from making certain types of changes (for example, deleting pages) by specifying them in the @disabled_actions list. Possible actions to disable are: read, add, edit, rename, delete, new, versions, author. The effects of the last three are:
- new – users will not be able to type a new page title in the "Add comment" form, and words_with_underscores will not be links when there is no existing page with that name.
- versions – when editing a page, users will not be able to access the old versions of the page.
- author – users will not be able to change their pen-name.
- Single Section Actions: %section_actions
You can configure which actions will be easily available in section-titles, by deleting the actions you want to hide from %section_actions.
(Note: "edit section" is not yet implemented.)
- Administrator(s): @admin_users
Administrators are not restricted and are able to change any page, even read-only pages. To grant administrator privileges to a user, add her ID to the @admin_users list.
- Banning: @banned_users and @banned_ips
To prevent a user from making changes to pages, add her ID to @banned_users or (in version 1.8 or later) add her IP to @banned_ips. The user will still be able to view pages. Banning any user also bans users that do not accept cookies, as a side effect.
Note: Banning based on cookies and IPs is easy to bypass. Use it as a way to send a clear message to a user, not as a way to protect the site from malicious attacks.
If you restrict permissions, you will probably need to review the page Terms_of_Use
, and change its default content if it is not appropriate for your site.
Back to the Admin_Manual