Closed (works as designed)
Project:
Open ReadSpeaker
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Minor
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
24 Jul 2014 at 02:08 UTC
Updated:
17 Jul 2019 at 07:15 UTC
Jump to comment: Most recent
Comments
Comment #1
killua99 commentedWhat about you have an editor role and an admin role and you don't want to mix this settings ?
Comment #2
torpy commentedIt wouldn't help, the variables are still set globally with the block method and don't change depending on role.
Comment #3
killua99 commentedNo, I'm talking on edit this settings. If you need for some reason some CRM team / editor team don't see /touch the "delicate" settings you might worry about it.
In the block settings are what you need edit the text and so. In the config settings you have what you need to setup the service.
Don't see the point for real.
Comment #4
killua99 commentedI'll postponed this issue. If you can redo others patch with require this one will be good.
Comment #5
torpy commentedI'm still not convinced the block settings page is the place to put those. Maybe an extra permission that then controls what fields you see on the admin page?
It'd work out to be better control for site admins as well. They don't need to give the editorial team access to entire block admin page if they don't want to.
Essentially, the 'acount_settings' fieldset would only be accessible by users with 'administer open_readspeaker'. The 'read_settings' fieldset would then be accessible by users with 'administer open_readspeaker' and those with 'manage open_readspeaker' (or whatever the second permission is).
Comment #6
mpp commentedLet's close this for now as this is an old Drupal 7 patch and hasn't had any port to Drupal 8.
Also, in Drupal 8 multiple blocks can be created so different reader blocks can be created with different settings which makes it a 'feature'.