A non-editing teacher can only teach a Course, and can't touch any course resources/activities. But I want after every lesson he/she teaches they should be able to write a Feedback which Admins can read. Is there a way to give a permission to Non-editing teacher to upload a file or to add text/note in a new field ?
There is a feedback module/activity which can be set up for non-editing teachers.
https://docs.moodle.org/27/en/Feedback_FAQ#How_can_I_allow_teachers_and_non_editing_teachers_to_give_feedback.3F
Login as admin and go to the course.
Turn editing on and add a feedback module.
Save and display.
Choose "Permissions" from the feedback administration menu on the left.
In the dropdown list "Advanced role override" choose "non-editing teacher"
Look for "mod/feedback:complete" and set it to "Allow"
Click on "Save changes"
This will allow a non-editing teacher to give feedback. Although you will also need to set up the feedback questions, there are a variety to choose from.
Related
I would like to restrict access to a dialog's field (input field) to a given role.
Only specific role can enter the value in the the input field others can read only the field.
I looked into the Dialog Definition documentation of Magnolia CMS and found nothing on this topic.
Need code like
id:
label: Model ID
$type: textField
roles:
- superuser
# could also be written as
# roles: [superuser]
Might be duplicate of Magnolia CMS: permission to edit dialog
Anyhow, you can restrict either Path that user can access or you can restrict actions that user can invoke.
In former case, user will still be able to open the dialog and see the values in it in read only mode.
In latter user will not be able to open dialog or if you also apply same availability rules on the commit action in the dialog itself, user would not be able to save the dialog even if you failed to restrict all the actions that lead to opening the dialog.
But all in all it is important to remember that there are multiple ways to access the content hence if you want to restrict someone from either modifying or seeing certain content, you should restrict content by type/path not just hide the dialog.
So I have a resource (aka Maveoc) named Department that is configured as Visible in Menu.
In the generated app, the link to this resource/Maveoc is visible to all users, including those that do not have the permissions to access it.
From a security point of view, this is not a problem since it's not possible for the users to access that page.
It would be however nice to hide the link for the users that do not have access to it.
Any ideas on how to do this?
Thanks.
That's exactly what the boolean :check_access option in link_to_action does.
In graphical mode or if you specify a view's options, just check the checkbox.
Feel free to browse /macros_references in the Designer.
We know it's a tedious read for now: feedback is welcome,
and be sure that our V3 will have a much cleaner doc page.
I am using moodle 2.8
I wants to confirm user before edit course.
Basically I have a category name ex. 'Live' category
So when user move course into 'Live' category then want to show confirm box and if he click on yes then course will be update otherwise redirect to course edit page.
This will require changes to the Moodle core code (not usually a great idea, for ongoing maintenance) and would probably be a bit fiddly to implement - you would need to store all the submitted details somewhere in the confirmation form, then re-send them along with the confirmation.
It might be easier to make a small core code change to prevent the user from ever moving the course directly into the 'live' category (adjust the 'validation' function in the form submission), then have a separate admin page (within a local plugin, or maybe a block), that listed all the non-live courses and gave the option of moving them into the 'live' category (with the appropriate warnings / confirm action).
I need for certain users to only be able to create pages in certain categories based on their permissions. One reason for this is approvals ("flagged revisions"). If a user can create content outside of any category, then it could show up live on the web site. Even thought it wouldn't initially be linked anywhere directly in an existing page (except other unapproved pages) this can still be a problem.
I can prevent the user from creating a new page in the global scope (apparently this corresponds simply to "edit" permissions as I don't see a special permission for creating new pages), and then I can grant them permission to edit pages in the category their group is authorized to edit. But I can no longer see the "Menu:Wiki:Create a Wiki Page" option, and I can't figure out how to allow the user to create a new page in that category.
I can edit the group and set the "Default category assigned to uncategorized objects edited by a user with this default group" to the desired category. When I do that, a user in that group now has a "Create a Wiki Page" option show up in the Menu:Wiki sub-menu, but clicking on that does not bring up a new page for editing; instead if just brings up a list of existing wiki pages, without the option to create a new one!
If I create a link to the new page from an existing page, I am unable to edit it in any way. Clicking the link takes me to a page which indicates that the page does not exist, but which does not provide any way to edit it. Putting the title of the page directly in the URL, as in tiki-editpage.php?page=New+Page+Name brings up a "You do not have permission to edit this page" error page. Since any new page created by the user should have the category they have permission to edit, this does not make sense unless the category isn't set until after the initial edit permission check occurs, which creates a catch-22!
How do I let the user create a new page in any of the categories they have permissions to edit in?
If Categories are not the best tool for the task that's okay too. I don't really understand the difference between Categories and Structures with regards to which is better for what I'm trying to accomplish, however it seems Categories are the more "native" feature, which is why I am trying to use them.
I am trying to implement for a registered user to edit an article from front-end section of joomla 1.5. Is it possible? if so how can I proceed. I am new in joomla.
Thanks in advance.
There are two things you have to do. First you have to make sure that you have the correct user permissions set up. Go to your /administrator page and go to the user menu. There are a list of permissions in there - should be self explanatory.
The second thing you need to do is enable editing articles. Again, go to your administrator page and click the content menu. On the tool bar there is an 'options' button. Click that and there is an 'edit'tab. Enable all the options.
Now when the user logs into the front end, there will be a small 'edit article' icon on the article, but only if they have permission to edit it. If you find this icon isn't there, double check the user permissions.