t - Profile

Non-static method SugarView::getBreadCrumbSymbol()

Support September 24th, 2024 @ 12:25 pm

corrected code is as follows: $module_title = join((new SugarView())->getBreadCrumbSymbol(),$new_params);

View Comment

Support July 8th, 2024 @ 3:18 pm

I have added the following method to both

custom/VIDynamicPanels/VIDynamicPanelsAllModuleFields.php

and

custom/VIDynamicPanels/VIDynamicPanelsAllModulePanels.php

        function getViewPanels($view, $module)
        {
                require_once &#039;ModuleInstall/PackageManager/PackageManager.php&#039;;
                $lView = strtolower($view);
                $secsuiteproInstalled = false;
                $pm = new PackageManager();
                $installedModulesInfo = $pm->getinstalledPackages();
                foreach ($installedModulesInfo as $installedModuleInfo) {
                        if ($installedModuleInfo[&#039;name&#039;] === "SecuritySuite - Enhanced, Professional, and Enterprise") {
                                $secsuiteproInstalled = true;
                                break;
                        }
                }

                if ($secsuiteproInstalled) {
                        $moduleDirectory = BeanFactory::newBean($module)->module_dir;
//                      $moduleDirectory = (new $module())->module_dir;
                        include "custom/modules/$moduleDirectory/metadata/$securityGroupID/{$lView}defs.php";
                        $editViewPanelArray = $viewdefs[$module][$view]["panels"];
                        $panelArray = $editViewPanelArray;
                        return $panelArray;
                } else {
                        $view_array = ParserFactory::getParser($lView, $module);
                        $panelArray = $view_array->_viewdefs[&#039;panels&#039;];
                        return $panelArray;
                }
        }

This function replaces the parts of the code which gets the panels metadata. it will check if the full version of security suite is installed. if it is then it will use an alternate method to get the view metadata, otherwise it will use the standard method.

I may need to tweak this slightly after battle testing. not sure if I need to do extra handling for default layouts.

View Comment

Compatibility with ParserFactory

Support July 8th, 2024 @ 10:13 am

delimiter*

View Comment

Plugin doesn't select correct layout

Support July 8th, 2024 @ 10:12 am

delimiter*

View Comment

Compatibility with ParserFactory

Support July 8th, 2024 @ 10:12 am

my proposal is to expand the first parameter $view,

this can be both the group id and the view name a colon, pipe, or similar symbol can be used as a delmeter,

and could be called like so:

$view = "2d1f3312-6ca8-1fe6-dc2d-2a645d3d2c23|editview";
$module = "Contacts";
$metadata = ParserFactory::getParser($view, $module);

View Comment

Plugin doesn't select correct layout

Support July 8th, 2024 @ 10:03 am

So far I have made modifications to the JavaScript to send the id of the selected Security Group during the calls to the backend. if no security group is selected it will send null for this parameter.

The PHP code will then be able to use this id to select the correct layout for the view and return the panels and fields within it. first the following needs to be addressed.

the function

function getEditDetailViewFields($view,$module)

makes use of the ParserFactory. SecuritySuite does not override the ParserFactory to make it possible to select the correct layout for a view.

I have reached out to SecurtiySuite to see if they have plans to override the ParserFactory. For the moment until this is addressed, I'll use the ParserFactory if no security group id is returned or if the CRM system is not using the full version of Security Suite otherwise, I will use another method for obtaining a views metadata,

View Comment

Plugin doesn't select correct layout

Support July 4th, 2024 @ 1:27 pm

I am already aware that you are not responsible for any changes I make that break the plugin these changes are for your benefit if you wish to include them with your plugin

View Comment

Plugin doesn't select correct layout

Support July 4th, 2024 @ 1:25 pm

Hi,

Within the CRM it is possible to create different layouts for different security groups containing different fields. Currently when using dynamic panels no matter which security group is selected, the UI will always return the fields and panels that are defined in the default layout.

We would like the list of fields and panels from the layout that would be active with the selected security group.

Screenshot from 2024-07-04 14-20-56.png

View Comment

Updating to Version 15 without losing current settings

Support July 4th, 2024 @ 9:26 am

I would also like to know the correct official way to do this. uninstalling the plugin deletes the relevant tables even when "do not remove tables" is selected.

the only way I've been able to do it successfully is to backup the data in the tables first. and then insert the records after installing the new version

View Comment

Relationship::get_other_module cannot be called statically

Support November 8th, 2023 @ 2:09 pm

I've viewed modules/Relationship/Relationship.php from the SuiteCRM 7.14.0 zip and Relationship::get_other_module is not supposed to be a static method.

View Comment

Installation Guide

Documentation September 4th, 2023 @ 9:55 am

I'd reccomdend when updating the CRM system, 1. check to make sure a version of security suite exists for the version of SuiteCRM you are updating to. 2. uninstall SecuritySuite (make sure not to delete tables), 3. install the SuiteCRM update 4. delete the previous SecuritySuite module 5. upload and install the new SecuritySuite module

6 (optional). if using the bitnami docker images. try to run a couple of Suitecrm versions older than your actual SuiteCRM version. Security Suite as well as SuiteCRM does not work with the PHP handler versions set on the latest versions of these images.

View Comment

Single Sign-on

Support May 26th, 2023 @ 9:15 am

Hi

Thanks for the quick reply. Do you have any plans to support this in the future?

Regards,

View Comment

AOR report link to file fails

Support April 5th, 2023 @ 10:55 am

Fix has been made by end user. AOR_Reports that uses aow_utils for generating field value html from field templates sets the record_id as a paramer when executing the smarty template.

within the template the variable is reset to a variable that doesn't exist from the context of a report but would normally if the template was executed from the original module view (grabs it from the $fields variable)

wrapping the variable declaration for record_id with a check to see if it exists within custom/include/SugarFields/Fields/Multiupload/DetailView.tpl fixes the problem

{assign var="record_id" value=$fields.id.value} to {if !isset($record_id)} {assign var="record_id" value=$fields.id.value} {/if}

View Comment

#4742 - Non-static method SugarOutfitters_API::get_default_payload() cannot be called statically

Support March 1st, 2023 @ 2:19 pm

get_default_payload is defined as a normal method. defining get_default_payload as a static method solves the issue. and allows for the outfitterscontroller action to complete

View Comment

500 crash. Non-static method Relationship::get_other_module() cannot be called statically

Support February 23rd, 2023 @ 2:44 pm

Hi Thankyou eggsurplus for your reply changing error_reporting configuration wouldn't prevent a PHP application from crashing due to a fatal error. Your suggestion would only hide PHP error messages.

View Comment

500 crash. Non-static method Relationship::get_other_module() cannot be called statically

Support February 23rd, 2023 @ 2:20 pm

replacing $rel_module = Relationship::get_other_module($_REQUEST['relate_to'], $focus_module_dir, $focus->db); with $rel_module = (new Relationship())->get_other_module($_REQUEST['relate_to'], $focus_module_dir, $focus->db); solves the problem