Can Not Deply Custom package

[ajlisowski]

Hey all, I am having an issue that is hurting my development with SUGAR. I am unable to deploy any custom packages.

I have two enviroments, my development XAMPP set up on my local machine.

And my company's LAMPP set up on a unix box.

SUGAR works perfectly fine on my local XAMPP machine. However any package I create there can not be loaded into the UNIX installation of SUGAR.

I am able to develop on XAMPP and deploy my modules there, then I am able to move my updates to the UNIX box by exporting the database and uploading the custom directory via FTP.

However is not the best way to do things. When I try to load a module or deploy one in the UNIX install it just freezes up, any ideas?

[ajlisowski]

It appears as though 2 of my modules get installed out of the package, then it dies. So I am assuming one of the modules is causing the problem!

[andopes]

Some tips:

Edit the php.ini at your linux server and update the attributes to log errors, display errors and display all kind of errors (Errors, Fatals, Warnings);
Update into php.ini the attributes for max allowed memory, upload max size, time out, post max size;
Restart your apache;
Try again.

Hopefully you will see some error message.

Let us know them.

Kind regards

[ajlisowski]

Ok, so I am able to export a module from an installation on my server and successfully upload/install it to another sugar install on my server. I just can not deploy the module to the installation its created in.

The only error I get when installing the export is that although the module shows up in the list of packages it does not show up in the installed modules list. Deploying the module adds another version of the module to the list of packages but still nothing in the installed modules.

When I try to delete the module from the list, the entries created by deploying will not be deleted.

I will post soon with various errors logged from apache.

[ajlisowski]

So. I think I fixed it. I turned error reporting on in index.php and then I manually entered the URL for the ajax request when deploying. I got a number of reasonable responses "Table already exists" etc. Then a memory error. So I jacked up my memory and then I got a completed.

Apparently my PHP settings just didnt have enough memory allocated for Sugar to deploy the modules. I think this is something that should be mentioned on install. Or perhaps it was and I just didn't notice.

I wonder if more memory would be required for larger packages?

Either way deploying seems to work now. The module is listed as installed and can be uninstalled now! Yay!

One question though: When redeploying, changes to tables that already exist dont seem to take effect. Should I uninstall always before redeploying? This would work fine for development. But it would be tricky if modifications have to be made AFTER the system goes into production. If I want to add a field a month from now I would have to backup the module tables and then write an import script to bring them into the newly deployed tables. That seems a bit silly. Am I wrong about this?