garbage characters in all browsers but I/E after upgrade

[jmiani]

I just upgraded to Sugar 6.1.0; upgrade was successful but all browsers except I/E show garbage characters in the header above the DOCTYPE reference (see attachment). I am using Apache 2.2 and PHP 5.2 on a windows 7 pro 64 bit machine; I've tried to make sure everything involved is using UTF-8 encoding. Any suggestions on cause of this or solution to it?

Also, this is my 3rd attempt to post on this topic - I tried the first two under installation and upgrade help forum and although the submissions seem to be successful, they never seem to show up on the forum. Apparently they must go through a moderator? Anyway, not sure what is going on there, these are legitimate posts and I attempted the first one was several days ago. Hopefully this one gets through on this forum.

[Angel]

I seem to recall that in the past, this issue was related to the version of PHP in use. Take a look here to see if the version you are using matches the list of supported versions:

Supported Platforms for Sugar 6.1.x | Open Source Business & Social CRM - SugarCRM

If it doesn't, you'll need to install an appropriate version of PHP or upgrade Sugar in order to correct the problem.

As for your posting issue, I think it was a temporary glitch with the Forums software as I was having a similar posting problem recently too.

[kuske]

It is possible that you have some binary files in your custom directories not belonging to sugarcrm.

Check alle the custom directories for non php files.

[jmiani]

Hi Angel,
Thanks. I was running PHP 5.2.16 and that is not supported. I upgraded it to 5.2.17 which is and I am still having the same issue. I checked phpinfo and to make sure I upgraded php properly and it is showing 5.2.17

[jmiani]

Harald,
Thanks, I thought you had hit upon the answer because I had some binary files from ZuckerReports under my custom folder. However, I have moved all of them out of sugar entirely (in fact I moved everything under the custom folder except for index.html), restarted Apache, and still the same issue.

Jim

[jmiani]

I just noticed the footnote that PHP 5.2.17 is supported only under 6.1.2 or better. Arrrrgh. Will upgrade one or the other and report back on success/failure.

[jmiani]

OK now I've upgraded PHP to 5.3.3 and Sugar to 6.2.4 and I am still having the same problem. Does anyone have any suggestions for me on what to try next?

[Angel]

This is a thread that touches on the issue I was initially thinking of after your first post on the matter:

http://www.sugarcrm.com/forums/f3/su...racters-67849/

You might want to check the zlib compression setting to see if it helps.

[jmiani]

This is a thread that touches on the issue I was initially thinking of after your first post on the matter:

http://www.sugarcrm.com/forums/f3/su...racters-67849/

You might want to check the zlib compression setting to see if it helps.

OK, well I checked the zlib compression setting and it is set to Off. I also tried to put in andopes hack mentioned in the thread you gave me, but the lines he mentions were already commented out. The original poster (Jashank) in that thread solved his problem by upgrading php, but I am up to 5.3.3 at this point. I am also up to 6.3.1 of Sugar. I have apache 2.2.17 and mysql 5.5.

One thing I have noticed is that in threads similar to mine the posters entire sugar page is garbage. In my case it is only a few lines preceding the header information (I've attached another screen shot below that shows the source of the page). Does that provide a clue? What is being output in the page prior to the DOCTYPE declaration? (Unfortunately when I do a view source in IE I am not getting the source at all, not sure why).

I am just about ready to punt, reinstall sugar from scratch, and recreate all customizations - but I'd hate to do that as it leaves me zero confidence in the upgrade path for next time.

[Angel]

Yes, understood about the entire page versus just a line.

Something else is at play here though, because it shouldn't be necessary to make edits of the type you speak of in order to get it to display correctly.

I would double check the version of PHP via phpinfo() to make sure things aren't being mixed up for some reason. Also, what version of Firefox are you using?