Modify LogView to add the navbar in the view

Alexbmp · 24 April 2026 12:27

Good morning,
I am trying to modify the LogView view in my SuiteCRM 8.9.0 installation, since in this section of the CRM the navbar does not appear, and I need it for some screenshots I have to take as a demonstration for a project, where we are required to have the top bar visible.

Is there any way to also display the menu bar in this section of SuiteCRM?

Thank you in advance.
Best regards,

BastianHammer · 25 April 2026 13:08

Hello Alex,

you only need it for a screenshot?

How about simply using an image editor and put the two parts together?
A screenshot of the navigation and a screenshot of the log view?

Alexbmp · 27 April 2026 05:17

Good afternoon,

Initially, this requirement is for taking screenshots, although in the future we will need to carry out a demonstration of the application’s functionality within our business environment. In other words, we must prove that we are using the solution correctly (we have actually been working with it for several months).

The issue is that, before reaching that demonstration stage, we are required to provide usage screenshots. We have successfully passed the other 49 validation points, but in this particular case, the logs section does not display the top navigation bar like the rest of the sections, which is causing our project to be rejected.

The workaround you mentioned, involving making an edit, could help us gain some time while we implement the navigation bar. However, for the demo, it would be necessary for it to be displayed correctly.

Therefore, I would like to ask whether this modification is possible, as I am not entirely sure to what extent SuiteCRM allows this part of the interface to be customized in this way.

Thank you very much in advance for your help.

Best regards,

BastianHammer · 27 April 2026 06:19

I’d challenge the real business requirement behind this request?

The log viewer only shows the suitecrm.log file - not the Suite 8 files, not the upgrade and not the installation. There isn’t an access to the web-servers log files as well.

I only use this in odd / specific cases, where the admin doesn’t have access to server and could do some ad hoc investigation. It’s often only a workaround.

Much better would be, to create a specific FTP / SSH user with access only to the logs directory - that would provide the whole picture + all features that cannot be provided by the UI easily (log streaming, file size, date time stamps, loading 100MB large log files etc.).

If it absolutely has to be a log view UI feature inside the CRM, it would probably be best to create a new module from scratch with the new logs as well.

github.com/SuiteCRM/SuiteCRM-Core

public/legacy/modules/Configurator/LogView.php

d122172c0


      
          }
          $ignore_self = false;
          if (!empty($_REQUEST['ignore_self'])) {
              $ignore_self = 'checked';
          }
          $reg_ex = false;
          if (!empty($_REQUEST['reg_ex'])) {
              $reg_ex = 'checked';
          }
          set_time_limit(180);
          echo <<<EOQ
          <form action='index.php' name='logview'>
          <input type='hidden' name='action' value='LogView'>
          <input type='hidden' name='module' value='Configurator'>
          <input type='hidden' name='doaction' value=''>
          <input type='button' onclick='document.logview.doaction.value="all";document.logview.submit()' name='all' value='{$mod_strings['LBL_ALL']}'>
          <input type='button' onclick='document.logview.doaction.value="mark";document.logview.submit()' name='mark' value='{$mod_strings['LBL_MARK_POINT']}'>
          <input type='submit' name='display' value='{$mod_strings['LBL_REFRESH_FROM_MARK']}'>
          <input type='button' onclick='document.logview.doaction.value="next";document.logview.submit()' name='next' value='{$mod_strings['LBL_NEXT_']}'>
          <br>
          {$mod_strings['LBL_SEARCH']} <input type='text' name='filter' value='$filter'>&nbsp;{$mod_strings['LBL_REG_EXP']} <input type='checkbox' name='reg_ex' $reg_ex>

github.com/SuiteCRM/SuiteCRM-Core

public/legacy/modules/Configurator/tpls/EditView.tpl

d122172c0


      
          			{assign var='stackTraceChecked' value='CHECKED'}
          		{else}
          			{assign var='stackTraceChecked' value=''}
          		{/if}
          		<td><input type='hidden' name='stackTrace' value='false'><input name='stackTrace'  type="checkbox" value='true' {$stackTraceChecked}></td>
          		<td scope="row">{$MOD.LBL_LOGGER_MAX_LOGS} </td>
          		<td> <input name="logger_file_maxLogs" value="{$config.logger.file.maxLogs}"></td>
          	</tr>
          {/if}
          	<tr>
          	    <td><a href="index.php?module=Configurator&action=LogView" target="_blank">{$MOD.LBL_LOGVIEW}</a></td>
          	</tr>
          </table>
          
          
          <div style="padding-top: 2px;" class="btn-hide">
          <input title="{$APP.LBL_SAVE_BUTTON_TITLE}" class="button primary"  type="submit" name="save" value="  {$APP.LBL_SAVE_BUTTON_LABEL}  " class="button primary"/>
          		&nbsp;<input title="{$MOD.LBL_SAVE_BUTTON_TITLE}"  class="button"  type="submit" name="restore" value="  {$MOD.LBL_RESTORE_BUTTON_LABEL} " />
          		&nbsp;<input title="{$MOD.LBL_CANCEL_BUTTON_TITLE}"  onclick="document.location.href='index.php?module=Administration&action=index'" class="button"  type="button" name="cancel" value="  {$APP.LBL_CANCEL_BUTTON_LABEL}  " />
          </div>
          {$JAVASCRIPT}

