6

Yes. you can: Here I created a User group which has only access to the english part of the content. As you can see these are checkboxes. So you can grant access to multiple languages at once.


5

As carlcs said, this is already working as expected. Craft only enforces content validation rules for enabled entries (not including drafts), and most people prefer that behavior. If you want to change that behavior, you can write a plugin that provides its own entry validation logic, by latching onto the entries.onBeforeSaveEntry event. Just put this in ...


5

I guess this feature request will solve my problem... in the future: http://feedback.buildwithcraft.com/forums/285221-feature-requests/suggestions/7197199-ability-to-hide-or-disable-fields-based-on-a-user But in the meantime I did it with a small css hacking (no choice): protected function includeResources() switch ( $segments[ 0 ] ) { case 'entries' ...


4

If the users will never have access to the Craft CP then you can use categories or any other applicable field type (i.e. dropdown, radio buttons, tags, etc.) to create differentiation between the users. It really just depends on how accessible and/or 'static' you want the groups or sudo-groups to be. Categories and tags for example can be created dynamically,...


4

OK so here is my solution : 1/ define a custom permission for user groups public function registerUserPermissions() { return array( 'updateTopNews' => array('label' => Craft::t('Update Top News')), ); } 2/ simply add css to hide the field when user has not the permission in my plugin init function public function init () { ...


4

As other answers have touched on, the behaviour you're seeing is by design. I've written a plugin called Always Validate which will make Craft validate all disabled entries and categories – including entry drafts or entries saved by users not permitted to publish – which should solve your issue.


4

Craft is the perfect CMS to handle everything you just pointed out. Can Craft CMS handle bilingual sites? YES. https://craftcms.com/docs/localization-guide Is the Craft CMS admin available in French? YES. https://craftcms.com/support/cp-languages Can my client set up different user permission levels?** "YES". Depending on your use case this will be ...


4

There is a way - it's actually quite easy but you need to dig deep into Craft 3 to do it. In general: there is only one single Javascript function that fetches all elements for all index pages updateElements: function() { // Ignore if we're not fully initialized yet if (!this.initialized) { return; } this.setIndexBusy(); var ...


3

That's the idea behind Drafts, to store entries not yet ready to publish, unfinished ones so to speak. I think it does make sense to not validate the fields. Good feature!


3

On the server, check: if the folder exists? Check the folder permissions are set to 777 (could probably reduce to 755) Within Craft: In: Settings > Assets > Asset Sources - make sure File System Path and URL fields, have no leading forward slashes e.g. imgs/logos/


3

In addition to naboovalley's great answer... Actualités (News) page: These are news listings on the page (image + date + title/text), which point to individual article pages when clicked. Sure can. Basically you'd setup a new section in Craft to house these entries. Craft already has the title and date fields built-in so you just need to add an Asset ...


3

I'm not sure if this helps, but here is how I (attempt) to manage deployments/installs. I first create a user so I'm not using the root account. I tie that user to the apache user group. We'll call him 'user1'. I use beanstalk to deploy, and the deployment credentials are for 'user1'. Once all of the files have deployed for the first time, I'll log into ...


3

Edited based on comment below No sorry I see what you mean now. But I think with entry drafts you need to have first published an entry, then you create a draft from that entry, essentially creating two versions of the same one. I think for approving entries as comments this is going to lead to a lot of complexity and you might struggle to get the results ...


3

Of course as soon as I post this, I find the answer. /app/etc/config/defaults/general.php 'defaultFilePermissions' => 0664, 'defaultFolderPermissions' => 0775, The default settings are there, I just need to add them to my own config.


3

There’s no way to give a user group permission to create entries but not see those entries they created in the CP. The only way to achieve what you want would be to write a plugin that provides its own “save-entry” controller action, which allows users to create the entries without actually having the permission. The Guest Entries plugin would be a good ...


3

The {% requirePermission 'perm1' %} tag only supports a single permission. Behind the scenes it's effectively the same as: {% if not currentUser.can('perm1') %} {% exit 403 %} {% endif %} So I think either what you already have, or this: {% if not currentUser.can('perm1') and not currentUser.can('perm2') %} {% exit 403 %} {% endif %} <!-- Your ...


3

{% requirePermission %} can only take on parameter. To make your code a little easier to manage, you might want to check for false in your conditional and exit. That way you wont have to worry about closing the if statement later in your template code. You could even stick the code below in a partial _checkPermissions.html template to include on your pages ...


3

There is two similar plugins that look's like it might do the job (I have tested neither). Internal Assets MemberAssets


3

As far as I know there is no way to assign a 'group' using an entries fieldType. What I would likely do is create a category group called 'User Groups' (userGroups) that mirror my groups, with fields for 'title' and 'groupId'. Group Title 1 -> 1, Group Title 2 -> 2, Group Title 3 -> 3, etc. (Unfortunately, I think the only way to get the groupId is to ...


3

This might be considered more of a "workaround" than a technical solution, but I think it could actually solve your problem quite nicely... You can use CP CSS and/or CP JS to show or hide certain fields. You'll probably find that the CP Body Classes plugin is helpful for narrowing in on specific conditions. For example, you could show/hide certain fields ...


3

I had a similar problem where I needed to manage national and regional users groups where regional users should only see their own content. I didn’t like the idea of overriding the whole ElementIndexesController controller as most of its properties and methods are private and that could impede upgrades to Craft. I managed to have this work by using ...


3

Assuming you've recently updated to Craft 3.1, if you look in your userpermissions table you'll see that they're now lowercase and using UIDs rather than integer IDs, like this: editentries:3bb69b06-3e65-4ae5-8d70-6c47c1a88fbe The only place I can find anything like this documented is in the "Updating Plugins for Craft 3.1" guide https://craftcms.com/...


3

This feature was added in Craft 3.3.5, see the changelog. If you update to this version, your users should be able to control whether the activation email is sent.


2

I decided to try a different approach. I made two dropdown fields "studentlevel", one for the user where the admin can set the level from 1 to 12 and one in a matrix block with the video's, also from 1 to 12. I've set a conditional: {% for block in entry.videos %} {% if currentUser.studentlevel <= block.studentlevel %} video here {% endif %...


2

Under Settings/Users, you can create user groups and set what each different group has access to. So if there is a channel or section you don't want one group touching, then you can toggle it off for that group.


2

doesn't work if the client doesn't have the "Assign user groups and permissions" checked. That's not a limitation of the plugin, but a requirement of Craft. Is there a way to force every new user created in the CP by the client into a default group? Yes, that's what the previously linked plugin will do, with the caveat that the currently logged in user ...


2

You would have to write a custom plugin that provided its own UI (outside of the Settings portion of the control panel) and that plugin's controller could mimic Craft's SectionsController (with the exception of not requiring an admin) while calling SectionsService's saveEntryType. For security your plugin should also register a custom "canSaveEntryType" ...


2

When you mention new user group, is that a new group of admins/back end users or just people browsing on the front end? If it's on the front end, just checking the logged in user's group in twig against a new restricted entry type could give you want you want. {% if entry.type == "restrictedEntryType" and currentUser and currentUser.isInGroup('newUserGroup'...


2

The only point of those permissions is to determine whether the user has access to the plugins’ sections, so it would be pretty pointless to show the permissions for plugins that don’t have sections. The confusion here is probably just in the wording of the permissions. “Access [Plugin]” isn’t very clear on which aspect of the plugin you’re granting access ...


2

You should consider voting for this feature request: https://github.com/craftcms/cms/issues/915


Only top voted, non community-wiki answers of a minimum length are eligible