CustomerCentrix

The upgrade did not work for us. I am sure that there was something along the way that we did wrong, but after much fussing, I decided to move the older version to another location and try with a brand new install.

Can't get past step 1; that's not a good start. Blame it on Firefox? IE allows us to accept the license agreement and move ahead. All is green on step 2 except the Writable Session Save Path. Another black mark, but if we give the Sugar folks the benefit of the doubt, then we can say that this probably works on other more common installation setups.

The choices for dealing with this are to change the Sugar code so that it bypasses this check or tinker with the PHP setup so that the check is passed. I had this problem before on previous versions tinkered with the underlying code to skip that check. This worked before, so I will try again. This isn't what I would normally choose or advise, but the check seems to be wrong since the directory is valid and I already checked permissions to make sure that it was writable.

From line 439 in install/checkSystem.php remove:

<?php if($error_found) { echo disabled="disabled"'; } ?>


The rest of the install steps went easily, filling in the database name and other details.

Now on to using the system. Overall, I have to say that I am pleased to not find any errors after an hour or so use of the system. There is one problem that I found and took a while to fix related to this in the "improvements" within the release notes:

Fixed: Locked down many directories and files using .htaccess.
Note: For Apache, verify that the AllowOverride setting in httpd.conf is set to "All", or that you have mirrored the settings in all .htaccess files.

While this sounds nice on the surface, who can argue with better security? What they don't say is that the cron job that was set up in previous installations for running the mass emailer will not longer work. You have to run emailmandelivery.php, but the new htaccess file redirects this to the home page. The intent is that there is an override for this redirect, so that the server can run the file but no one else can. This bit of information is unclear to me from the Fixed statement above. If you just comment out the last line of the htaccess file for emailmandelivery, then it will start working again.