I am currently using MediaWiki as a documentation website, with login authenticated by LDAP.
However, we have hit a snag. Certain pages contain sensitive information. For example links that say "click here to log in". I would like to be able to protect certain pages from being edited by just anyone. I would like to allow certain groups of users (like employees) to edit those pages.
How do I set up page protection by group in MediaWiki (if it is possible)?
This is well-covered in the MediaWiki docs:
In addition the page protection options Andy Lester linked to you can also setup site wide protection against account creation and anominous editing. See MediaWiki Manual:Preventing access
Related
Anyone have ideas how to password protect a New Google-sites page or the entire site? No page-level permissions for New sites yet. Trying to share a couple pages with public and one with specific users.
Make a single account within your Google Workspace and share the site internally. You can't use your custom domain, only sites.google.com/xxx. Doesn't seem to work, see below...
Or other ideas, besides going to wix, squarespace, et al, which ALL allow password protected pages/ page level permissions. :)
I was wondering if it is possible to show/hide links on the sidebar navigation of a Google Site based on what the email / permissions the end user has. Has anyone ever done anything like this? I don't see any options under "edit site layout", perhaps it can be done with Google Apps Script? If anyone has any resources / links to similar problems and solutions, that would be appreciated. I can't seem to find anything on the subject myself.
Users will only see pages they have access to, so you can set individual page permissions and this will hide the page from some users. I use Google Groups to define the permissions and add users to the appropriate groups. If a user is in a group which has permissions to view, they have permissions to view. If they are in a group which has edit permissions, they have edit permissions. They will get the highest permissions associated with all the groups they are a member for which is applied to that page.
I'm working with Bolt CMS and I would like to create a new section on our website that is only accessible by a set of authenticated users. These users can only view the pages within this section of the site. Anonymous users would not see this section of the website in the menu, nor would they be able to navigate to it.
I see where I can create content types and assign roles to the types via permissions.yml, but how does that translate to authenticated page views? Is this possible without custom coding?
Backend permissions do not carry over to the front end, they are very deliberately kept separate.
There is an extension (bolt/members) being developed for the upcoming Bolt v3 that will implement this functionality, but still very separately from the backend.
I am trying to add extra buttons for my wiki editor page and I came across to this page:
http://en.wikipedia.org/wiki/User:MarkS/Extra_edit_buttons#Simple_Install
In the simple install section, I need to add extra code in monobook.js.
However, I cannot find monobook.js in my wiki folder. Can anyone give me some direction?
The "simple install" you linked to is for Wikipedia users who want to enable the gadget from their personal script file.
The correct topic would be #Installing XEB on your own Wiki, however I don't fully agree with that (importScript is deprecated, for example). Your alternatives are:
let your users just import the script from //en.wikipedia.org/w/index.php?title=User:MarkS/extraeditbuttons.js&action=raw&ctype=text/javascript. That's a possible XSS risk, but imported userscripts always are. Bonus: The will always get the latest version.
copy the script, the css and the images to your domain - which means you are in charge to maintain them. You could locate them anywhere in your server's file system, on a wiki page in the MediaWiki: namespace (only admins can edit) or on a user subpage that ends in .js (only that user and admins can edit). The last one was recommended in the help file, but I suggest not to use User:MarkS for that. Ensure nobody whom you don't trust could log into that account.
Then promote that location to your users, so they can import the script from there.
Even better: Install the Gadgets extension and migrate the script to a gadget, which users can easily enable in the settings.
Notice the script is deprecated and might not work with current MediaWiki versions. It depends heavily on script loading order, which needs some hacks to integrate well with the ResourceLoader.
See also Manual:Interface/JavaScript; there are similar customisations at Manual:User group CSS and Javascript and Manual:Page customizations.
The page you linked to talks about a user's monobook.js, which is a page called User:UserName/monobook.js.
If you want to do the same for all users on your wiki, you can use the site-wide monbook.js, which is not a file, but a page called MediaWiki:monobook.js.
Keep in mind that those scripts only apply if you're using the Monobook skin. If you want to have some script for all skins, use User:UserName/common.js or MediaWiki:common.js.
Went into my site and the site would not load. I had my friend look at the site and here is what he told me.
"I had to upload Drupal core files for version 5 and reconnect everything.
The previous user id’s and passwords should all work, there may be some missing data as I did have to pull one of the database files from back up so the site will have to be checked for integrity/links etc."
After he did that, the page was back up and running but editing tools were missing. In the edit mode, the page only shows html and no visual editing.
I also have not been able to access a page containing a calendar that was there before as a link from the home page.
Here is the URL - www.kntram.com. Any help would be very much appreciated.
The Wysiwyg (or similar editors like FCKEditor and TinyMCE) modules have probably just been deactivated when your friend replaced data in the database.
If you can, go to the Admin -> Site Building -> Modules page and reactivate the module (if it's missing, follow the link to download it, and upload it to the "modules" folder of your website).
If it's already activated, check the roles permissions in Admin -> User Managagement -> Permissions because the role your user belong to simply may not have the permission to use the editor activated.