[Sun Aug 25 11:22:32 2013] [error] [client 192.168.0.100] PHP Notice: Undefined variable: cluster in
/var/www/sites/mediawiki001/extensions/IntraACL/includes/HACL_ACLSpecial.php on line 282, referer:
http://SERVERNAME/sites/mediawiki001/index.php?title=Special:IntraACL&ac...
[Sun Aug 25 11:22:32 2013] [error] [client 192.168.0.100] PHP Warning: Invalid argument supplied for foreach() in
/var/www/sites/mediawiki001/extensions/IntraACL/includes/HACL_ACLSpecial.php on line 282, referer:
http://SERVERNAME/sites/mediawiki001/index.php?title=Special:IntraACL&ac...
[Sun Aug 25 11:22:32 2013] [error] [client 192.168.0.100] PHP Notice: Undefined index: in
/var/www/sites/mediawiki001/extensions/IntraACL/includes/HACL_ACLSpecial.php on line 341, referer:
http://SERVERNAME/sites/mediawiki001/index.php?title=Special:IntraACL&ac...
[Sun Aug 25 11:22:32 2013] [error] [client 192.168.0.100] PHP Warning: Invalid argument supplied for foreach() in
/var/www/sites/mediawiki001/extensions/IntraACL/includes/HACL_ACLSpecial.php on line 341, referer:
http://SERVERNAME/sites/mediawiki001/index.php?title=Special:IntraACL&ac...
[Sun Aug 25 11:22:32 2013] [error] [client 192.168.0.100] PHP Notice: Undefined variable: edges in
/var/www/sites/mediawiki001/extensions/IntraACL/includes/HACL_ACLSpecial.php on line 357, referer:
http://SERVERNAME/sites/mediawiki001/index.php?title=Special:IntraACL&ac...
[Sun Aug 25 11:22:32 2013] [error] [client 192.168.0.100] PHP Warning: Invalid argument supplied for foreach() in
/var/www/sites/mediawiki001/extensions/IntraACL/includes/HACL_ACLSpecial.php on line 357, referer:
http://SERVERNAME/sites/mediawiki001/index.php?title=Special:IntraACL&ac...
These warnings went from the "rightgraph" tab - this was an experiment to display all defined ACLs graphically using Graphviz. So, it seems it emits warnings when no ACLs are defined. Nothing to worry about, and maybe I've already fixed it in the storage-rewrite branch...
Also: I went to Special:IntraACL and understand that I will have to learn how it works :-)
It's not that hard... rights are set on ACLs, ACL is a wikipage with special content in ACL namespace. ACLs can be created for pages, categories and namespaces. By default they are additive, i.e. if page X is in a protected namespace, has two protected categories and also has page ACL set for it, the rights from all these ACLs are summarized.
Category ACL affects pages that are in the category and its subcategories, and also the category page itself ("Category:X"). Namespace ACL obviously affects pages from that namespace. Page ACL affects single page.
To create page or category ACL the simplest is to use "ACL" tab which is displayed between "page" and "talk" tabs on the top. Just click it and the ACL article will show up. Then you click "create with editor". In the editor, select right target type - user/group/* (all users)/# (all registered users)) in the selectbox on the right, and start typing the target (user/group) name - the input has autocomplete. Then use checkboxes to grant rights to the selected target. The editor composes corresponding wikitext and then you save it using Save button [ :-) ]
Also you can access the editor from Special:IntraACL ("create ACL"), for example to create namespace ACL.
Groups aren't MediaWiki builtin like "sysop", IntraACL uses its own groups that are also managed from Special:IntraACL under "groups"/"create group". The UI is similar to that of ACLs.
Is there a kind of "user guide" somewhere ? (in English, if possible :-), else I will try with Google Translate if in Russian...) I believe that http://wiki.4intra.net/IntraACL/ru is the user guide ???
Kind of... There's no real "user guide", mostly it explains some concepts about ACLs and differences from HaloACL. But there's something to learn, anyway.
Also: not sure, but I believe to have read somewhere that IntraACL isn't compatible with Semantic ? True ? False ?
Yes, it is, in the sense of that it doesn't protect SMW properties and query results. It's mentioned on http://wiki.4intra.net/IntraACL/ru mostly because the original extension (HaloACL) tried to protect them in some weird manner (they've tried to encrypt them and then decrypt in some places O_o)... And because I've removed this feature.
It's basically "incompatible" with any extension that does direct database access - i.e. its usage may lead to leaks. But it's usually simple to make it "compatible" by just adding userCanRead() checks. Extensions that we use are already patched, you can take them from github.