We need for our clients to be able to add an entry to their blog which is being used for their news feeds but the Add Blog Entry option is not available to registered users, only to the Host account. How would I go about setting the blog up so that the users can add a blog entry as well?
Thanks,
James
On the page where you have the module installed, go into the module's settings and near the top, you should see a section called Permissions. In there, you'll want to give Registered Users (or another role) edit permissions (and/or perhaps other permissions).
Related
I'm playing around with the CakeDC/Users plugin and I can't for the life of me figure out how to give permission for non-logged in visitors (lets call them 'guests') to access things like my /pages/home, or if I was to do a Blog plugin, allow guests to see posts etc (but not edit).
Is this possible using the 'permissions.php' file? Seems to only work for user groups (admin and user) rather than guests? Or do I have to play around with $this->Auth->allow() and $this->Auth->deny() as in this post which seems to make the permissions.php file kinda pointless...
RBAC permissions defined in CakeDC/Users are checked in the authorization step, which means you have a user already logged in (authenticated) requesting access to a specific controller/action.
All these checks happen in the core CakePHP AuthComponent per the plugin configuration.
You want to exclude specific pages from Auth, which is something managed outside of the plugin (for now). The right way to do that is using
$this->Auth->allow('yourAction');
In the controller's beforeFilter function.
I have had a user with browser role which has been able to make subscriptions but he has not seen CC and BCC fields. Because of that, I added Content Manager role for him to all folders and reports and after that, he cannot make more subscriptions or manage reports in any way. He gets error
"The permissions granted to user 'domain\username' are insufficient for performing this operation". Now he can only see the reports.
Do you have any idea?
Browse to Site Settings, Configure item level role definitions.
Then check what settings you have for Content Manager. Maybe someone removed them.
When I added a role also to the Home folder then it starts working. I don't know why, before this was not needed.
Is it possible to restrict access of Site public pages for a few Users through configuration?
Now by default in liferay anybody can access the Public pages [that is the reason they are named Public Pages :-) ] of any Site whether Open, Restricted or Private.
In our system we force login to access even Public pages, but once logged-in the User can see the public-page of any Site if he has the URL for it.
To make the requirement more clear:
I have 3 users in the system, User01, User02, User03.
I have 3 Sites - Site01 (open), Site02 (restricted), Site03 (private)
These Sites have only one User respectively.
All these 3 users can see public-pages of all three Sites. So now what I want is that only User02 should be an exception, that is User02 should not be able to access the Public-pages of Site01 and Site03.
Is this possible through configuration? Or will it require changes in liferay code (possibly through hook)?
Even if we can limit access to Public-pages for all Users who are not member of that Site that will also work?
Any ideas or help is much appreciated. Thanks.
Here are few steps to achieve this:
You can remove view permission from guest role(or all role as per your requirement) to specified page(here from public pages as per your
requirement) from manage permission tab of page.
Create a new role(which will allow view permission) and from manage permission of page assign this role view permission.
Now assign these newly created role to users to whom you want to have view access to pages
For your last question
Even if we can limit access to Public-pages for all Users who are not
member of that Site that will also work?
This can be achieved by removing VIEW permission for Guest role for each of Public pages of site.
HTH,
Thanks,
Trying to figure out if I can do the following via the box-api.
authenticate as an enterprise admin
lookup a user (in our case a special box user named "group_xxx" where this account will serve as a non-person shared group like "group_math_dept", "group_engineering_dept", etc...).
query for the root folder info for a given user-id (perhaps "GET /users//folders/0"
(tried that it doesn't work).
View the list of enterprise users with whom the given folder has been shared.
Modify the list of enterprise users with whom the given folder has been shared.
What I'd like to do is develop an app to delegate admin of these special group accounts to an appropriate individual in the given group. We can maintain who admins what locally. I can authenticate as one of our Box Admins (i.e. I have working code for steps 1 and 2). However, I don't see support in the API v2.0 doc for steps 3, 4, and 5.
Am I missing anything?
Unfortunately my understanding is the same as what you've found; that account and meta operations like steps 3 through 5 are not currently supported through the API.
UPDATE:
Looking at Box's developers blog it looks like functionality for steps 4 and 5 were actually just added, but are not yet in the documentation.
http://developers.blog.box.com/2012/09/10/v2-api-updates-keep-rolling/
Box actually has some more enterprise/admin API methods in private beta. Those are made accessible to early testers for a controlled environment, and include methods to perform operations on behalf of other users with administrative privileges.
If you're interested, feel free to email api [at] box [dot] com to discuss the testing of beta methods.
How can i disable or delete an user in mediawiki?
I can delete the records from the db but i am not sure if this would affect anything else in the wiki.
Any suggestions would be welcome
Thanks
Prady
1. This solutions is available out of the box for MediaWiki 1.16+
The user and all the contributed content will remain but they will not be able to log in any more.
There are two steps that need to be done:
First block the user using the link in Special Pages.
Blocking can be performed against user id or IP address to prevent them from editing the wiki.
They will still be able to log in and view content.
Then in LocalSettings.php add $wgBlockDisablesLogin=true; ($wgBlockDisablesLogin).
Now upon logging in the user will be greeted with Login error. This user is blocked. Login not allowed..
2. This solutions requires an extension that works with MediaWiki 1.29+
If you want to completely remove access to a user, e.g. on a simple private wiki, it's not possible to simply delete the account (unless no edits have been made); you can block it, but the user will still be able to read pages. However, using User Merge and Delete extension you can merge the account in another one and delete the former; the original account will then "disappear".
Also:
If you want to preserve history readability (i.e., to have edits from the user to be still shown under his name), you can create a new account e.g. with username "OriginalUserName (deactivated)" and then merge "OriginalUserName" into the former, or even use Renameuser extension.
I suppose if you wanted to revive the user later on you would need to repeat this process but this time you would merge OriginalUserName (deactivated) into OriginalUserName.
See Preventing Access page in the MediaWiki manual.
There's a special page that Admin users can see, /Special:BlockIP. Block them there.
You can also get to it from the Special Pages page, /Special:SpecialPages.
you could also reset the password of the user via
/Special:PasswordReset
note: I would not recommend deleting data via scripts in the DB. there are various functionalities for rolling back unwanted user edits, merging contribution from one user to another, etc.