Sugar Community Edition Installation and ... - SugarForge
Sugar Community Edition Installation and ... - SugarForge Sugar Community Edition Installation and ... - SugarForge
Chapter 2Administering Sugara. Open php.ini in your favorite text editor.b. Find the section named “Paths and Directories”.c. The pertinent entry is “extension_dir”.d. Keeping in mind that this file piggybacks on Window's $PATH$ variable,double-check the paths listed.e. Correct any errors - sometimes giving an absolute path solves hard-todiagnoseproblems, for example, full path listing from c:\... onwards.Necessary extensions are disabled.f. Open your php.ini file in a text editor.g. Find the section named “Dynamic Extensions”.h. Scroll to the Windows-specific list.i. Make sure that the necessary extensions are uncommented (no “;” precedingthe line). The bare minimum for Sugar Scheduler to run is to have php_curl,your database connector, typically php_mysql (for PHP5), and php_imap.j. Test the batch file again.Diagnostic ToolUse this option to capture system configuration for diagnostics and analysis. Thediagnostic tool pulls up system information and stores it in a zip file on the server fordownload. When you send a help request to Customer Support, you can attach the filebecause it summarizes all the basic information required to resolve the problem.To capture system configuration1. On the Diagnostic Tool page, click Execute Diagnostic to run the tool.2. To capture specific configuration information, click the Advanced link below theExecute Diagnostic button.36 Sugar Community Edition Installation and Administration Guide
SystemThe system displays a list of system configuration files. By default, the systemcaptures configuration information for all the selected files.The system performs the following actions of these files:SugarCRM Config.php - Copies the config.php file from the root directory afterreplacing the DB password with asterisk for security purposes.SugarCRM Custom directory - Copies the custom directory to a zip file toenable Customer Support to know what has been customized through the LayoutEditor.phpinfo() - Executes phpinfo and stores it in a file.MySQL - Configuration Table Dumps - copies a few tables from the databaseand replaces sensitive information with asterisk for security purposes.MySQL - All Tables Schema - writes the schema for all tables to an HTML file.MySQL - General Information - Pulls up some general information, likeMySQL version, character sets, etc.MD5 info - Runs md5 checks on all files in the sugar directory and compares itagainst a stock Sugar installation’s md5s. This enables Customer Support to learnwhich, if any, files have been manually customized.BeanList/BeanFiles files exist - If a custom module has been loaded, and theauthor did not define these references correctly, it can cause problems. This actionchecks all the references to ensure they are correct.SugarCRM Log file - copies the log file.Sugar schema output (VARDEFS) - copies the Sugar database schema.3. Deselect the ones you do not want to view and then click Execute Diagnostic.Sugar Community Edition Installation and Administration Guide37
- Page 1 and 2: Sugar Community EditionInstallation
- Page 3 and 4: ContentsPreface....................
- Page 5 and 6: PrefaceWelcome to Sugar, an open so
- Page 7 and 8: Preface• Customize the applicatio
- Page 9 and 10: Chapter 1Installing SugarThis chapt
- Page 11 and 12: Installation Prerequisites and Guid
- Page 13 and 14: Installation Process2. Unzip the Su
- Page 15 and 16: Installation ProcessIf you select M
- Page 17 and 18: Installation ProcessTo select an ex
- Page 19 and 20: Installation ProcessThe Installer d
- Page 21 and 22: Installation ProcessIf you select M
- Page 23 and 24: Installation Processcommunicate wit
- Page 25 and 26: Installation ProcessThe Installer d
- Page 27 and 28: Installation ProcessThe Perform Set
- Page 29 and 30: Chapter 2Administering SugarThis ch
- Page 31 and 32: Sugar NetworkSugar Support PortalUs
- Page 33 and 34: SystemTo configure the user interfa
- Page 35 and 36: SystemUse proxy server. If you want
- Page 37 and 38: SystemWhen you specify a logging le
- Page 39 and 40: Systemperformance job, and is not e
- Page 41 and 42: Systemthe location of the php.ini f
- Page 43: SystemTroubleshooting TipsLinux1. T
- Page 47 and 48: SystemTo backup Sugar configuration
- Page 49 and 50: SystemRebuild Config File: Rebuilds
- Page 51 and 52: SystemSystem Locale SettingsUse thi
- Page 53 and 54: SystemSugar Feed SettingsSelect thi
- Page 55 and 56: System2. If a connector’s URL has
- Page 57 and 58: UsersUsersUse this sub-panel to man
- Page 59 and 60: Usersonly user. If you do not selec
- Page 61 and 62: UsersCreating RolesWhen you create
- Page 63 and 64: UsersEdit: Edit records in the modu
- Page 65 and 66: EmailsTo configure email settings f
- Page 67 and 68: EmailsSelect Outlook Default Minimu
- Page 69 and 70: Emails5. Enter the mail account inf
- Page 71 and 72: EmailsNumber of Auto-responses. Use
- Page 73 and 74: EmailsIf both templates are selecte
- Page 75 and 76: EmailsUse the Scheduler to run nigh
- Page 77 and 78: Developer Tools2. Create a module u
- Page 79 and 80: Developer ToolsTo create a module1.
- Page 81 and 82: Developer ToolsYou do not need to d
- Page 83 and 84: Developer ToolsA list of existing d
- Page 85 and 86: Developer ToolsDropDown. Creates a
- Page 87 and 88: Developer ToolsYou can click and dr
- Page 89 and 90: Developer ToolsThe Edit View page i
- Page 91 and 92: Developer ToolsThe Preview page pro
- Page 93 and 94: Developer ToolsThe system displays
SystemThe system displays a list of system configuration files. By default, the systemcaptures configuration information for all the selected files.The system performs the following actions of these files:<strong>Sugar</strong>CRM Config.php - Copies the config.php file from the root directory afterreplacing the DB password with asterisk for security purposes.<strong>Sugar</strong>CRM Custom directory - Copies the custom directory to a zip file toenable Customer Support to know what has been customized through the LayoutEditor.phpinfo() - Executes phpinfo <strong>and</strong> stores it in a file.MySQL - Configuration Table Dumps - copies a few tables from the database<strong>and</strong> replaces sensitive information with asterisk for security purposes.MySQL - All Tables Schema - writes the schema for all tables to an HTML file.MySQL - General Information - Pulls up some general information, likeMySQL version, character sets, etc.MD5 info - Runs md5 checks on all files in the sugar directory <strong>and</strong> compares itagainst a stock <strong>Sugar</strong> installation’s md5s. This enables Customer Support to learnwhich, if any, files have been manually customized.BeanList/BeanFiles files exist - If a custom module has been loaded, <strong>and</strong> theauthor did not define these references correctly, it can cause problems. This actionchecks all the references to ensure they are correct.<strong>Sugar</strong>CRM Log file - copies the log file.<strong>Sugar</strong> schema output (VARDEFS) - copies the <strong>Sugar</strong> database schema.3. Deselect the ones you do not want to view <strong>and</strong> then click Execute Diagnostic.<strong>Sugar</strong> <strong>Community</strong> <strong>Edition</strong> <strong>Installation</strong> <strong>and</strong> Administration Guide37
Change language