joomla/Component-Builder
joomla/Component-Builder
39
23
Fork 11
Code Issues 78 Pull Requests Projects 4 Wiki Activity

Updated 022 Global Settings of Component Builder (markdown)

Amigo 2019-06-25 12:41:45 +02:00
parent 2a113dfbdb
commit 7990eae783
1 changed files with 10 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
022-Global-Settings-of-Component-Builder.md

@ -37,16 +37,21 @@ Currently there are two folder paths that can be used. It is the Backup folder p
### Permissions ### Permissions
The permissional structure in Component Builder is not that intense, but there are a lot of permission switches. With the latest Joomla release of Joomla 3.5, this permissional structure updating construct is made much easier. A problem had been experienced in the past where the data set of permissions was to big and when it was saved, the browser got frozen and even the server did not want to receive the data set. [00:07:26](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h07m26s) Now ajax per field had been added, which makes this so much easier. That means that currently without clicking save and close, changes may be made to the permissional structure and immediately it will be stored in the data base. This apply to version 3.5 Joomla and later versions. There is still these areas 'Global', 'UiKit Settings', 'Encryption Settings', 'Folder Paths' that we also want to store. [00:07:58](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h07m58s) Possibly this implementation isn't that accurate, but here is 'Configure Options Only' as a permission. Perhaps it will work by taking a certain group, give them that Configure Options Only 'Access', and then log out of this user. Login to a user that is in that group. Then this permissional tab will not be visible. [00:08:26](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h08m26s) Only these 'Global', 'UiKit Settings', 'Encryption Settings', 'Folder Paths' settings which are in these tabs will be seen. Changes may be made to these and saved without any browser latency or overload. Whereas it is possible to come in and tweak the permissions in Global or Super Administrator accordingly. This can be changed in the manager area in the 'Select a new setting' column and it does a Ajax storing of the value in the database.[00:09:02](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h09m02s) There are Global Create, Delete, Edit, Edit state, Edit own, Edit created by, and Edit created date. [00:09:39](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h09m39s) Then there is the per View permission structure like Admin view, Custom admin view, the Dynamic get, and have different areas where permissions can be changed for groups.<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< The permissional structure in Component Builder is not that intense, but there are a lot of permission switches. With the latest Joomla 3.5 release, this permissional structure updating construct is made much easier. A problem had been experienced in the past where the data set of permissions was to big and when it was saved, the browser got frozen and even the server did not want to receive the data set. [00:07:26](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h07m26s) Now Ajax per field had been added, which makes this so much easier. That means that currently without clicking save and close, changes may be made to the permissional structure and immediately it will be stored in the data base. This apply to Joomla 3.5 and later versions. There is still these areas 'Global', 'UiKit Settings', 'Encryption Settings', 'Folder Paths' that we also want to store. [00:07:58](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h07m58s) Possibly this implementation isn't that accurate, but here is 'Configure Options Only' as a permission. Perhaps it will work by taking a certain group, give them that Configure Options Only 'Access', and then log out of this user. Login to a user that is in that group. Then this permissional tab will not be visible. [00:08:26](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h08m26s) Only these 'Global', 'UiKit Settings', 'Encryption Settings', 'Folder Paths' settings which are in these tabs will be seen. Changes may be made to these and saved without any browser latency or overload. Whereas it is possible to come in and tweak the permissions in Global or Super Administrator accordingly. This can be changed in the manager area in the 'Select a new setting' column and it does a Ajax storing of the value in the database.[00:09:02](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h09m02s) There are Global Create, Delete, Edit, Edit state, Edit own, Edit created by, and Edit created date. [00:09:39](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h09m39s) Then there is the per View permission structure like Admin view, Custom admin view, the Dynamic get, and have different areas where permissions can be changed for groups.
### Example Preacher Permissions ### Example Preacher Permissions
The same permission implementation options and [00:10:05](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h10m05s) structures are available to all components build by component builder, as you trip the switches for the fields as well as for your certain views. First we look at components, [00:10:30](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h10m30s) sermon distributor, in the admin views you have access control. This is not the only place of implementation. If you go to the admin views, and let's say we open preacher, [00:11:28](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h11m28s) you have the permissional structure for edit. Now if select view, it is going to use the view name. If you select core, you will fall back on the core edit and delete features corresponding. So if you use the word view.edit you will see in the permissional structure an edit [00:11:51](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h11m51s) switch with this views name preacher.edit. Where as you use the word core.edit you would only see edit or delete or create whatever one of these you will select. This in relation to its record means that it will be added to the record itself. You can tweak the edit structure. This is only the global setting or this is for both. That is party how you control some of the permissional switches we just looked at. The other area is in fields itself. [00:12:25](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h12m25s) [00:10:05](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h10m05s)The same permission implementation options and structures are available to all components build by Component Builder, as the switches are used for the fields as well as for certain views. In Components, [00:10:30](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h10m30s) Sermon Distributor, in the Admin Views is 'Access control'. There is another place of implementation. In Admin views, in 'Preacher', [00:11:28](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h11m28s) there is the permissional structure for 'edit'. If 'view' is selected , it is going to use the view name. If 'Core' is selected , it will fall back on the Core edit and delete features corresponding. If the word 'view.edit'is used an edit switch with this views name 'preacher.edit' will be seen in the permissional structure. [00:11:51](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h11m51s) If the word core.edit is used, only 'edit' or 'delete' or 'create' may be seen whatever one of these are selected. This in relation to each record means that it will be added to the record itself. The edit structure can be tweaked. This is only the global setting or this is for both. That is partly how some of the permissional switches are controlled. The other area is in fields itself. [00:12:25](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h12m25s)
### Field Permission Switch ### Field Permission Switch
You have here a permissional structure, where you can say this specific field, let say the preacher name, I want to control that permission 'who can edit it?'. Is what you would add a 'who edit?' button. Currently we are not yet implementing 'who can view?'. Since we were having problems with a tremendous overload of switches being added to the permissional structure. Since Joomla now has made this change we might possibly add that in. [00:12:58](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h12m58s) Then you can even have a view, 'who can view that field?'. Where as this is currently just who can edit it. This is how you get the fields permissional switch. For example: In the specific field, 'Preacher name', a 'who edit?' switch can be used to prevent anyone to edit that field. Currently a 'who can view?' function had not yet being implemented since there are problems with a tremendous overload of switches being added to the permissional structure. Since Joomla has made this change it might possibly be added. [00:12:58](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h12m58s) This is how you get a fields permissional switch.
* ### Example See Video * ### Example See Video
Let me give you this as an example. Let's make that one for now. Name, [00:13:23](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h13m23s) say that it must be permission, save and close. Here I have sermon distributor open. I will open it's options. Go to the permissional tab. Then scroll down. I see first here is the help documents. And here's preacher. Preacher has site access and access to preacher itself, and batch, create, [00:13:49](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h13m49s) dashboard add, dashboard list, delete, edit, edit created by, edit created date, edit own, edit state, edit version, export, import, submenu, and then it starts with series. So as you can see it doesn't show name here yet. What we'll do is now will go back to component builder, go to compiler, and we will select sermon distributor, and compile it. Once it's completed I'll just click on the install button to do a quick install. [00:14:27](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h14m27s) Now that is completed let's go back to the configuration and just refresh the page. I'll just click on the refresh here at the top. Now if we scroll down again it we'll get here(preacher edit name) we set, you will see it got a new field called preacher edit name. Now I can decide, can this group edit that name or is it denied or should it be inherited? So the permissional structure per field can be added in this way. I'm going to go back and revert that because I don't want that area to be monitored. Go back [00:15:07](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h15m07s) open preacher. Back to the fields. Say no. Save and close. Compiler. Select sermon distributor, compiling it. Then installing it. Going back refresh. And we will see that the field is gone. So it's no longer being controlled by the permission [00:15:41](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h15m41s) infrastructure. That is how you can tell which group is able to access which fields. Even in which views are accessible through the permissional structures. This is an amazing advantage of component builder in its ability to integrate the permissions, not only per view, but also [00:16:07](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h16m07s) per field in a view. Your normal control also related to a specific view. Not only that, it also adds these permissions to every item. So you could override an item, and say ok this item I don't want that group to actually access this field. This is one of the advantages that component builder has above other similar applications out there. Its ability to implement some of the most advanced concepts that are currently accessed or available at Joomla. [00:16:50](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h16m50s) That's a quick look at the global configuration options for component builder. [00:13:23](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h13m23s) For example: In the 'Fields' column click 'Name'. In the 'Permissions' column click the 'yes' switch', then save and close. Here is Sermon Distributor Dashboard open. Open it's options. Go to the permissional tab. Then scroll down. The Help Documents can be seen. Here is 'Preacher'.[00:13:49](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h13m49s) Preacher has site access and access to Preacher itself, and batch, create, dashboard add, dashboard list, delete, edit, edit created by, edit created date, edit own, edit state, edit version, export, import, submenu, and then it starts with series. So as it doesn't show 'name' here yet. Go back to Component Builder, go to Compiler, and select Sermon Distributor, and compile it. Once it's completed, click on the 'Install' button to do a quick install. [00:14:27](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h14m27s) If that is completed go back to the configuration and refresh the page. Click refresh at the top. Scroll down and there is a new field 'Preacher edit name'. It can be decided, can this group edit that name or is it denied or should it be inherited? So the permissional structure per field can be added in this way. Go back and revert that if you do not want that area to be monitored. [00:15:07](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h15m07s) Go back and open 'Preacher'. Back to the fields. Click 'no'. Save and close. Open Compiler. Select Sermon Distributor, compile it and install it. Go back to refresh. It can be seen that the field is gone. It's no longer being controlled by the permissional infrastructure.[00:15:41](https://www.youtube.com/watch?<<<<<<<<<<<<<<<<<<<<<<<<<<
v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h15m41s) That is how you can tell which group is able to access which fields. Even in which views are accessible through the permissional structures. This is an amazing advantage of component builder in its ability to integrate the permissions, not only per view, but also [00:16:07](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h16m07s) per field in a view. Your normal control also related to a specific view. Not only that, it also adds these permissions to every item. So you could override an item, and say ok this item I don't want that group to actually access this field. This is one of the advantages that component builder has above other similar applications out there. Its ability to implement some of the most advanced concepts that are currently accessed or available at Joomla. [00:16:50](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h16m50s) That's a quick look at the global configuration options for component builder.