cancel
Showing results for 
Search instead for 
Did you mean: 
vg30
Sisense Team Member
Sisense Team Member

How to properly enable/disable plugins on the Sisense guide

The reason we have created this guide would be to increase the awareness of our customers on how to properly enable/disable plugins at Sisense to ensure that you are doing it properly to avoid potential issues when changes are not applied as expected and so long.

Steps to perform:

  1. Navigate to Sisense Admin -> Add-ons tab
  2. Based on the list of all plugins, you can enable or disable them by switching the toggle

vg30_0-1717440281480.png

 

  1. If you want to perform any actions against the specific plugin, for example, enable/disable switch the toggle and wait until the popup window appears as an example:

vg30_1-1717440281563.png

If you hit “Yes”, the plugin service will be restarted and all changes will take effect.

Otherwise, If you hit “No”, no changes will be performed.

An alternative way of disabling plugins, steps to perform:

  1. Navigate to your Sisense instance and open the dev tool in your browser
  2. Open the network tab and refresh the page to find an API request main.xxxx with the random hash,
    example below:

    vg30_2-1717440281630.png

     

  3. Select 'Block request URL', which means on the next page load, your browser would prevent plugin API from loading which prevents plugin code from being executed and you can use such an approach for troubleshooting.

Most common issues with Plugins, and why you want to perform changes from above:

  1. When you are experiencing any of the plugins not working as expected. You are getting the console JS error message, the support team might advise you to isolate the issue to the specific plugin, so you would need to start disabling plugins 1 by 1 to check If the issue still exists. None of the plugins are conflicting with each other.
  2. When some of the basic Sisense functionality is not working as expected, could be related to the issue with plugins or custom plugins, due to some plugin code is no longer compatible or up to date, or the plugin itself is causing the issue which is preventing default Sisense logic from execution.
Rate this article:
(1)
Version history
Last update:
‎07-10-2024 07:00 AM
Updated by:
Contributors