Custom Button in Detailview of Custom Module

[best_kobe_beef]

Hello again,

this time i'm trying to recreate a problem which appears here very often and was solved very often but in my case i don't know what i am doing wrong.

I tried the following approach in both SugarCRM 5.5 CE (already customized= and 6.03 CE (fresh install).

1) i created a custom module via Module Builder
2) i edited the file custom/modules/my_custom_module/metadata/detailviewdefs.php


The first lines of the file before modification:

<?php
$module_name = 'my_custom_module';
$_object_name = 'my_custom_module';
$viewdefs [$module_name] = 
array (
  'DetailView' => 
  array (
    'templateMeta' => 
    array (
      'maxColumns' => '2',
'form' => 
        array (
        ),
      'widths' =>

and afterwards, one of several approaches trying to get a custom button in there

<?php
$module_name = 'my_custom_module';
$_object_name = 'my_custom_module';
$viewdefs [$module_name] = 
array (
  'DetailView' => 
  array (
    'templateMeta' => 
    array (
      'maxColumns' => '2',
'form' => 
        array (
          'buttons' => 
          array (
            0 => 'EDIT',
            1 => 'DUPLICATE',
            2 => 'DELETE',
            3 => 'MY_CUSTOM_BUTTON',
          ),
        ),
      'widths' =>

After saving the file, and reloading the page nothing changed. What am i mssing here?



I then also tried changing other fields, but also with no effect

 'panels' => 
    array (
      'default' => 
      array (
        0 => 
        array (
          0 => 
          array (
            'name' => 'document_name',
            'label' => 'LBL_DOC_NAME',

to

 'panels' => 
    array (
      'default' => 
      array (
        0 => 
        array (
          0 => 
          array (
            'name' => 'document_name',
            'label' => 'LBL_SF_CATEGORY',

breaking the code is easy - resulting in a white empty page, therefore i don't believe it's caching or the wrong file i'm editing.

 array (
            'name' => 'document_name',

to

 arrrrrrray (
            'name' => 'document_name',

[andopes]

Custom Buttons on SugarCRM must be accomplished just like Convert Lead button on Leads DetailView.

Regards

[best_kobe_beef]

Custom Buttons on SugarCRM must be accomplished just like Convert Lead button on Leads DetailView.
Regards

Hello andopes! Thanks for your reply, can you give me a hint on how to implement it here? I already looked at various of your posts and tried that approach, one example of such a post here:
http://www.sugarcrm.com/forums/showthread.php?t=58036

more details added into the first post (renaming labels had also no effect for example).

Maybe i do have to explicitely combine both steps
1) modify detailview
2) create controller

or said in other words: before the button even appears, a controller has to exist?

[best_kobe_beef]

To answer my question myself:
Steps 1 and 2 must both be finished for changed to be applied.

After changing the button array AND creating controller.php, something happens (blank page, well....) when changing the filename of controller.php to acontroller.php, i indeed do have the unchanged website presented.

Therefore i now need to look into how to correctly implement code into controller.php, but i think i will get to that quickly looking into other threads.

[andopes]

It is interesting to understand the MVC architectural pattern and the SugarCRM MVC Framework as well.

Whenever you send some request to Sugar the Controller process this request and forward it to a view, if applicable.
The action of button, you are going to implement, is fetched by Controller, so Sugar Controller look for a function called "action_<action_name>" where <action_name> is the own action you configured into your button.
This function on controller may figure out, by itself, all the stuffs, or invoke a view if applicable.

Take a look on modules/Leads/metadata/detailviewdefs.php

Regards

[best_kobe_beef]

It is interesting to understand the MVC architectural pattern and the SugarCRM MVC Framework as well.

Whenever you send some request to Sugar the Controller process this request and forward it to a view, if applicable.
The action of button, you are going to implement, is fetched by Controller, so Sugar Controller look for a function called "action_<action_name>" where <action_name> is the own action you configured into your button.
This function on controller may figure out, by itself, all the stuffs, or invoke a view if applicable.

Take a look on modules/Leads/metadata/detailviewdefs.php

Regards

Thanks for the architectural explanation and your patience. I am confident i can now solve that problem looking into modules/Leads/metadata/detailviewdefs.php and working my way from there to the custom logic implementation in the controller.