email error clean install, new host

AnneR · 13 October 2015 01:18

I clean install from my host - version 7.3.1
login with no problem
start running through the initial wizard
upload logo with no problem
get to email, try to set up using gmail,
1st time with smtp authentication, didn’t receive an email and got a whole heap of errors
2nd time with gmail without smtp authentication, did receive a test email but still received errors all over the screen
3rd time with no email information entered, didn’t try to send a test email just tried to move on and received a whole load of errors
The errors are:
Strict Standards: Declaration of SugarEmailAddress::save() should be compatible with SugarBean::save($check_notify = false) in /home/fourfive/public_html/suitecrm/include/SugarEmailAddress/SugarEmailAddress.php on line 1113

Strict Standards: Declaration of Person::create_export_query() should be compatible with SugarBean::create_export_query($order_by, $where) in /home/fourfive/public_html/suitecrm/include/SugarObjects/templates/person/Person.php on line 44

Strict Standards: Declaration of User::retrieve() should be compatible with Person::retrieve($id = -1, $encode = true, $deleted = true) in /home/fourfive/public_html/suitecrm/modules/Users/User.php on line 44

Strict Standards: Declaration of User::create_export_query() should be compatible with Person::create_export_query(&$order_by, &$where, $relate_link_join = ‘’) in /home/fourfive/public_html/suitecrm/modules/Users/User.php on line 44

Strict Standards: Declaration of User::create_new_list_query() should be compatible with SugarBean::create_new_list_query($order_by, $where, $filter = Array, $params = Array, $show_deleted = 0, $join_type = ‘’, $return_array = false, $parentbean = NULL, $singleSelect = false, $ifListForExport = false) in /home/fourfive/public_html/suitecrm/modules/Users/User.php on line 44

Strict Standards: Declaration of User::list_view_parse_additional_sections() should be compatible with SugarBean::list_view_parse_additional_sections(&$list_form) in /home/fourfive/public_html/suitecrm/modules/Users/User.php on line 44

Strict Standards: Declaration of Currency::retrieve() should be compatible with SugarBean::retrieve($id = -1, $encode = true, $deleted = true) in /home/fourfive/public_html/suitecrm/modules/Currencies/Currency.php on line 239

Strict Standards: Non-static method UploadStream::register() should not be called statically in /home/fourfive/public_html/suitecrm/include/entryPoint.php on line 184

Strict Standards: Non-static method SugarConfig::getInstance() should not be called statically, assuming $this from incompatible context in /home/fourfive/public_html/suitecrm/include/SugarLogger/LoggerManager.php on line 76

Strict Standards: Non-static method SugarConfig::getInstance() should not be called statically, assuming $this from incompatible context in /home/fourfive/public_html/suitecrm/include/SugarLogger/SugarLogger.php on line 121

Strict Standards: Declaration of MysqlManager::checkQuery() should be compatible with DBManager::checkQuery($sql, $object_name = false) in /home/fourfive/public_html/suitecrm/include/database/MysqlManager.php on line 1508

Strict Standards: Non-static method LogicHook::initialize() should not be called statically in /home/fourfive/public_html/suitecrm/include/entryPoint.php on line 239

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /home/fourfive/public_html/suitecrm/include/SugarEmailAddress/SugarEmailAddress.php:1113) in /home/fourfive/public_html/suitecrm/include/MVC/SugarApplication.php on line 602

Strict Standards: Non-static method LogicHook::initialize() should not be called statically, assuming $this from incompatible context in /home/fourfive/public_html/suitecrm/include/MVC/SugarApplication.php on line 619

Warning: Cannot modify header information - headers already sent by (output started at /home/fourfive/public_html/suitecrm/include/SugarEmailAddress/SugarEmailAddress.php:1113) in /home/fourfive/public_html/suitecrm/include/utils.php on line 2698

Strict Standards: Non-static method ControllerFactory::getController() should not be called statically, assuming $this from incompatible context in /home/fourfive/public_html/suitecrm/include/MVC/SugarApplication.php on line 74

Strict Standards: Non-static method ACLController::filterModuleList() should not be called statically, assuming $this from incompatible context in /home/fourfive/public_html/suitecrm/include/MVC/SugarApplication.php on line 179

Strict Standards: Declaration of ACLAction::toArray() should be compatible with SugarBean::toArray($dbOnly = false, $stringOnly = false, $upperKeys = false) in /home/fourfive/public_html/suitecrm/modules/ACLActions/ACLAction.php on line 643