Alternatively, you could compare the module:
module=Configurator&action=LogView
with the other legacy modules and build a fork for that and make the log file viewer a full legacy module.

Alexbmp · 27 April 2026 08:10

BastianHammer:

I’d challenge the real business requirement behind this request?

The log viewer only shows the suitecrm.log file - not the Suite 8 files, not the upgrade and not the installation. There isn’t an access to the web-servers log files as well.

I only use this in odd / specific cases, where the admin doesn’t have access to server and could do some ad hoc investigation. It’s often only a workaround.

Much better would be, to create a specific FTP / SSH user with access only to the logs directory - that would provide the whole picture + all features that cannot be provided by the UI easily (log streaming, file size, date time stamps, loading 100MB large log files etc.).

If it absolutely has to be a log view UI feature inside the CRM, it would probably be best to create a new module from scratch with the new logs as well.

Good morning,

First of all, thank you very much for your prompt responses.

Regarding your question, the need behind this request is quite simple: we are participating in a grant program where we must provide various pieces of evidence to demonstrate that we have been using our own CRM for some time, in our case, SuiteCRM.

To prove the use of the application, we are required to submit several screenshots showing activity and, most importantly, clearly identifying that the CRM belongs to us and is not taken from the internet or another company. For the rest of the screenshots, we have not encountered any issues, as the top navigation bar (navbar) displays the username, our URL (our domain) is visible, and we have also customized the application to include a header with our logo on all pages, as well as a footer with our logo.

The problem arises with the screenshot of the logs section. Initially, we submitted a screenshot accessing the logs via SSH, but this was not accepted because it could not be directly associated with the application (they required it to be shown from within the app itself). To address this, we added a company name prefix to every log entry and submitted a screenshot of the LogView section showing both the URL and the prefixed logs. However, this was also rejected because, although they acknowledged the improvement, they indicated that the navigation bar was not visible as it is in the other screenshots.

We understand that this requirement may seem somewhat unreasonable, as the URL and the prefix should be sufficient to associate it with the application. However, these are requirements imposed by the public authority, and we must comply with them.

For this reason, we are trying to find a way to include the navbar in the LogView section, as this is the only remaining requirement to obtain approval. In short, the only thing they are asking for is that the navigation bar be visible in this section, just like in the rest of the application.

Thank you very much in advance for all your help.

Best regards,

Alexbmp · 27 April 2026 11:22

Good afternoon,

In case this helps anyone, I was finally able to resolve the issue.

The root cause was that accessing the legacy URL directly (index.php?...) bypasses the Angular layer of SuiteCRM, which is responsible for rendering the navbar. In other words, it was going straight into the PHP backend without loading the full interface.

The solution was to modify the logs view access so that it goes through Angular (using the route /#/Configurator/LogView), allowing the application to properly load the navbar and then display the legacy view inside the iframe.

To achieve this, I:

Copied the relevant template into the custom/ directory to avoid modifying core files.
Updated the logs button URL to use the Angular route.
Adjusted file permissions so the web server could properly access them.
Ran a “Quick Repair and Rebuild” to clear the template cache.

With this change, the logs section now displays the navbar like the rest of the application.

Thank you all very much for your help.

Best regards,

BastianHammer · 27 April 2026 11:43

That sounds like a small ‘fix’ and low hanging fruit to add to the Github queue.
Do you want to open an issue and pointing out the solution?

Alexbmp · 27 April 2026 11:52

Yes, I will open an issue and try to describe it as clearly and in as much detail as possible.

On the other hand, I would like to thank you for all the help provided. I am quite new to SuiteCRM, and the support you have given both through the forum and your YouTube channel has been extremely helpful to me.

Best regards

BastianHammer · 27 April 2026 23:42

Thanks, glad that it worked out.