Module Loader Restrictions

bsoremsugar —  August 14, 2009 — 7 Comments

Background 

SugarCRM’s hosting objective is to maintain the integrity of the standard Sugar functionality when we upgrade a customer instance, and limit any negative impact our upgrade has on the customer’s modifications.

Prior to Sugar 5.2.0j (Patch J), Module Loader did not have the ability to detect whether the changes being uploaded are deemed “upgrade-safe”. For example, if a customer were to upload a module that modified standard Sugar functionality, an upgrade of the instance (new patch, new release) could impact those modifications, resulting in a production problem for the customer.

Modifications using the rest of the Developer Tools section of Admin are considered upgrade-safe. This includes Studio, Module Builder, and Workflow.

New Access Controls

Sugar 5.2.0j (Patch J) introduced a new Module Loader feature, the Module Scanner.  Module Scanner grants system administrators the control they need to determine the precise set of actions that they’re willing to offer in their hosting environment.  This feature is available in all editions of Sugar, and is enforced in the Sugar On Demand environment.  Anyone else who is hosting Sugar products will have the opportunity to take advantage of this feature as well.

For more information on package scanner, please refer to the module loader section of the developer guide specific to your release:

Sugar Developer Guide 7.1.x

Sugar Developer Guide 6.7.x

Sugar Developer Guide 6.5.x

7 responses to Module Loader Restrictions

  1. 

    Great! It is my sincere hope that there can be made a push towards upgrade-safe customization and the reuse of each others modules within the SugarCRM community and I think this is very helpful indeed. Any idea when patch J will be out?

  2. 

    Great! It is my sincere hope that there can be made a push towards upgrade-safe customization and the reuse of each others modules within the SugarCRM community and I think this is very helpful indeed. Any idea when patch J will be out?

  3. 
    Blake Robertson January 22, 2011 at 7:36 pm

    What about like mysql_query()… can you access the database directly?

  4. 

    I found that naming a function ‘delete’ will cause a package to fail the package scan

  5. 

    How do I upload a certificate to communicate with a payment source. The file is cert.pem but .pem is blacklisted!

Trackbacks and Pingbacks:

  1. Define own REST API in SugarCRM module without using chdir(Resolved) - Tech Forum Network - July 1, 2012

    […] However the chdir command is banned by installations that use Module Loader restrictions: http://developers.sugarcrm.com/wordpress/2009/08/14/module-loader-restrictions/ […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s