Strict Standards: Non-static method ACLController::checkModuleAllowed() should not be called statically, assuming $this from incompatible context in /home/fourfive/public_html/suitecrm/modules/ACL/ACLController.php on line 123

Strict Standards: Non-static method ACLController::filterModuleList() should not be called statically, assuming $this from incompatible context in /home/fourfive/public_html/suitecrm/modules/MySettings/TabController.php on line 88

Strict Standards: Non-static method ACLController::checkModuleAllowed() should not be called statically, assuming $this from incompatible context in /home/fourfive/public_html/suitecrm/modules/ACL/ACLController.php on line 123

Strict Standards: Non-static method SugarConfig::getInstance() should not be called statically in /home/fourfive/public_html/suitecrm/include/utils/sugar_file_utils.php on line 369

Strict Standards: Non-static method LanguageManager::loadModuleLanguage() should not be called statically in /home/fourfive/public_html/suitecrm/include/utils.php on line 1100

Strict Standards: Non-static method ViewFactory::loadView() should not be called statically, assuming $this from incompatible context in /home/fourfive/public_html/suitecrm/include/MVC/Controller/SugarController.php on line 339

Strict Standards: Non-static method ViewFactory::_buildFromFile() should not be called statically, assuming $this from incompatible context in /home/fourfive/public_html/suitecrm/include/MVC/View/ViewFactory.php on line 88

Strict Standards: Non-static method ViewFactory::_buildClass() should not be called statically, assuming $this from incompatible context in /home/fourfive/public_html/suitecrm/include/MVC/View/ViewFactory.php on line 223

Strict Standards: Non-static method ViewFactory::_loadConfig() should not be called statically, assuming $this from incompatible context in /home/fourfive/public_html/suitecrm/include/MVC/View/ViewFactory.php on line 95

Strict Standards: Non-static method SecurityGroup::groupHasAccess() should not be called statically, assuming $this from incompatible context in /home/fourfive/public_html/suitecrm/data/SugarBean.php on line 5494

Strict Standards: Non-static method LogicHook::initialize() should not be called statically, assuming $this from incompatible context in /home/fourfive/public_html/suitecrm/include/MVC/View/SugarView.php on line 120

Strict Standards: Non-static method LanguageManager::loadModuleLanguage() should not be called statically in /home/fourfive/public_html/suitecrm/include/utils.php on line 1100
Strict Standards: Non-static method SugarConfig::getInstance() should not be called statically, assuming $this from incompatible context in /home/fourfive/public_html/suitecrm/include/MVC/View/SugarView.php on line 915

Strict Standards: Non-static method LogicHook::initialize() should not be called statically in /home/fourfive/public_html/suitecrm/include/utils.php on line 3017

Strict Standards: Non-static method Tracker::logPage() should not be called statically in /home/fourfive/public_html/suitecrm/include/utils.php on line 3028

Strict Standards: Non-static method SugarConfig::getInstance() should not be called statically in /home/fourfive/public_html/suitecrm/include/utils/sugar_file_utils.php on line 369

A test system prior to 7.1 I managed to get rid of the errors (for demo purposes) by not entering any email information. Now I need email to work.

John · 13 October 2015 08:37

Hi,
You should disable strict standards warnings from displaying on your instance.
You should be able to do this with the commands:

ini_set('display_errors', '0');     
error_reporting(E_ALL | E_STRICT);

You can place these in your index.php, or your php.ini file. Whichever you prefer.

AnneR · 14 October 2015 00:14

Thank you John, that got rid of the messages.

Next step was to get the logo in there, because I’ve now gone past the initial wizard I have been trying to upload via system settings. When I select the file and click upload I end up with a spinning circle. I have searched the forums but can’t seem to find a clear answer whether this is due to permissions or not and if so what exactly to do about it? In the mean-time I renamed the logo to company_logo.png and moved it to themes/default/images/ to get it to work.

I have adjusted the security settings on the required directories and files, however I note there are still a whole lot of (sub) files and some directories that still have a setting of 0644. For example, cache directory is 0775, then directory dashlets is 0755, however the file in dashlets - dashlet.php is 0644. I’m not sure if this is correct or not. Is it a case of all files must be 0755 with the directories and files noted in the install notes being 0775?

