Control what your users can access and save time, money, and frustrations. Lock down sensitive data in SugarCRM or SuiteCRM to specific groups or teams. Supports unlimited assigned users, unlimited group assignments to records, custom layouts for each group, login/sudo capabilities and much more.
#3684 - Additional Users and Security Group fields automatically added to layouts
When editing a module's layout in studio and clicking on save and deploy, the fields for additional users and security group are automatically added to the view, even though I have not added these and don't want these fields shown to the end users.
-
"GREAT!!! add on superior support works well" - jpowers
Read More Reviews
- Most Recent Love from Users
kacsoristvan- damien8105
- anri
- Administrador
- Stefano1
- einkauf2
5 years ago
Do you happen to have any other layouts that have these fields already on the view?
What version of SugarCRM or SuiteCRM are you on? Which version of SecuritySuite is installed where you are seeing this behavior?
These questions will help me pin down the possible causes. It shouldn't be doing that by default.
5 years ago
No other layouts for the module. Upon clicking on save and deploy these two fields get automatically added. If I remove these fields and tray again, they are once again added.
SuiteCRM 7.10.4, SecuritySuite 3.1.9
5 years ago
Thanks. I've seen something like this happen with some other fields in the past. Can you make sure that the /custom/modules/YOURMODULE/metadata is writable by Apache? What is likely happening here is that your Studio working copy has the change you need without the fields on it. When it deploys it fails to do so properly which then causes Studio to reload the original layout with the fields still on it.
5 years ago
The folder is owned by Apache and the permissions are 775. I'm able to make changes to the layout and these work correctly, with the addition of these two fields being added. in the custom/modules/Contacts/metadata folder these two fields have been added to the views in that folder.
5 years ago
Are your other changes in Studio taking hold? Just trying to rule out permissions here as it's the most common problem even if you can directly edit those files. File ownership related issues often comes into play with Studio deploys.
I'm not able to replicate the issue on the same environment, but like I mentioned, I've seen this happen with other fields unrelated to SecuritySuite before. I'll keep digging into other possibilities.
5 years ago
Yes other changes in Studio are taking hold.
I've just set up a new VPS with LAMP on Ubuntu 16.04. Have installed SuiteCRM 7.10.4 and SecuritySuite 3.1.9, nothing else has been changed. All files have had their permissions set as per the SuiteCRM documentation. I can go into Studio, go to the default detail view for the Contacts module, click on Save and Deploy and these two additional fields are then added to the layout.
5 years ago
I just ran into the same issue. I'll follow up with a solution here likely within a day.
5 years ago
To solve this issue go to Admin->Repair and run the following three in order:
If you then go back into Studio and reload that view that was having problems you should no longer see those fields added.
5 years ago
I ran the three tasks in order and when I went back into Studio those fields were no longer there. However, when I clicked on Save & Deploy, they once again came back.
5 years ago
Well this is weird. I'll have to get back to you on this tomorrow.
5 years ago
Found the culprit and working on a new package for you. There is a check in Studio to see if any SuiteCRM field is required and if so then add it to the layout automatically. The check in SuiteCRM is not using a strict comparison as it should and it only happens when it returns from the Save & Deploy. It doesn't do that check if you leave that Studio view and come back to it. I'm patching that core SuiteCRM code and including it in the latest 3.1.10 package that will be available shortly today.
5 years ago
There is a new 3.1.10 package available to download on your Purchases page. Install on top of the existing install (do NOT uninstall prior) and then run a Quick Repair & Rebuild.
This fixes the issue where the 2 fields kept showing up on the layout in Studio after doing a Save & Deploy.
Let me know how that goes.
5 years ago
Fantastic thank you. This now works as expected.
5 years ago
Awesome! Thanks for reaching out. That was definitely a weird one, but glad it is worked out now.