
-
Display Nameeggsurplus
-
Website
-
Member SinceAugust 20th, 2012
-
Last SeenFebruary 23rd, 2021
-
Support February 8th, 2021 @ 4:10 pm
Confirmed via email that the CRM is back up and running.
View Comment
-
Support February 7th, 2021 @ 9:02 pm
Hi Slaven,
I just replied to your email, but wanted to reply here as well as it may also help someone else trying to upgrade their SuiteCRM/SecuritySuite.
The SuiteCRM uninstaller is spotty at best as it depends on file permissions/ownership to be right on the server. Always install SecuritySuite WITHOUT uninstalling the previous SecuritySuite first.
Here is how you can get back up and running:
0) Backup your CRM files
1) Grab a clean zip of SuiteCRM 7.11.18 and open it
2) Copy these directories back into your CRM:/data
/include
/modules
/soap
/themes3) Log into your CRM and do a Quick Repair & Rebuild
4) Now install the latest version of SecuritySuite
5) Run these 3 steps after installing SecuritySuite:- Quick Repair & Rebuild (execute generated SQL)
- Rebuild Relationships
- Repair Roles
You should be good at this point.
View Comment
-
Support January 7th, 2021 @ 4:56 am
Additional Assigned Users is now supported in the Quick Create forms with the latest 3.1.24 release which can be downloaded from your Orders at https://www.sugaroutfitters.com/orders.
View Comment
-
Support December 29th, 2020 @ 3:28 pm
A few questions to help pinpoint this issue:
What other add-ons do you have currently installed in Module Loader?
Do you have SuiteCRM or SugarCRM installed and which version?
Do you have a theme installed and if so, which theme?
Thanks!
View Comment
-
Support December 28th, 2020 @ 9:03 pm
Hi Lee,
Be sure to run the following steps after installing SecuritySuite or upon any upgrades. This will resolve the not being able to create records issue:
- Admin -> Repair -> Quick Repair & Rebuild (execute any generated SQL)
- Admin -> Repair -> Rebuild Relationships
- Admin -> Repair -> Repair Roles
You should be good to go after that.
View Comment
-
Documentation November 5th, 2020 @ 4:35 am
Always happy to help. I replied on that community thread and via email on how you can support 4 layers or 100 layers. It's all about creating groups/teams at the lowest level that you functionally need. Hopefully the example I provided based on your screenshot of your structure helps.
View Comment
-
Documentation November 5th, 2020 @ 3:09 am
Hello. I responded to your scenario there. This is also a nice starting point for figuring out how best to implement SecuritySuite for any scenario: https://www.sugaroutfitters.com/docs/securitysuite/example-of-a-typical-setup
View Comment
-
Support October 29th, 2020 @ 1:57 am
A new 3.1.22 version is now available for download that fixes this issue. Thanks again for reporting this!
View Comment
-
Support October 28th, 2020 @ 2:01 pm
Here is a temporary, quick fix to get your dashlets back up. This was introduced in 3.1.20 and assumes that a certain variable is set. It's always interesting to see something work well in most every where with SugarCRM/SuiteCRM and then have a single case that things break down. I apologize for the inconveniences heree.
Edit /include/generic/SugarWidgets/SugarWidgetFieldname.php
Look for the code block around line 244 that starts with: /* BEGIN - SECURITY GROUPS - additional-users */
Comment out the whole code block and save. Your dashlet filters will now work. A permanent fix will be available soon.
Thank you!
View Comment
-
Support October 28th, 2020 @ 1:48 pm
Thanks. This is exactly what i needed. Digging into it and I'll report back here shortly.
View Comment
-
Support October 27th, 2020 @ 2:07 pm
Which edition of SecuritySuite are you currently on?
View Comment
-
Support October 27th, 2020 @ 2:06 pm
Hello,
This functionality still works in 3.1.21. Can you try the following, please?
- Run a Quick Repair & Rebuild and execute any SQL generated
- Run Rebuild Relationships
- Run Repair Roles
Also try clearing the browser cache. See if this works. If not, check your sugarcrm.log (or suitecrm.log) on the server and see what errors may be showing at the end of it. There may be a database error.
If not, which module is this dashlet for?
View Comment
-
Support September 21st, 2020 @ 5:14 pm
Thanks for giving that a shot. This query is a dynamically created statement that has a lot of variables/moving parts involved so unfortunately it isn't just a missing bit of code. For some reason SuiteCRM is having trouble creating that statement in just your instance. I will try to recreate the issue locally and find some possible reasons for this to happen. Then we will be able to provide some alternative solutions.
Give me a couple of days to work through this one.
Thanks!
View Comment
-
Support September 21st, 2020 @ 4:15 pm
Usually it's a relationship that needs a little help getting squared away after install. Can you please run these 3 steps from the Admin->Repair options and see if that resolves the issue for you?
- Quick Repair & Rebuild
- Rebuild Relationships
- Repair Roles
Let me know if anything changes for you after running all 3. If not, if you could list any other add-ons you have installed and/or code-level customizations made to the Calls module that will help pinpoint how this may be happening on your instance.
Thanks!
View Comment
-
Support September 10th, 2020 @ 3:30 pm
Hi Slaven,
What it sounds like you might need in this case is the Strict Rights option: https://www.sugaroutfitters.com/docs/securitysuite/options.
This will mean that the roles from the group assigned to a record will take precedence. You may also want to consider turning off the Additive Rights setting if you want the most restrictive rights to take precedence, but that doesn't sound like that is wanted, in general.
View Comment
-
Support July 10th, 2020 @ 7:04 pm
I doubt it's a race condition. I just don't think it's getting to the AssignGroups logic hook like a normal process does. This seems very contained to your instance, relating to how things work in your heavily customized version. What I suggest is doing some dirty debugging to find why it isn't getting to the logic hook like it does normally.
View Comment
-
-
Support July 9th, 2020 @ 3:30 pm
relate_to and relate_id are the keys.
You'll see a section similar to below in that inherit function. Put this above the others that look like this:
if((empty($parent_type) || empty($parent_id)) && isset($_REQUEST['relate_to']) && isset($_REQUEST['relate_id'])) { $parent_type = $_REQUEST['relate_to']; $parent_id = $_REQUEST['relate_id']; }
This is not upgrade-safe so be sure to document this somewhere so that you can include it back in after updating your CRM and/or SecuritySuite.
Best of luck!
View Comment
-
Support July 9th, 2020 @ 3:07 pm
The flex relate defines who the parent of the Case is?
I don't have an exact answer, but I suggest outputting the REQUEST var in SecurityGroup.php->inherit_parent() to see what variables are set. Then alter the if statement to get into the inherit logic to support your flex relate.
$GLOBALS['log']->fatal(print_r($_REQUEST,true));
Save a new case and see what is in sugarcrm.log
View Comment
-
Support July 8th, 2020 @ 5:43 pm
Sounds like a tough one! I suggest working backwards within the files I mentioned earlier and debug why it isn't getting into the logic to trigger the popup. My personal favorite technique is to just add fatal() debug statements along with variable values to see why it is working in general and not for specific cases for you. My guess is that the after_save hook isn't being called due to an exit() call in some other hook.
View Comment
eggsurplus has not rated any add-ons.
eggsurplus has not verified any add-ons.
eggsurplus has not created any Wanted Add-ons.
Keep up to date on the latest additions