Deleting files after deploying a custom module

[niksata]

Hi there,

I'm using SugarCRM Community Edition 6.4.0, and I have a problem when I'm trying to use logic_hooks.
I created a logic_hooks.php script in which the event, the reference to the PHP script and etc. are described, as shown in the Guide. I put this file into the folder custom/modules/<MyCustomModule> folder.
However, when I deployed the module by using the Module Builder, I discovered that the file logic_hooks.php had been erased from custom/modules/<MyCustomModule>. The same happened with the controller.php script, located in the same folder.

Any information? Is there something I'm not aware of?
Thanks in advance
Niksa

[solid]

Same thing happened to me. I opened a bug SugarCRM Bug Tracker | Open Source Business & Social CRM - SugarCRM

[eggsurplus]

Best practice is to only use Module Builder initially as it does a great job of getting you going as fast as possible. After deploying once stick with using Studio instead as that does a great job of maintaining your customizations. Module Builder has had a history of overwriting your customizations for some time now. At the very least a warning should come up.

[solid]

Best practice is to only use Module Builder initially as it does a great job of getting you going as fast as possible. After deploying once stick with using Studio instead as that does a great job of maintaining your customizations. Module Builder has had a history of overwriting your customizations for some time now. At the very least a warning should come up.

The problem with Studio is that the customizations are stored in the DB, while Module Builder store everything in files. Also, Studio add a new table instead of modifying the table wanted itself. If you want to have your Sugar under source control, Studio is not a good choice.

All the modules created with Module Builder here are maintained using it. We only use Studio to customize the Sugar modules, since there is no other way to make them.

[eggsurplus]

Oh I completely agree. This is why I'd suggest to then use the Extensions directory to make additional modifications to your module's schema. Great thing about it is works well with code repositories and is easy to deploy. Just add to custom/Extension/modules/YOURMOD/Ext/Vardefs/anyfile.php. Then again it is your custom module so you could edit the modules/YOURMOD/vardefs.php to add all the fields you need. Quick Repair/Rebuild and execute the generated SQL to add your field(s). I'd highly advise against using MB for ongoing customizations. Great for proof of concepts and for getting started quickly.

[solid]

Oh I completely agree. This is why I'd suggest to then use the Extensions directory to make additional modifications to your module's schema. Great thing about it is works well with code repositories and is easy to deploy. Just add to custom/Extension/modules/YOURMOD/Ext/Vardefs/anyfile.php. Then again it is your custom module so you could edit the modules/YOURMOD/vardefs.php to add all the fields you need. Quick Repair/Rebuild and execute the generated SQL to add your field(s). I'd highly advise against using MB for ongoing customizations. Great for proof of concepts and for getting started quickly.

Yep, doing that already, and it works like a charm. My point was that in Sugar 5.5 Module Builder was not scraping Extensions files like the Sugar 6.3 Module Builder is doing. Except for that, I have no problem to use Module Builder to make ongoing customizations.