Thanks. But the problem remains: where to put the files? I’ve reached that article, it’s pretty much what I have done - written a new bean derived from the original bean.
Where to put the files? How to make sure the new bean is being used instead of the original one?
Besides, I believe there is an easier way of doing that, with no need to rewrite the controller. If I change modules.php and replace Task.php by the CustomTask, it works - but it’s not upgrade safe.
So, there should be a way to extend module.php and indicate the new class for the Task bean,
I believe it is always going to read the modules/Task/Task.php before it reads any customization added to it. The custom controller way works though. You can test it easily by adding a $GLOBALS[‘log’]->debug(‘my custom class is being used’) to the overriding get_list_view_data.
it works but is not upgrade safe. There should be a way to modify that in an upgrade safe fashion.
Which is pretty much what the guy on this thread https://community.sugarcrm.com/thread/30996-sugar-bean-override-not-working suggested to change. It, however, is intended for SugarCRM (I don’t know the version) and probably the directories structure where to put the files is now different from SuiteCRM.
I just tried that way too and it does work without the custom controller. Put the beanList file in custom/Extension/application/Ext/Include/<somescript.php> just like it says. Run a quick repair and it should pick it up unless there’s a permission issue.