Can modules be installed without using the built-in module loader?

[benfremer]

Thanks,

Ben

[mycrmspacegunnar]

Hi,

Well, if you know what your are doing then you can of course install modules manually.
Depending on the module this can be some work and you will not have the luxus of being able to de-install the module so easely.
In general I can very much recommend you to use the module loader.

Is there a good reason why you could not use it?


Cheers
Gunnar

[dionv]

Hi,

Well, if you know what your are doing then you can of course install modules manually.
Depending on the module this can be some work and you will not have the luxus of being able to de-install the module so easely.
In general I can very much recommend you to use the module loader.

Is there a good reason why you could not use it?


Cheers
Gunnar

Yes, there would be a good reason for some users.

My hosting provider offers an Installatron-based installation of SugarCRM, which handles the mundane details of a basic SugarCRM installation. When the installation is completed, all files are set owner:group of the account name eg: myaccount:myaccount. However, when modules are installed, they receive the owner:group of the webserver, apache:apache, which then makes the rest of the installation process fail as the Module Loader can no longer copy files into the new directories due to lack of permissions.

My hosting provider currently requires that I contact them to have the permissions of owner:group adjusted manually. At that point I then need to try installing the module again, and hope it picks up from where it left off.

Currently I have 10 modules that I would like to install and test. This could be a very tedious process. I'm not sure what the best workaround would be, other than a manual installation, as files that are uploaded through the account's file manager receive the proper owner:group and permission.

DionV

[kbrill]

Do you have ssh/telnet access? If you can manually install files, why can't you change the permissions yourself?

[chrisky]

Yes, there would be a good reason for some users.

My hosting provider offers an Installatron-based installation of SugarCRM, which handles the mundane details of a basic SugarCRM installation. When the installation is completed, all files are set owner:group of the account name eg: myaccount:myaccount. However, when modules are installed, they receive the owner:group of the webserver, apache:apache, which then makes the rest of the installation process fail as the Module Loader can no longer copy files into the new directories due to lack of permissions.

My hosting provider currently requires that I contact them to have the permissions of owner:group adjusted manually. At that point I then need to try installing the module again, and hope it picks up from where it left off.

Currently I have 10 modules that I would like to install and test. This could be a very tedious process. I'm not sure what the best workaround would be, other than a manual installation, as files that are uploaded through the account's file manager receive the proper owner:group and permission.

DionV

Wow.. That sounds like a bit of a conundrum..

It really has nothing to do with Sugar but is just simply some 'issues' with your hosting provider [depending on all the specifics of which haven't been covered in this thread as of yet].

It sounds like a really wacky hosting provider and setup to me, but I'm also going on some insights and assumptions I have.
If things are that messed up or more politically correct, 'if things are that unsuitable for your needs', you might pursue finding a new hosting provider..

Ken raised an absolutely excellent point and question. Do you have shell access?
I'm assuming that you do not.. Especially reading that you must contact the hosting provider each time you want [file] permissions changed.

Anyways, skipping my various assumptions, I'll get to my suggestion of which is based on some assumptions of mine followed by my assumption that you were intent on staying with that particular provider and environment.

My suggestion would be to install sugar either locally (on your pc) or under another host/environment, and proceed to install all modules in which you planned, etc.. Then archive that sugar deployment, upload (ftp, etc.) that archive package to your host.. Decompress it, and have'em just recursively change the file ownership/group(s)/and permissions.

But it really sounds like you might want to pursue finding a more suitable and friendly [to your needs and/or uses], hosting provider.

Good luck and Happy New Year!

[mycrmspacegunnar]

Yes, there would be a good reason for some users.

My hosting provider offers an Installatron-based installation of SugarCRM, which handles the mundane details of a basic SugarCRM installation. When the installation is completed, all files are set owner:group of the account name eg: myaccount:myaccount. However, when modules are installed, they receive the owner:group of the webserver, apache:apache, which then makes the rest of the installation process fail as the Module Loader can no longer copy files into the new directories due to lack of permissions.

My hosting provider currently requires that I contact them to have the permissions of owner:group adjusted manually. At that point I then need to try installing the module again, and hope it picks up from where it left off.

V

Well this setup sounds really wierd!

That your files are installed under your userid makes good sense from a security point of view
BUT only when apache does run under your userid as well.

That Apache runs as apache and can access to multible Sugar installations
in which people can upload new modules sounds most bizarre to me.

What prevents one of the users to upload a PHP-SHELL and to access all the other users Sugar installations
as well as to read their database contents?


Cheers
Gunnar

[rickcrites]

I host my Sugar system on a hosted server as well. I have found I can make things work well by setting all the file to ownership myuserid:apache, and setting the read/write permissions on all the files so that they can be read and written by owner and group. This allows me to install all modules without difficulty. I do need to go back in (with SSH, as Ken suggested) and update the permissions from time to time to ensure that Sugar updates will load. Or, you hosting service can go in and pretty easily recursively reset the permissions when necessary, if you are not able to do it yourself.

There is an instructional bulletin in the WIKI about setting permissions, and using hosting services. Check that out for more help.

Best,