After upgrading to the new version of windows internet explorer, I am facing the issue where the email field is not shown. And, after I edit a contact, the existing email address will disappear.
Is there a solution to this problem? Thanks.
After upgrading to the new version of windows internet explorer, I am facing the issue where the email field is not shown. And, after I edit a contact, the existing email address will disappear.
Is there a solution to this problem? Thanks.
That is a known compatibility issue with IE9. It is not yet supported by Sugar.
I don't use IE9, but apparently it has some sort of compatibility mode you can enable which helps with this problem. Short of that, the only other solution is to use a supported browser.
See here for a list of supported versions: http://www.sugarcrm.com/crm/content/...ents-sugar-62x
Regards,
Angel Magaņa
Co-Author: Implementing SugarCRM 5.x (Packt Publishing -- Sept. 2010)
Blog: http://cheleguanaco.blogspot.com.
Twitter: @cheleguanaco.
________
| Projects: |_____________________________________
|
| CandyWrapper (.NET Wrapper for SugarCRM SOAP API). Source now available on GitHub!
| GoldMine to SugarCRM Express Conversion. Latest: 1.0.1.7 (Nov. 3, 2009)
| CRM SkyDialer (Skype Integration). Latest: 1.0.2 (Feb. 17, 2010)
| Round Robin Leads Assignment
| Phone Number Formatter
| CaseTwit (Twitter Integration)
______________________________________________
Sugar announced support for IE9 for one of the next releases, as far as I remember it will be 6.2.3.
There are similar problems with Firefox 4 so I'm using Google Chrome now which is working fine with the actual Sugar releases.
Stefan Ulrich Sauer
System Analyst
Devoteam Danet GmbH
Gutenbergstraße 10
D-64331 Weiterstadt
Germany
email: Stefan-Ulrich.Sauer@devoteam.com
http://www.devoteam.de
I donīt really understand this. I know that IE9 was still beta when Sugar was launching 6.1.1 but why it is not running yet and why they donīt fix it unitl now. IE9 is still the most common browser and we are using it as standard. Our 250 User donīt have another browser option. It works with comp mode and we can launch a policy that our Sugar CRM is always running in comp mode but hey. is this correct?
--
Best regards
Matthias Brück
IT Manager, CRM Specialist IT Dep.
Roxtec Int. AB
+49 1724392462
matthias.brueck@de.roxtec.com
http://www.roxtec.com
WE SEAL YOUR WORLD
Probably because compatibility with IE9 is not the only priority they have.
Also, speaking from personal experience, I have seen multiple situations where a Beta release of IE will work one way and the RC release works differently. My point being, testing for compatibility when IE is beta is often times a wasted effort because whatever it is you discover/fix during that phase in order to make it compatible often times ends up being useless once IE goes to RC.
Regards,
Angel Magaņa
Co-Author: Implementing SugarCRM 5.x (Packt Publishing -- Sept. 2010)
Blog: http://cheleguanaco.blogspot.com.
Twitter: @cheleguanaco.
________
| Projects: |_____________________________________
|
| CandyWrapper (.NET Wrapper for SugarCRM SOAP API). Source now available on GitHub!
| GoldMine to SugarCRM Express Conversion. Latest: 1.0.1.7 (Nov. 3, 2009)
| CRM SkyDialer (Skype Integration). Latest: 1.0.2 (Feb. 17, 2010)
| Round Robin Leads Assignment
| Phone Number Formatter
| CaseTwit (Twitter Integration)
______________________________________________
If you have access to the server, you can put the following line in your Sugar's main .htaccess file
supporting documentation to be found at https://blogs.msdn.com/b/hanuk/archi...ng-in-ie8.aspx which explains some apache changes that may be necessary.Code:Header set X-UA-Compatible: IE=EmulateIE8
If you're more adventurous, for Sugar 6 you can edit the main Sugar template that is found in SugarDir/themes/Sugar5/tpls/_head.tpl If you put the following into it directly under the '<head>' you'll have success. You'll have to do a 'Repair and Rebuild' after this, but it may not be upgrade safe.
Upon success, the user will not see the little icon that allows them to switch Compatibility modes anymore -- and the email addresses won't disappear, either. :^)Code:<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" />
Sugar 6.2.2 is compatible with IE9. Upgrading Sugar would correct the problem.
Regards,
Angel Magaņa
Co-Author: Implementing SugarCRM 5.x (Packt Publishing -- Sept. 2010)
Blog: http://cheleguanaco.blogspot.com.
Twitter: @cheleguanaco.
________
| Projects: |_____________________________________
|
| CandyWrapper (.NET Wrapper for SugarCRM SOAP API). Source now available on GitHub!
| GoldMine to SugarCRM Express Conversion. Latest: 1.0.1.7 (Nov. 3, 2009)
| CRM SkyDialer (Skype Integration). Latest: 1.0.2 (Feb. 17, 2010)
| Round Robin Leads Assignment
| Phone Number Formatter
| CaseTwit (Twitter Integration)
______________________________________________
Yes, but not everything else is 6.2.x compatible... Some of our clients are still using 5.5.4
My solution is upgrade safe and requires minimal effort. YMMV :^)
We had similar issues and it was down to the browser having cached the previous email field javascript widget which failed with the new version. Just force the user to refresh the edit view - or clear their cache - and it MAY work.
Had the same issue with SugarCRM 5.5 and IE9, the .htaccess Header fixed it but i found another way too:
In /include/SugarEmailAddress/SugarEmailAddress.js find this section in function addEmailAddress()
and remove it completelyCode:if(nav.match(/MSIE/gim)){newContentPrimaryFlag=document.createElement("<input name='emailAddressPrimaryFlag' />");}
then the line will still include the "else" -section, remove "else {" and the closing "}" so there is nothing left from the if-else-statement, except the contents of that else which is:Code:var newContentPrimaryFlag;newContentPrimaryFlag=document.createElement("input");
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks