Updated 022 Global Settings of Component Builder (markdown)
parent
709b0ec823
commit
6b89b04742
@ -33,14 +33,14 @@ Component Builder has a few places where it encrypts some of the data in the dat
|
|||||||
|
|
||||||
### Folder Paths
|
### Folder Paths
|
||||||
|
|
||||||
Currently there are two folder paths that can be used. It is the Backup folder path and the Git folder path.[00:05:42](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h05m42s) Please read related notation. It is suggested that no changes should be made to Custom folder path and the Compiler folder path at this stage. These fields were added because VDM envisioned the possibility that these folders have to be moved out of our web area of developing, since it is part of some security concerns, that this files and folders might be targeted. [00:06:14](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h06m14s) It has not been fully implemented all across the compiler infrastructure. Currently it's best to leave that folders the way they are by not adding any data in it. [00:06:50](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h06m50s) <<<<<<<<<<<<<<<<<<<,
|
Currently there are two folder paths that can be used. It is the Backup folder path and the Git folder path.[00:05:42](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h05m42s) Please read related notation. It is suggested that no changes should be made to Custom folder path and the Compiler folder path at this stage. These fields were added because VDM envisioned the possibility that these folders have to be moved out of our web area of developing, since it is part of some security concerns that this files and folders might be targeted. [00:06:14](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h06m14s) It has not been fully implemented all across the compiler infrastructure. Currently it's best to leave that folders the way they are by not adding any data in it. [00:06:50](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h06m50s)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Permissions
|
### Permissions
|
||||||
|
|
||||||
Next up we can look at the permissions. Now the permissional structure in component builder is not that intense, but as you can see 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. In the past we had a problem were the data set of your permissions is to big, that when you save it, it just freezes up your browser and even the server doesn't want to receive the data set it's to big. [00:07:26](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h07m26s) Now they have added ajax per field. Which makes this so much easier. That means that currently without clicking save and close, you can make changes to the permissional structure and immediately will be stored to the data base. That's from version 3.5 Joomla. We still have these areas(Global UiKit Settings, Encryption Settings, Folder Paths) that we also want to store. So what I have thought might work, [00:07:58](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h07m58s) possibly my implementation isn't that accurate, but you have here configurations only as a permission. I would say take a certain group, give them that configuration only access, and then log out of this user, login to a user that is in that group. Then this permissional tab won't show. [00:08:26](https://www.youtube.com/watch?v=LA2WDi8G79E&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h08m26s) They will only see these(Global UiKit Settings, Encryption Settings, Folder Paths) settings which are in these tabs. They can make changes to these and save them without any browser latency or overload. Where as you can come in and you can just tweak the permissions when you are in the global or super administrator build. So you can come in here and you can tweak the permissions accordingly. So as you saw previously, when I was here in the manager area, I could just change this 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) Which is really smart. I am very grateful that they've done that search for the main reason that this set of the permissions became so huge, that I had in some places had to do server adjustments on some of my components to ensure that the user could still save and change the permissions. You have your 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 you get the per view permission structure. Here is the admin view then the custom admin view, the dynamic get, and they all have their own different areas that you can change permissions for groups to be able to do this or that.
|
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. So you can come in here and you can tweak the permissions accordingly. So as you saw previously, when I was here in the manager area, I could just change this 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) Which is really smart. I am very grateful that they've done that search for the main reason that this set of the permissions became so huge, that I had in some places had to do server adjustments on some of my components to ensure that the user could still save and change the permissions. You have your 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 you get the per view permission structure. Here is the admin view then the custom admin view, the dynamic get, and they all have their own different areas that you can change permissions for groups to be able to do this or that.
|
||||||
|
|
||||||
### Example Preacher Permissions
|
### Example Preacher Permissions
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user