Difference between revisions of "Talk:IntraACL"

From Wiki4Intranet
Jump to: navigation, search
(added a header)
(MediaWiki 1.27.1 Support: new section)
Line 60: Line 60:
 
I don't consider this to be a bug, but I think it would be helpful if there was a note about this somewhere in the documentation for other people who encounter the same problem.
 
I don't consider this to be a bug, but I think it would be helpful if there was a note about this somewhere in the documentation for other people who encounter the same problem.
 
{{wl-comment:  }}
 
{{wl-comment:  }}
 +
 +
== MediaWiki 1.27.1 Support ==
 +
 +
Does this extension support MW 1.27.1? I see the patch for 1.26 but when I ran it against my 1.27.1 installation it broke some things.
 +
 +
I reverted the Includes folder with the files from my install/upgrade file to get back up and running.

Revision as of 23:11, 31 August 2016


creating a template that allows edit right only to the creator of the page

is it possible with this extension ? if yes how ?

Thanks,

Nicolas

Uninstallation instructions

Hi, I'm missing instructions how to remove the extension after it has been set up according to this page. Krichter (talk) 21:54, 31 August 2014 (MSK)


Malfunctions

Mediawiki : 1.23.4 IntraACL : 2.1.6

Case 1 Combine mode : OVERRIDE

Rules applied via IntraACL

  • ACL on the namespace without read or edit permission for the user
  • ACL on the category of the page without read or edit permission for the user
  • No ACL on the page
  • But ACL on the parent category of the page's category with read permission for the user


In this case, the page is visible for the user when he accesses by the direct link or through search page. Therefore, I was obliged to prohibit the use of hierarchical categories. If the user, on the parent category clicks the category without read or edit permission for him, he was forbidden.


Case 2 Combine mode : SHRINK

Rules applied via IntraACL

  • ACL on the namespace with read permission for the user
  • ACL on the first category of the page without read or edit permission for the user
  • ACL on the second category of the page with read permission for the user
  • No ACL on the page


In this case, the page is visible for the user. Therefore, I was obliged to prohibit the use of multiples categories for a page.

In SHRINK mode, is-it possible to test all the categories Security Descriptor and if just one category deny the access, the user is forbidden.


Thanks you very much for this extention.

Best Regards

Requires HTTP Server Name Header

Hi, I've found that IntraACL doesn't work unless your web server sets the HTTP server name header. The ACL tab is missing, and the access controls aren't applied, but the Special:IntraACL page still appears.

I don't consider this to be a bug, but I think it would be helpful if there was a note about this somewhere in the documentation for other people who encounter the same problem.

MediaWiki 1.27.1 Support

Does this extension support MW 1.27.1? I see the patch for 1.26 but when I ran it against my 1.27.1 installation it broke some things.

I reverted the Includes folder with the files from my install/upgrade file to get back up and running.