I’m now trying to change the colors of the theme, two issues here

clking the theme name, changing colours and saving has no effect.
Suite 7 is checked as the enabled theme, with Suite R as the default theme. I can uncheck Suite 7 to disable it, but I can’t check Suite R to enable, the checkbox is greyed out.
Any changes and subsequent saves I make in this area have no effect.

Please assist.

John · 14 October 2015 12:47

Hi,

In regards to permissions, it’d probably be worth re-setting your permissions now that you have installed.
We find a suitable permissions level is:

sudo chmod -R 755 .
sudo chmod -R 775 cache custom modules themes data upload config_override.php

And run a Quick Repair & Rebuild from the Admin > Repair menu.

Also, if you navigate to your config.php file, you can find inside an array called “default_permissions”
What values do you have for dir_mode, file_mode, user and group?

Resolving your permissions issues could potentially resolve your Themes issues too, but just to be sure, What verison of SuiteCRM are you running?

AnneR · 14 October 2015 20:47

sudo chmod -R 755 .
sudo chmod -R 775 cache custom modules themes data upload config_override.php

I’m using a shared hosting service and aren’t obviously able to see where the above might be used. Currently have a ticket in with my host on this.

dir_mode => 1517
file_mode => 420
user => ‘’
group => ‘’

CRM version 7.3.1

AnneR · 14 October 2015 22:02

I’ve had a response from my host -

'You have set the permissions correctly as they requested however they are not required and are generally unsecure on a shared hosting platform.

What you have done generally gives other users on our server access to your files.’

From what he can see the permissions are set correctly. I am concerned that other users on the shared server have access to the files, how do I clos this access off?

I have run a quick repair (again) and still have the following issues:

unable to upload a logo
unable to change colours on themes

John · 15 October 2015 08:56

Hi,

If you are worried about security, then you are free to change the permissions to something that will be more suitable for you.
Maybe something like 664 for all files? I’m not sure how compatible that will be with the CRM, however.

You should be able to upload a logo through Admin > System Settings as long as it fits these conditions:
The image file format is either .png or .jpg,
The maximum height is 17px, and the maximum width is 450px,
There are no spaces in the filename.

Which theme are you trying to change the colours of? If I change colours by going through Admin > Themes > {Then choose a theme}
Changing any of the Theme’s colours works fine for me on the SuiteR theme, but some can’t be changed on the Suite7 theme.

AnneR · 15 October 2015 21:04

I scaled the logo down to H: 17px x W: 55px. When uploading it displays the logo as $mod_strings_LBL_LOGO on the system settings screen, however once saved, exited and logging back in does show the logo on the front login panel and then displays it correctly in system settings. Thank you

I have tried changing the colours in the following areas on both themes, each time I have saved both the individual screen where the colours are changed and the screen that lists the themes, then logged out and logged back in.

Top menu base colour
Menu hover colour
Drop down link colour
Action menu colour
Button hover colour
Page link colour

Nothing has changed, I’d like to be able to change it from blue to something else (client dependent).

John · 16 October 2015 11:15

Hi,

There is an issue logged on our github that states "Theme colour changes only save pressing ‘Enter’ "
If you try to save your changes by pressing enter, instead of clicking the “Save” button, do the colour changes save?

If this does not resolve the issue, there are some fixes proposed for Theme Colour Changes:
https://github.com/salesagility/SuiteCRM/commit/10db86f781bcda801a588a0a80a5302759a6082f
https://github.com/salesagility/SuiteCRM/commit/2e9980ed25a489f5c644b220ced07a80456c3629

If you apply these, do a Repair & Rebuild from the Admin > Repair Menu and clear your Browser’s Cache and try to change colours again.

AnneR · 26 October 2015 00:10

Hi John, enter does nothing, doesn’t save.

Is there an eta of when the bug fix will filter through to an available version of SuiteCRM?

AnneR · 26 October 2015 01:27

I have tested both changes from github and neither have made any difference. attached is an outline and screenshots of the testing.

Any other ideas?

John · 26 October 2015 10:02

Hi,

I’m unsure as to why your issue is even occurring, but we have recently released SuiteCRM v7.3.2
This was a Bug-fix release that included a lot of Studio fixes, as well as the two fixes I linked earlier.
It may be worth upgrading to this version, or even installing it fresh, setting your instance’s permissions again, and checking if this issue still occurs as this seems like a local issue.

