I can't be the only one

[llcorp]

Am I the only one have tremendous issues getting this CRM to install and work? I know I am not a PHP expert and all but to have to repair code and work on this for 7 days and it STILL doesn't work just pretty much has me angry and pissy. I can't be the only one in the world thinking this is a piece of crap right now. I see stellar reviews about SugarCRM and it seems to have everything I need on paper but it's of no use to me currently. Is it far fetched for me to think that it just doesn't work without heavily delving into the code to fix things?

[roblaus]

You may not be the only one but one of few. Let's say 0.1%. That makes me thinking that the problem may be in front of the screen.

I read your other thread but unfortunately I couldn't even find a hint about your environment or the "code fixes" that you had to apply. Most of us here KNOW that there is no need to fix anything to install Sugar if you stick to the (very simple) guidelines outlined in the manuals.

So it's probably better to start looking for another product if you can't deal with this one. One of the good things in our today's SW world is the freedom of choice.

[tjlewis]

Yeah sounds like your got some environmental issues there .

You can always opt to pay someone to install it or you can pay for the hosted version.

Are you trying to install it on windows or linux? Shared hosting account or on your own server? What version of php/mysql/os/sugar are you using? What are your php.ini settings/ webserver settings? etc etc etc. There is tons of information on the sugar wiki about installation etc. Maybe try there first or answer some of these questions and we'll try to help you.

[Angel]

Is it far fetched for me to think that it just doesn't work without heavily delving into the code to fix things?

Yes.

There is no need to modify the code in order to install. If you are doing so, you are treating the symptom, not the disease, as there is a bigger problem at hand. The install process itself doesn't take more than 5 minutes under normal circumstances.

Like others have stated, you might want to consider paying someone to do the install for you as it shouldn't be causing anyone that much aggravation, or like others suggested, move on to another product.

[llcorp]

I have actually tried 14 different CRMs only to have certain issues with functionality or it didn't do what I needed it to do. I really don't want to have to sit and write one myself but after a month of this, that is sounding better. I liked ...... but I could not get it to upload my logo which I thought was simple but nothing I tried worked so Sugar seemed the next best thing and has everything that I need. I'm not an idiot albeit a PHP beginner but code is code and words are words. It shouldn't be that hard to fix a perms error. I ended up installing it just because I got tired of looking at the directory and go figure I can't get the entire thing to delete so now I'm bitching at my VPS host because this isn't the first time I have had issues like this. Maybe it's them...

[roblaus]

If it helps here's my standard setup that I always use and which always worked (and still does):

(Fresh) install of Ubuntu LTS Server (8.04 currently) or Debian
Plain vanilla LAMP stack from the Ubuntu/Debian repositories (for speed reasons I sometimes use Lightspeed but this is a matter of taste).
rem: I am still using php 5.2.8
One app directory somewhere
Underneath the Sugar directories
After copying and unzipping Sugar I set the user/group for the entire Sugar directory (incl. subs) to www-data (this is the Debian/Ubuntiu webserver user)
Then again for the entire directory incl subs I set the permissions to 755.
You may change some dirs to 644 later on as suggested.
For each installation I create a session directory within the Sugar structure (again 755) and I do set the session save path in config.php accordingly (NOT in php.ini and NOT in .htaccess).
During installation I always have Sugar create the db and the respective user (not root of course)
The db always sits on the same server as Sugar (at least for the installation). This means you need to use "localhost" rather than the path Sugar suggests.

That pretty much is it and I installed Sugar probably a 100 times on at least 20 different machines/environmments.

[crmsiva]

Hi

Robert is right. I usually give 777 permission, while doing installation or upgrades. Later will change it to either 755 or 644. Alternatively chown is a good idea.

[llcorp]

Well, after a few hours of changing perms in SSH, I found my problem. I had a few faulty files that were...I guess half downloaded or something because I was having issues with particular directories and not other ones. Seems my FTP client was restarting the connection midway through transfers so I ended up reinstalling the SugarCRM directory to the account 5 times before I found that setting in my client. Also, the httpd service had crashed several times so that had to be restarted a few times before it would work properly. I think the httpd service had been down for a bit but I turned auto restart on so that should fix it. After correcting all of these issues, I had a pretty flawless FRESH install and things seem to be working. Now, I don't feel so defeated by software.

[crmsiva]

Great. Enjoy playing with SugarCRM