¿Cuál es la estructura de archivos en la implementación de SugarCRM desde Studio?

I am facing a problem with SugarCRM. I made a relationship and other changes from Studio and deployed them. However, my previously made changes from ModuleBuilder and custom changes within the /custom/modules directory vanish. Why is that?

I also have another question:

When I make changes and deploy from ModuleBuilder, SugarCRM distributes the copy of changes from the /custom/ModuleBuilder/packages directory. If I make changes and deploy from Studio then where does SugarCRM distribute the copy of changes?

preguntado el 22 de mayo de 14 a las 14:05

1 Respuestas

Mixing SugarCRM's Module Builder and Studio tools is dangerous, and it seems like you just found out why.

Building out a module in Module Builder is absoltuely the best practice, but once it's deployed, you'll want to nunca hit deploy again. The Deploy button wipes out anything in /custom/Extension/modules/MyModule/Ext/ e /custom/modules/MyModule for your custom module NewModule. MyModule exactly where Studio puts it's changes, whether they're new fields, layouts, or relationships.

A great way to avoid this is to keep your system in version control. A simple git init works wonders, but you'll probably want to use a .gitignore archivo como SugarCRM.gitignore.

Another way to accommodate this is to keep a production and a staging server. That way you can be 100% sure that what you're trying to do works before you do it. This also lets you use Module Builder in the development system, then Publish the package, and install it in production. That way Production doesn't have the package in Module Builder, thus there is no Deploy Button to push.

contestado el 22 de mayo de 14 a las 21:05

No es la respuesta que estás buscando? Examinar otras preguntas etiquetadas or haz tu propia pregunta.