Hi!
I have to customize DetailView.tpl of the Account module. I created the Accounts folder in themes/SuiteP/modules and inside I defined tpls/DetailView.tpl folder. This file is completely ignored.
I saw that the same thing was done for the Users and it works.
What am I doing wrong?
Only for the Accounts module I want to change the size of the bootstrap columns.
I created the file and put these few lines to see if it goes through this file but it is completely ignored
{{sugar_include type="smarty" file=$headerTpl}}
{sugar_include include=$includes}
<form action="index.php" method="post" name="DetailView" id="formDetailView">
<input type="hidden" name="module" value="{$module}">
<input type="hidden" name="record" value="{$fields.id.value}">
<input type="hidden" name="return_action">
<input type="hidden" name="return_module">
<input type="hidden" name="return_id">
<input type="hidden" name="module_tab">
<input type="hidden" name="isDuplicate" value="false">
<input type="hidden" name="offset" value="{$offset}">
<input type="hidden" name="action" value="EditView">
<input type="hidden" name="sugar_body_only">
</form>
<div class="detail-view">BBBB</div>
Could you please have a look at here:
https://community.suitecrm.com/t/how-do-you-switch-from-metadata-to-smarty-templates/82514/2
maybe you’ll find something useful
Thanks but I ask a question anyway.
I understand that suiteCRM first checks if it is there
themes / SuiteP / modules / Accounts / tpls / DetailView.tpl
and if it doesn’t find it
themes / SuiteP / include / DetailView.tpl
Is this not correct?
Hi @crmex , I’m sorry if this isn’t the answer you are waiting for, but have you checked this:
?
I think you can go with:
custom/modules/Accounts/views/view.detail.php
<?php
if(!defined('sugarEntry') || !sugarEntry) die('Not A Valid Entry Point');
require_once 'modules/Accounts/views/view.detail.php';
class CustomAccountsViewDetail extends AccountsViewDetail
{
…
}
And you can add some css classes like here: