Loading...
 

Comments

  • pingus 01 Aug 09 01:55 GMT-0000

    You should evaluate what you can earn and what you can loose by dumping the adoption of category permissions and use a well engineered system of setting object permissions from ad-hoc, premade templates/roles:
    1) Perms would be in the objects, not outside them
    2) perms would be settable on a per object basis, not on a per-container basis
    3) no hineritance problems, just replication ones
    4) no risk of mixing content categorization with access permissions, nor need to limit/rule this

    Once you cross the field of category permissions, a whole lot of problems arise that are not really needed. An example is the fact that the need of a single different perm for any single object needs a category for itself, and you must handle the relation/dependance/inheritance with the parent category.

    What categories are good at (but any other union table would do) is to join objetcs:
    -groups (that should become categorizable objects)
    -resources
    -presets object permission templates (roles) that can be stored as groups too, and thus categorized.

    Something I think is useful is some sort of group level (like in UNIX, where users groups start at gid 1000), or another way to cross categorize groups to categories that explain their 'level'. But this is not yet category permissions. With this you can select which 'object permission templates (stored as groups)' can be applied to which 'users groups'. And which 'users groups' can be selected for inclusion into other 'users groups'.
    Because it should be also possible to add groups to groups, not only individual users.

    I don't understand if this idee fixe with category permission is because these can be more easily replicated/transferred by profiles/datachannels, or if because it seems that bringing an object into a category is somehow more a simpler operation that applying a preset or perms to the object... The latter is very trivial and immediate too, and in fact the code has been there for a time in aulawiki.

  • Louis-Philippe Huberdeau 02 Aug 09 09:30 GMT-0000

    Temporary breakage prevents from making a proper reply.

    My view is that category permissions will simplify management by reducing the amount of places permissions have to be verified. Object permissions will stay, but when using categories, they will mostly be used for exceptional cases. I think synchronization problems are much harder to solve and can cause privacy issues if rules change and some objects are forgotten.

    However, using category permission remains optional. Disabling categories make these permissions go away, and it could be possible to just disable the category permissions. As part of the permission UI revamp that will begin shortly, permission auditing should be easier and better, and batch allocation should also improve the experience with both category permissions and object permissions.

    As far as permission templates go, it would mostly be handled by having a model page and copying permissions from it.

Keywords

The following is a list of keywords that should serve as hubs for navigation within the Tiki development and should correspond to documentation keywords.

Each feature in Tiki has a wiki page which regroups all the bugs, requests for enhancements, etc. It is somewhat a form of wiki-based project management. You can also express your interest in a feature by adding it to your profile. You can also try out the Dynamic filter.

Accessibility (WAI & 508)
Accounting
Administration
Ajax
Articles & Submissions
Backlinks
Banner
Batch
BigBlueButton audio/video/chat/screensharing
Blog
Bookmark
Browser Compatibility
Calendar
Category
Chat
Comment
Communication Center
Consistency
Contacts Address book
Contact us
Content template
Contribution
Cookie
Copyright
Credits
Custom Home (and Group Home Page)
Database MySQL - MyISAM
Database MySQL - InnoDB
Date and Time
Debugger Console
Diagram
Directory (of hyperlinks)
Documentation link from Tiki to doc.tiki.org (Help System)
Docs
DogFood
Draw -superseded by Diagram
Dynamic Content
Preferences
Dynamic Variable
External Authentication
FAQ
Featured links
Feeds (RSS)
File Gallery
Forum
Friendship Network (Community)
Gantt
Group
Groupmail
Help
History
Hotword
HTML Page
i18n (Multilingual, l10n, Babelfish)
Image Gallery
Import-Export
Install
Integrator
Interoperability
Inter-User Messages
InterTiki
jQuery
Kaltura video management
Karma
Live Support
Logs (system & action)
Lost edit protection
Mail-in
Map
Menu
Meta Tag
Missing features
Visual Mapping
Mobile
Mods
Modules
MultiTiki
MyTiki
Newsletter
Notepad
OS independence (Non-Linux, Windows/IIS, Mac, BSD)
Organic Groups (Self-managed Teams)
Packages
Payment
PDF
Performance Speed / Load / Compression / Cache
Permission
Poll
Profiles
Quiz
Rating
Realname
Report
Revision Approval
Scheduler
Score
Search engine optimization (SEO)
Search
Security
Semantic links
Share
Shopping Cart
Shoutbox
Site Identity
Slideshow
Smarty Template
Social Networking
Spam protection (Anti-bot CATPCHA)
Spellcheck
Spreadsheet
Staging and Approval
Stats
Survey
Syntax Highlighter (Codemirror)
Tablesorter
Tags
Task
Tell a Friend
Terms and Conditions
Theme
TikiTests
Timesheet
Token Access
Toolbar (Quicktags)
Tours
Trackers
TRIM
User Administration
User Files
User Menu
Watch
Webmail and Groupmail
WebServices
Wiki History, page rename, etc
Wiki plugins extends basic syntax
Wiki syntax text area, parser, etc
Wiki structure (book and table of content)
Workspace and perspectives
WYSIWTSN
WYSIWYCA
WYSIWYG
XMLRPC
XMPP




Useful Tools