AnneR · 26 October 2015 20:58

1st try, upgrading. The upgrade occurred with no errors, tried testing using the same process as yesterday, still no change.
2nd try, uninstalled and installed version 7.3.2 (via softalicious), tested using same process, still no change to colours.

The install process went fine, I uploaded the modified php.ini file before I ran the install wizard frontend. The email works, no errors, looked like the logo uploaded ok (but it didnt’ - I had a dash in the file name, once removed it uploaded fine via system settings).

Am I expecting the right thing when I change the theme colours. The 2nd row Top Menu Base Colour, I am expecting this to be the background colour on the top menu bar, is this correct?

AnneR · 26 October 2015 21:10

I don’t seem to be able to upload the .rtf file with testing results, nor edit posts.

John · 27 October 2015 09:29

Would you be able to post a screenshot specifying exactly which part of the theme you would like to change the colour of?
There are some parts of the Suite7 theme that cannot be changed through the colour selector, so there may be some in the SuiteR theme too.
If you specifiy the exact section(s), it may be possible to edit its colour by editing the CSS file, if you are unable to edit it through the Colour Picker.

AnneR · 27 October 2015 22:06

John · 29 October 2015 10:00

Hi,
You should be able to change most of these.

In the Theme Colour changer page:
The Top banner is titled: Top menu base colour
The Text on the top banner is titled; Menu Link colour
The Text on the top of Dashlets should be: Page Link Colour
The Icons are: Icon Colour
Buttons are: Button Colour

However, you won’t be able to change Specific buttons, specific Text or the Background Page colour without editing the Theme’s CSS files.

If you are unable to edit any of the listed above, it may be worth checking your config_override.php file

If there are any lines like:
[i]$sugar_config[ theme_settings ][ SuiteR ][ button ] = ‘’;
$sugar_config[ theme_settings ][ SuiteR ][ page_header ] = ‘’;
$sugar_config[ theme_settings ]{ SuiteR ][ page_link ] = ‘’;

[/i]or[i]

$sugar_config[colourselector]
[/i]

Remove them, do a repair & Rebuild and try to edit the theme again.

If lines like those don’t exist, we can try adding them as they should override your theme’s colour settings.

AnneR · 29 October 2015 22:49

Hey John,

yes the config_override.php did have the $sugar_config[ theme_settings ] rows in the file.

1st, I removed them, ran repair and rebuild with no change in the results, the lines in that config_overrride.php file were

$sugar_config[‘http_referer’][‘list’][0] = ‘cp3.hooplahosting.com’;
$sugar_config[‘default_currency_iso4217’] = ‘NZD’;
$sugar_config[‘default_currency_name’] = ‘NZ Dollars’;
$sugar_config[‘default_date_format’] = ‘d-m-Y’;
$sugar_config[‘default_locale_name_format’] = ‘f l’;
$sugar_config[‘disabled_themes’] = ‘Suite7’;
$sugar_config[‘default_module_favicon’] = false;
$sugar_config[‘dashlet_auto_refresh_min’] = ‘30’;
$sugar_config[‘enable_action_menu’] = true;
$sugar_config[‘stack_trace_errors’] = false;
$sugar_config[‘developerMode’] = false;

Next I tried the original file with the hex colour changed in the row with navbar, after running repair and rebuild there was still no change.

