I am working with mediawiki in my project. I want to restrict specific pages from users and it should be only accessed(along with edit, move and upload rights) to some group of users and administrator.
There are plenty of different access control extensions with different mechanism and effectiveness, you can check full list here: https://www.mediawiki.org/wiki/Category:Page_specific_user_rights_extensions
You may try PageSecurity (requires patches to core files) or SimpleSecurity.
Related
How to do it so that the customer can edit his website in a simple way, without having to enter the html code, so that he can add a photo or a file through the website instead of going to the editor. Thank you for help.
Use your favorite search engine to look for "content management system", also known as CMS.
There are some ready-to-use hosted solutions (e.g. blogger.com); there are also software packages you can run on your own server (e.g. WordPress). Depending on your needs, you might also want to consider a Wiki system, where only approved users have editing rights.
I have some pages which I want to restrict access to specific users, i.e, I want user A and user B only to view this page. How can this be done? Do I need additional extensions or it can be done through LocalSettings.php for example?
You could try this extension: Extension:AccessControl. I've not deployed it to my wiki sites, but a quick read of the pages suggests it might be what you're looking for.
Note though that as Tgr covered in the comments above, Mediawiki is not intended to operate like this, so the extension could be fundamentally flawed in its implementation. Practise due diligence if you try to deploy any 3rd party extensions. Alternatively, look into alternative CMSs that handle access control as a core feature.
I develop an application which has a manual/help system on a mediawiki site. When the user needs help in the application, he/she can click a button and access the corresponding help page on the wiki. This works pretty well and it is easy to keep the manual updated when I add/change functionality in the application.
Now I will release a new version of the application but some users will still use the old version. I would like to be able to "tag" an old revision of a page, e.g "#version1.0" and tag the new revision "#version2.0" and then when I link from the old application I link with the tag "#version1.0".
The reason why I want to have two versions of some pages is that some functionality changes between version1 and version2 and I want the users to be able to get the correct help/guides regardless of which version the users use.
I know that I can make a copy of the current wiki and call that version1 and then use the current installation for version2 but I want to avoid having two wikis on the same server.
So, is there a solution for this problem? I have tried to search for built-in solutions and extensions but could not find anything good..
If we're talking of a wiki with few pages, you can simply hardcode a permalink to the specific revision appropriate for the release in question. The permalink is a link which contains the parameter oldid=; in most skins it's found in the "tools" section of the sidebar.
If there are more pages but your users are minimally competent, you can either
hardcode all links to the current revision of all pages and trust that they'll follow the banner at the top to see more recent versions where needed (example), or
link the page history instead, with the appropriate year/month/offset/limit parameter (example), and trust that the user will click the suggested version or switch to more recent versions if really needed.
Otherwise, the "standard" MediaWiki way is sadly to run parallel pages for the different but similar content. There is another question for that scenario, IIRC focused on Wikibooks books for different versions of a same software.
This question might not belong here, and since this is related to HTML and reporting, I thought I could ask nonetheless.
I'm currently working to list all of the user identities in Designer for Identity Manager, by Novell.
I used the User Application connector and built the required queries. I also created a Provisioning and Request Definition with the necessary fields.
I can populate an HTML table with the results of the selected query, and get the user information from the Vault. Aside, I could use the organization's logo on the top-left-hand corner, the project name on the top-right with the report title just below on the right-hand side.
My concern is to set the organization's logo on the report.
Question
How can I define this image logo as an image resource into NIM so that I can use it in my HTML identity report?
Shall it suffice to include the path of the image into the HTML document? If so, how shall I set this image path? I don't know much about HTML.
EDIT #1
I know that NIM uses Tomcat as Web Server to handle the responses. Perhaps moving the image in its directory should suffice?
If so, how can I find out what is this path where I can put the image, so that it is considered part of the Website resource?
Father Ramon, the patronizing saint of IDM, responded in this thread in the Support Forums.
It is the path to where to leave the file that is incredibly non-obvious. He says the path is:
/opt/novell/eDirectory/lib/dirxml/rules/manualtask/mt_files or
/usr/lib/dirxml/rules/manualtask/mt_files (depending on whether you are
using eDir 8.7.x or 8.8.x. IDM will automatically find it there and
attach when referenced.
But I see in another thread that some people had issues getting this to work.
You may find the Support Forums (I linked the IDM forum specifically) helpful. A lot of people monitor those on this topic.
Also, you may find Novell Cool Solutions helpful for user contributed content. (I write as geoffc there).
In the IDM space, I have written a large number of articles that may help you in general, that are list on my Wiki Page.
If all that fails, the User Application Workflow engine uses a different email engine that may be more flexible. (Thus you could call a Start Workflow for a workflow with just a single Email action in it).
Additionally in IDM 4 there is library, lib-AJC included, full of ECMA functions (Which would work perfectly well in IDM 3.6 and 3.5) that include a set of emailing functions. If you have a driver configuration from IDM 3.6.1 odds are good you will have a lib-AJC in your tree already.
I have what seems like a typical usage scenario for users downloading, editing and uploading a document from a web page.
User clicks a link to download a document
User edits downloaded file
User saves the file
User goes back to the web page and uploads the new file with the changes
The problem is that downloaded files are typically saved in a temporary directory, so it can be difficult to find the file after it is saved. The application is for very non-technical users, and I can already imagine the problems with saved files being lost or the wrong versions being uploaded.
Is there a better way? Things I've thought about:
Using Google Docs or something similar.
Problems: forcing users to use new
application with less features,
importing legacy content, setting up
accounts for everyone to edit a
file.
Using WebDAV to serve the files. Not sure how this would work exactly, but seems like it should be possible
Some kind of Flash or Java app that manages downloads and uploads. Not sure if these even exist.
User education :)
If it matters, the files will be mostly Word and Powerpoint documents.
Actually, despite the fact that you have more flexibility with AJAX in developing application, the problem of uploading multiple files is not solved yet.
To the thoughts you've mentioned in your question:
Google Docs:
Online apps like Google docs are certainly appealing for certain use cases. However, if you'd like to upload Word and Powerpoint slides, you don't want the content to be changed once you've uploaded the document. The problem is that Google Docs uses its own data format and therefore changes some of the formats. If you go for an online app, I'd go for a Document Management Solution. I'm sure there are plenty (even free ones) out there; however, I didn't use any on them yet.
WebDAV It is possible and seems to me like the best solution. You can embed WebDav like any directory. Documents are locked until a user releases the document. Unfortunately, you don't have a web front end to manage the files or administer access restrictions.
It
Flash or Java app They do exist, for sure. I'd prefer Flash over Java since Flash Apps still run smoother within a browser. I would definitely not use a rich application, even if it is a Java Web Start app that can be downloaded and opens in a separate window. More and more, users seem to accept browser based web applications. Which brings me to point 4:
User education You can educate them, sure. But in the end you want them to want to use the system. Most often, users get easily used to a tool. However, if they don't like the tool, they're not going to use it.
Clear instructions to save to their desktop is a start. Then clear instructions to go to the desktop to re-up it. I've not run across an online MSWord viewer/editor or whatever format the file is, but I'm sure they exist, now that Google Docs and a few other online versions of MSOffice exist.
I would make sure that there are easy to follow instructions, plus a tutorial somewhere else (perhaps with a video too) to guide users through the process.