I need to restrict the template to be available only for a set of user. The template should not be available for other users while creating new page. How can I do that in CQ5?
First, read this documentation page. After that create an group containing all users which should be able to create a page using the template. Then add following ACLs to the template node (eg. /apps/myapp/templates/mytemplate):
deny jcr:all for everyone
allow jcr:read for (created group)
Related
TCA offers the possibility for conditional displaying fields using displayCond. for an instance HIDE_FOR_NON_ADMINS allows to display field only for admin, but is there a way to display given field only for its creator, determined by cruser_id field?
Not out of the box. You can hook into TCEMAIN (DataHandler) or TCEFORM (FormEngine) to archive this.
You can however use access rights and set the rights to show the page (storage folder) only the the given backend user. Check out the access module.
I (as admin) want to create a few pages in the wiki where the users may/can create subpages or similiar hierarchical structures.
Is it possible to automatically create a hierarchical order (e.g. a few spaces like Tutorials / Info / Resources) and restrict the users from creating pages outside those defined areas?
I already tried to revoke edit rights from the users and use Structures and only granting rights to edit the content of the structures. This seems to work pretty well, but when a user creates a new sub pages he has no rights to edit them later, because the new files get the global rights (no edit permission).
Is there a right way to do that?
You can do this via Categories.
Create a category for each structure (Tutorials, Info, Resources).
Remove the global tiki_p_edit permission from the group, and edit the each category's permission to allow tiki_p_edit for that specific category.
Categorize each of the wiki pages within the appropriate structure.
Use the wiki "force categorization" option to automatically force newly created pages in the structure to be in the appropriate category.
I wonder how it is possible to change the default settings for creating new users. At the moment I must remove the “live edit” permission and change the BE language to german for every single user.
I have two groups for my users AUTHOR and MAINAUTHOR. Members of AUTHOR should only have access to the draft workspace and only MAINAUTHOR’s members should have the live workspace too. (MAINAUTHOR inherits from AUTHOR and should add only the live permission.)
I found out that I can use setup.override.lang = de in the group options to change the language but I can’t find an equivalent for the live permission.
You can change the default pageTS for your own user via userTS (or for a whole group).
There you can use TCAdefaults to set default values for your be_users table.
https://docs.typo3.org/m/typo3/reference-tsconfig/11.5/en-us/PageTsconfig/TcaDefaults.html
Example from TYPO3 Core Docs for pages table
# Show newly created pages by default
TCAdefaults.pages.hidden = 0
You could try the extension sys_workflows[1] which was made for these kind of tasks. The extension should work on TYPO3 4.5 but doesn't work on a 6.2beta3 (just tested).
[1] http://forge.typo3.org/projects/extension-sys_workflows
You can configure the default values in the user TSconfig for new users. All options are described in the user TSconfig manual: https://docs.typo3.org/m/typo3/reference-tsconfig/11.5/en-us/UserTsconfig/Setup.html
Also explained is how to configure user TSconfig in general:
https://docs.typo3.org/m/typo3/reference-tsconfig/11.5/en-us/UsingSetting/UserTSconfig.html
Is it possible to have multiple backend user group access lists in Typo3? For instance, I would like to have an access list at the root level (which seems to be the normal case),
and another one further down in the page tree. The title in the backend would then look something like:
Edit Backend usergroup "Author" on folder level
Is this possible?
Access list are assigned to groups. So this is not possible with a stock TYPO3. However you might want to try the extension be_acl.
How do I hide the content resource field from non-admin users?
So you'd like a user to be able to change document fields such as title, alias etc but not the content?
You can not lock individual fields to admin user (as far as I know). You can either lock the whole page/resource or you could put the content that you want to be locked into the template for that document and lock the template to only the admin user which would achieve the same effect.
Make sure you don't have a reference to [+content+] in the template and even if the user enters document content it won't impact the page.
New answer instead of editing the above as this is a much cleaner solution.
Create different user groups eg. Admin & Editor
Make sure admin is in the admin user group
Create a template variable for your content and in the Access Permissions section only tick the admin group.
Assign the TV to your template.
Now if the user isn't in the admin user group the TV won't even be visible when they are editing the resource.
Hey, thanks for the answer.
I thought I'd post what I ended up doing.
With MODx Evo 1+, you have managermanager included. After removing the included file(which is used rather than the default chunk) using the rules in there I can rename hide and sync content.