Hosting: Anyone on M8 Solutions?

[appdev]

I'm having an issue with a hosting provider, and I'm wondering if anyone else has / is running into anything similar.

M8 Solutions set up a new account w/ Sugar 4.5.1 already in place and running -- this was great. The files are all owned by username:webservername -- so username is the user, and webservername is the group. So far, so good.

When I ftp anything to the server, however, it ends up being owned by username:username -- this means that the web server now no longer has the same access to this file that it did before. In many cases, this is BAD, because it prevents Sugar from writing files when it needs to.

I begged and pleaded with M8 to get shell access so I could chown these files, and they finally granted this to me, but my login didn't have permission to chown to the proper user and group so the web server would be happy again.

This is driving me nuts, and I can't seem to get M8 to understand the problem.

Has anyone else experienced this with M8 or other providers? I'm afraid if this doesn't get resolved soon, I'm going to have to look for a new home for this client.

[appdev]

FYI -

I'm still going round and round with these guys. Latest example:

I needed to modify the Leads listview to include another column. Normally, this is a five-minute fix in SugarCRM's studio, so i went in and customized the listview to include the extra field.

I saved the view and went to test it, and no change had taken place. I went back into the Studio and found that my changes had reverted.

I did the same customizations on a local test system, and they worked just fine. I noted the most recently-modified files and saw custom\modules\Leads\metadata\listviewdefs.php had been changed.

Back to M8 - I used file explorer to look at the directory structure on the production server, and found there was no "metadata" folder beneath "Leads". When Studio tried to create that directory so it could store the newly-customized file, the web server process had been unable to make the directory. If the directory had been created, I don't know if the web server would have been able to create a new file there, but I wouldn't be surprised if that failed, too.

I was able to get the changes to show up only by manually creating the folder and then uploading the file I modified on my test system.