/CONFIGURATOR/
$sugar_config[‘http_referer’][‘list’][0] = ‘cp3.hooplahosting.com’;
$sugar_config[‘default_currency_iso4217’] = ‘NZD’;
$sugar_config[‘default_currency_name’] = ‘NZ Dollars’;
$sugar_config[‘default_date_format’] = ‘d-m-Y’;
$sugar_config[‘default_locale_name_format’] = ‘f l’;
$sugar_config[‘theme_settings’][‘SuiteR’][‘display_sidebar’] = true;
$sugar_config[‘theme_settings’][‘SuiteR’][‘navbar’] =[color=#ff0000] ‘#FF0000’;[/color]
$sugar_config[‘theme_settings’][‘SuiteR’][‘navbar_hover’] = ‘BC1A1A’;
$sugar_config[‘theme_settings’][‘SuiteR’][‘navbar_font’] = ‘FFFFFF’;
$sugar_config[‘theme_settings’][‘SuiteR’][‘navbar_link_hover’] = ‘FFFFFF’;
$sugar_config[‘theme_settings’][‘SuiteR’][‘dropdown_menu’] = ‘F7F7F7’;
$sugar_config[‘theme_settings’][‘SuiteR’][‘dropdown_menu_link’] = ‘3C8DBC’;
$sugar_config[‘theme_settings’][‘SuiteR’][‘dropdown_menu_link_hover’] = ‘FFFFFF’;
$sugar_config[‘theme_settings’][‘SuiteR’][‘action_menu_background’] = ‘FFFFFF’;
$sugar_config[‘theme_settings’][‘SuiteR’][‘action_menu_background_hover’] = ‘3C8DBC’;
$sugar_config[‘theme_settings’][‘SuiteR’][‘button’] = ‘3C8DBC’;
$sugar_config[‘theme_settings’][‘SuiteR’][‘button_hover’] = ‘597DBC’;
$sugar_config[‘theme_settings’][‘SuiteR’][‘button_link’] = ‘FFFFFF’;
$sugar_config[‘theme_settings’][‘SuiteR’][‘button_link_hover’] = ‘FFFFFF’;
$sugar_config[‘theme_settings’][‘SuiteR’][‘page_header’] = ‘333333’;
$sugar_config[‘theme_settings’][‘SuiteR’][‘page_link’] = ‘3C8DBC’;
$sugar_config[‘theme_settings’][‘SuiteR’][‘dashlet’] = ‘FFFFFF’;
$sugar_config[‘theme_settings’][‘SuiteR’][‘icon’] = ‘FFFFFF’;
$sugar_config[‘disabled_themes’] = ‘Suite7’;
$sugar_config[‘default_module_favicon’] = false;
$sugar_config[‘dashlet_auto_refresh_min’] = ‘30’;
$sugar_config[‘enable_action_menu’] = true;
$sugar_config[‘stack_trace_errors’] = false;
$sugar_config[‘developerMode’] = false;
/CONFIGURATOR/

What I have noticed is that changing the colors in theme settings does change the config_override.php file, i.e. if I change top menu base color to #D6FF08 then the config_override.php changes to $sugar_config[‘theme_settings’][‘SuiteR’][‘navbar’] = ‘D6FF08’;

Using firebug the css for the navbar is:
.navbar-inverse {
background: #3C8DBC !important;
}
I can of course temporarily override the color here.

I’ve tried changing the permissions on the /themes/SuiteR/css/colourSelector.php file with no change in results.

I’ve tried changing the color via css, but not sure I’ve done this correctly (spotted instructions in another post - https://suitecrm.com/forum/suite-themes/5726-change-background-colour-from-white-to-something-darker)

changed style.css

.navbar-inverse {
background:#FF0000 !important;
max-height:50px !important;
}

created custom/themes/SuiteR/css and copied style.css into it (with the changed css)
Ran repair and rebuild, repair relationships

no change

I happened to run the repair with firebug active, this error came up in the console

GET http://…/suitecrm/themes/SuiteR/css/colourSelector.php 404 (Not Found)
index.php?module=Administration&action=repair:613 Resource interpreted as Document but transferred with MIME type image/gif: “http://fourfiveplus.co.nz/suitecrm/index.php?entryPoint=getImage&imageName=blank.png”.
measureIt.js:120 Uncaught TypeError: Cannot read property ‘create’ of undefined(anonymous function) @ measureIt.js:120

Note colourSelector.php is in this directory as it is in the custom/themes directory (and I checked the spelling of colour)

PS, colourSelector.php has !important in the row starting .navbar-inverse, I have tried removing this and running repair etc but it made no diff.

AnneR · 2 November 2015 22:00

It seems the only way to make changes to the style are via …/suitecrm/themes/SuiteR/css/style.css. These changes are viewable and appear to remain regardless of which user you are logged in as. I expect this is not upgrade proof.

changes made in …/suitecrm/custom/themes/SuiteR/css (with the default themes/SuiteR/css/style.css file) are not viewable anywhere regardless of how many times you click repair and rebuild.

changes made front-end and saved (in developer mode or not) then running repair are not viewable.

please note the changes made in the themes/SuiteR/css/style.css are not reflected front end under admin, themes (default colours still show)

changing the colours in config_overide.php, running repair are not viewable.

AnneR · 9 November 2015 20:19

theme changes are working perfectly in 7.4, and it installed like a dream on localhost (didn’t have to muck around with permissions, php.ini etc).