by synolia

Create standardized dashboards for your users. No more having confused users missing out on what they could be doing with Sugar. This add-on gives Sugar administrators the ability to easily and quickly deploy dashboard templates to one or multiple users.

Includes a 30 day guarantee
Try it Now

By clicking you consent to be contacted by the developer

#3139 - Uninstall Completely

Closed Bug? created by lowen Verified Purchase 4 years ago

Hi there, i no longer have "support" to get the latest updates for 7.8 or 7.9. I'm stuck in 7.7 but cannot upgrade due to failures in the upgrade log. I have removed it as a module (uninstalled in module builder) done all the usual repairs but its still complaining about files in certain folders being incompatible. I've tried removing these files and it just kills my sugar environment. Is there something you can do to help me remove it completely?

  1. synolia member avatar

    synolia Provider Affiliate

    4 years ago

    Hello,

    Can you please tell us the files that block your upgrade and also can you specify the version of the Dashboard Templates module you are using?

    Kind regards, Synolia Support

  2. lowen member avatar

    lowen Verified Purchase

    4 years ago

    Hi there, Dashboard Templates V: 7.2.2-to-7.7_20170223 and here is the output from the upgrade log:~Thu, 08 Jun 2017 13:39:34 +0100 [Upgrader] - => C: [Issue 64][green][notStockModule][201][SYNO_DashboardTemplateFilters is not a stock module] Studio customizations were detected on your instance. We do not anticipate any problems with these customization and your customizations can be upgraded to Sugar7. Thu, 08 Jun 2017 13:39:34 +0100 [Upgrader] - => C: [Issue 65][green][notStockModule][201][SYNO_DashboardTemplateHistory is not a stock module] Studio customizations were detected on your instance. We do not anticipate any problems with these customization and your customizations can be upgraded to Sugar7. Thu, 08 Jun 2017 13:39:34 +0100 [Upgrader] - => C: [Issue 66][green][notStockModule][201][SYNO_DashboardTemplateLines is not a stock module] Studio customizations were detected on your instance. We do not anticipate any problems with these customization and your customizations can be upgraded to Sugar7. Thu, 08 Jun 2017 13:39:34 +0100 [Upgrader] - => C: [Issue 67][green][notStockModule][201][SYNO_DashboardTemplates is not a stock module] Studio customizations were detected on your instance. We do not anticipate any problems with these customization and your customizations can be upgraded to Sugar7. Thu, 08 Jun 2017 13:39:34 +0100 [Upgrader] - => D: [Issue 68][yellow][isNotMBModule][304][Unknown files: modules/SYNO_DashboardTemplates/SYNO_Dashboard.php modules/SYNO_DashboardTemplates/SYNO_DashboardHelpers.php modules/SYNO_DashboardTemplates/SYNO_DashboardLogicHooks.php - SYNO_DashboardTemplates is not MB module] Unknown files (modules/SYNO_DashboardTemplates/SYNO_Dashboard.php modules/SYNO_DashboardTemplates/SYNO_DashboardHelpers.php modules/SYNO_DashboardTemplates/SYNO_DashboardLogicHooks.php) were detected and were not migrated to Sugar7. This module (SYNO_DashboardTemplates) will continue to be available but it will be run in Backwards Compatibility Mode on Sugar7. Thu, 08 Jun 2017 13:39:34 +0100 [Upgrader] - => D: [Issue 69][yellow][toBeRunAsBWC][301][SYNO_DashboardTemplates to be run as BWC] Certain customizations were detected and were not migrated to Sugar7. This module (SYNO_DashboardTemplates) will continue to be available but it will be run in Backwards Compatibility Mode on Sugar7. Thu, 08 Jun 2017 13:39:34 +0100 [Upgrader] - => B: [Issue 70][green][hasExtensions][102][Schedulers has extensions: custom/Extension/modules/Schedulers/Ext/Language/en_us.SUGAR_SYNODASHBOARDTEMPLATES.php custom/Extension/modules/Schedulers/Ext/Language/fr_FR.SUGAR_SYNODASHBOARDTEMPLATES.php custom/Extension/modules/Schedulers/Ext/ScheduledTasks/SynoliaDTUpdateUsersRolesField.php custom/Extension/modules/Schedulers/Ext/ScheduledTasks/SynoliaDTUpdateRolesDropdown.php] Studio customizations were detected on your instance. We do not anticipate any problems with these customization and your customizations can be upgraded to Sugar7. Thu, 08 Jun 2017 13:39:34 +0100 [Upgrader] - => B: [Issue 71][green][hasExtensions][102][Tasks has extensions: custom/Extension/modules/Tasks/Ext/Vardefs/full_text_search_admin.php] Studio customizations were detected on your instance. We do not anticipate any problems with these customization and your customizations can be upgraded to Sugar7. Thu, 08 Jun 2017 13:39:34 +0100 [Upgrader] - => B: [Issue 72][green][hasCustomVardefs][103][Tasks has custom vardefs] Studio customizations were detected on your instance. We do not anticipate any problems with these customization and your customizations can be upgraded to Sugar7. Thu, 08 Jun 2017 13:39:34 +0100 [Upgrader] - => B: [Issue 73][green][hasStudioHistory][101][Users has studio history] Studio customizations were detected on your instance. We do not anticipate any problems with these customization and your customizations can be upgraded to Sugar7. Thu, 08 Jun 2017 13:39:34 +0100 [Upgrader] - => B: [Issue 74][green][hasExtensions][102][Users has extensions: custom/Extension/modules/Users/Ext/Vardefs/sugarfield_synodt_block_dashboards_c.php custom/Extension/modules/Users/Ext/Vardefs/SUGAR_SYNODASHBOARDTEMPLATES.php custom/Extension/modules/Users/Ext/Vardefs/sugarfield_users_job_role_c.php custom/Extension/modules/Users/Ext/Vardefs/sugarfield_synodt_roles_c.php custom/Extension/modules/Users/Ext/Language/en_UK.lang.php custom/Extension/modules/Users/Ext/Language/fr_FR.SynoDashboardTemplatesHistory.php custom/Extension/modules/Users/Ext/Language/en_us.SynoDashboardTemplatesHistory.php custom/Extension/modules/Users/Ext/Language/en_us.SUGAR_SYNODASHBOARDTEMPLATES.php custom/Extension/modules/Users/Ext/Language/en_us.sugarcrm_sudo_login.php custom/Extension/modules/Users/Ext/Language/fr_FR.SUGAR_SYNODASHBOARDTEMPLATES.php] Studio customizations were detected on your instance. We do not anticipate any problems with these customization and your customizations can be upgraded to Sugar7. Thu, 08 Jun 2017 13:39:34 +0100 [Upgrader] - => B: [Issue 75][green][hasCustomVardefs][103][Users has custom vardefs] Studio customizations were detected on your instance. We do not anticipate any problems with these customization and your customizations can be upgraded to Sugar7. Thu, 08 Jun 2017 13:39:34 +0100 [Upgrader] - => B: [Issue 76][green][hasCustomViewdefs][105][Users has custom viewdefs] Studio customizations were detected on your instance. We do not anticipate any problems with these customization and your customizations can be upgraded to Sugar7. Thu, 08 Jun 2017 13:39:34 +0100 [Upgrader] - => F: [Issue 77][red][useOfAppViewInvokeParent][562][useOfAppViewInvokeParent] Use of removed Sidecar app.view.invokeParent method in modules/SYNO_DashboardTemplates/clients/base/fields/syno-dashboard-load-data/syno-dashboard-load-data.js Thu, 08 Jun 2017 13:39:34 +0100 [Upgrader] - => E: [Issue 78][yellow][stockPhp4ConstructorCall][532][Stock parent PHP4 constructor call in modules/SYNO_DashboardTemplateLines/Dashlets/SYNO_DashboardTemplateLinesDashlet/SYNO_DashboardTemplateLinesDashlet.php] A class declared in modules/SYNO_DashboardTemplateLines/Dashlets/SYNO_DashboardTemplateLinesDashlet/SYNO_DashboardTemplateLinesDashlet.php calls its stock parent's constructor as parent::DashletGeneric() Thu, 08 Jun 2017 13:39:34 +0100 [Upgrader] - => E: [Issue 79][yellow][stockPhp4ConstructorCall][532][Stock parent PHP4 constructor call in modules/SYNO_DashboardTemplateHistory/Dashlets/SYNO_DashboardTemplateHistoryDashlet/SYNO_DashboardTemplateHistoryDashlet.php] A class declared in modules/SYNO_DashboardTemplateHistory/Dashlets/SYNO_DashboardTemplateHistoryDashlet/SYNO_DashboardTemplateHistoryDashlet.php calls its stock parent's constructor as parent::DashletGeneric() Thu, 08 Jun 2017 13:39:34 +0100 [Upgrader] - => E: [Issue 80][yellow][stockPhp4ConstructorCall][532][Stock parent PHP4 constructor call in modules/SYNO_DashboardTemplateFilters/Dashlets/SYNO_DashboardTemplateFiltersDashlet/SYNO_DashboardTemplateFiltersDashlet.php] A class declared in modules/SYNO_DashboardTemplateFilters/Dashlets/SYNO_DashboardTemplateFiltersDashlet/SYNO_DashboardTemplateFiltersDashlet.php calls its stock parent's constructor as parent::DashletGeneric() Thu, 08 Jun 2017 13:39:34 +0100 [Upgrader] - => E: [Issue 81][yellow][stockPhp4ConstructorCall][532][Stock parent PHP4 constructor call in modules/SYNO_DashboardTemplates/Dashlets/SYNO_DashboardTemplatesDashlet/SYNO_DashboardTemplatesDashlet.php] A class declared in modules/SYNO_DashboardTemplates/Dashlets/SYNO_DashboardTemplatesDashlet/SYNO_DashboardTemplatesDashlet.php calls its stock parent's constructor as parent::DashletGeneric() Thu, 08 Jun 2017 13:39:34 +0100 [Upgrader] - *** END HEALTHCHECK ISSUES ***~

    • synolia member avatar

      synolia Provider Affiliate

      4 years ago

      Hello,

      Did you uninstall the add-on through the module loader and no by the module builder? If you perform that action that must delete these directories. It that didn't happen, please check your file permissions on your server.

      Best regards,

    • lowen member avatar

      lowen Verified Purchase

      4 years ago

      Hi there, i removed it with module loader. File permissions are ok...? other modules have removed fine

    • synolia member avatar

      synolia Provider Affiliate

      4 years ago

      Hello,

      Usually all files are removed when you perform the uninstall by the module loader, especially the files under modules directory. If that didn't happen the only way is to remove all files manually unfortunately.

      Best regards,

    • lowen member avatar

      lowen Verified Purchase

      4 years ago

      That's fine but when i've tried that previously the environment just dies... i could send error log after removing the files if you like?

    • synolia member avatar

      synolia Provider Affiliate

      4 years ago

      Hello,

      It's not an easy step, you need to remove all files without exceptions and perform a quick repair and rebuild to apply that.

      Best regards,

    • lowen member avatar

      lowen Verified Purchase

      4 years ago

      How would be best to approach that? What order should i remove files in?

    • synolia member avatar

      synolia Provider Affiliate

      4 years ago

      Hello,

      The best way is to check all files available in the package (zip file) and remove them one by one.

      Best regards,

  3. Tmoriello member avatar

    Tmoriello Verified Purchase

    4 years ago

    Iowen I'm having the same exact problem. Cant upgrade to 7.8 and cant uninstall. Every time I try to remove from module loader it kills my instance and just says "HTTP 500 error" and its unrecoverable. I've tried taking all of the files from the manifest (with a little excel trickery since there are so many files), adding them to a bash file with rm and running a script manually.

    I an confirm through logging in my script that every file in the manifest is deleted (no longer exists) but this plugin still leaves behind a LOT of data. It still leaves directories and some random files behind as well as auto generated ext.php files that it does not clean up itself. I've looked through the manifest file and they included a "post_execute" php file but never included a pre_uninstall or post_uninstall PHP cleanup script which I am assuming is the root of all these problems.

    Assuming you are on Linux, you have a lot of work ahead of you. Uninstall through module loader which will hard crash your system. This is inevitable. Now comes the hard parts:

    Delete the 4 SYNO directories in /modules/Syno~~~~~ Delete the 4 SYNO directories in /custom/modules/Syno~~~~~~~ Try to load your instance. It will fail. Check your HTTPD error logs. Look for entries like below PHP Fatal error: require_once(): Failed opening required 'modules/SYNO_DashboardTemplates/SYNO_DashboardTemplates.php'

    Now the fun REALLY starts. It may take you an hour or so, but you need to start running GREP's on the files/directories that appear in your HTTP error log. There will be a lot but unfortunately HTTPD kills after the first fail. This is a multi step process.

    Here's one first such example:

    grep -rl 'modules/SYNO_DashboardTemplates/SYNO_DashboardTemplates.php'

    One such auto generated file you will probably find not cleaned up is -> /custom/application/Ext/Include/modules.ext.php

    You'll notice that there are a TON of references to files that were supposed to be "uninstalled". Whenever you see a "//Merged from custom/Extension........." leave that comment alone. You might need it later. Delete all the real code that has "SYNO" anywhere in it and leave the comments in place. After you've deleted all of the code, traverse your directory structure and make sure that the files that were referenced as "//Merged from" have been deleted.

    Here's what is left behind in my /custom/application/Ext/Include/modules.ext.php after an "uninstall"

    <?php
    // Merged from custom/Extension/application/Ext/Include/SYNO_DashboardTemplateHistory.php
    
    
    $beanList[&#039;SYNO_DashboardTemplateHistory&#039;] = &#039;SYNO_DashboardTemplateHistory&#039;;
    $beanFiles[&#039;SYNO_DashboardTemplateHistory&#039;] = &#039;modules/SYNO_DashboardTemplateHistory/SYNO_DashboardTemplateHistory.php&#039;;
    $modules_exempt_from_availability_check[&#039;SYNO_DashboardTemplateHistory&#039;] = &#039;SYNO_DashboardTemplateHistory&#039;;
    $report_include_modules[&#039;SYNO_DashboardTemplateHistory&#039;] = &#039;SYNO_DashboardTemplateHistory&#039;;
    $modInvisList[] = &#039;SYNO_DashboardTemplateHistory&#039;;
    
    ?>
    <?php
    // Merged from custom/Extension/application/Ext/Include/DashboardTemplates.php
    
     //WARNING: The contents of this file are auto-generated
    $beanList[&#039;SYNO_DashboardTemplates&#039;] = &#039;SYNO_DashboardTemplates&#039;;
    $beanFiles[&#039;SYNO_DashboardTemplates&#039;] = &#039;modules/SYNO_DashboardTemplates/SYNO_DashboardTemplates.php&#039;;
    $modules_exempt_from_availability_check[&#039;SYNO_DashboardTemplates&#039;] = &#039;SYNO_DashboardTemplates&#039;;
    $report_include_modules[&#039;SYNO_DashboardTemplates&#039;] = &#039;SYNO_DashboardTemplates&#039;;
    $modInvisList[] = &#039;SYNO_DashboardTemplates&#039;;
    
    ?>
    <?php
    // Merged from custom/Extension/application/Ext/Include/SynoDashboardTemplateFilters.php
    
     //WARNING: The contents of this file are auto-generated
    $beanList[&#039;SYNO_DashboardTemplateFilters&#039;] = &#039;SYNO_DashboardTemplateFilters&#039;;
    $beanFiles[&#039;SYNO_DashboardTemplateFilters&#039;] = &#039;modules/SYNO_DashboardTemplateFilters/SYNO_DashboardTemplateFilters.php&#039;;
    $modules_exempt_from_availability_check[&#039;SYNO_DashboardTemplateFilters&#039;] = &#039;SYNO_DashboardTemplateFilters&#039;;
    $report_include_modules[&#039;SYNO_DashboardTemplateFilters&#039;] = &#039;SYNO_DashboardTemplateFilters&#039;;
    $modInvisList[] = &#039;SYNO_DashboardTemplateFilters&#039;;
    
    ?>
    <?php
    // Merged from custom/Extension/application/Ext/Include/SynoDashboardTemplateLines.php
    
     //WARNING: The contents of this file are auto-generated
    $beanList[&#039;SYNO_DashboardTemplateLines&#039;] = &#039;SYNO_DashboardTemplateLines&#039;;
    $beanFiles[&#039;SYNO_DashboardTemplateLines&#039;] = &#039;modules/SYNO_DashboardTemplateLines/SYNO_DashboardTemplateLines.php&#039;;
    $modules_exempt_from_availability_check[&#039;SYNO_DashboardTemplateLines&#039;] = &#039;SYNO_DashboardTemplateLines&#039;;
    $report_include_modules[&#039;SYNO_DashboardTemplateLines&#039;] = &#039;SYNO_DashboardTemplateLines&#039;;
    $modInvisList[] = &#039;SYNO_DashboardTemplateLines&#039;;
    
    ?>
    <?php
    // Merged from custom/Extension/application/Ext/Include/sugar-synodashboardtemplates.php
    
     //WARNING: The contents of this file are auto-generated
    $beanList[&#039;SYNO_DashboardTemplateFilters&#039;] = &#039;SYNO_DashboardTemplateFilters&#039;;
    $beanFiles[&#039;SYNO_DashboardTemplateFilters&#039;] = &#039;modules/SYNO_DashboardTemplateFilters/SYNO_DashboardTemplateFilters.php&#039;;
    $modules_exempt_from_availability_check[&#039;SYNO_DashboardTemplateFilters&#039;] = &#039;SYNO_DashboardTemplateFilters&#039;;
    $report_include_modules[&#039;SYNO_DashboardTemplateFilters&#039;] = &#039;SYNO_DashboardTemplateFilters&#039;;
    $modInvisList[] = &#039;SYNO_DashboardTemplateFilters&#039;;
    $beanList[&#039;SYNO_DashboardTemplateHistory&#039;] = &#039;SYNO_DashboardTemplateHistory&#039;;
    $beanFiles[&#039;SYNO_DashboardTemplateHistory&#039;] = &#039;modules/SYNO_DashboardTemplateHistory/SYNO_DashboardTemplateHistory.php&#039;;
    $modules_exempt_from_availability_check[&#039;SYNO_DashboardTemplateHistory&#039;] = &#039;SYNO_DashboardTemplateHistory&#039;;
    $report_include_modules[&#039;SYNO_DashboardTemplateHistory&#039;] = &#039;SYNO_DashboardTemplateHistory&#039;;
    $modInvisList[] = &#039;SYNO_DashboardTemplateHistory&#039;;
    $beanList[&#039;SYNO_DashboardTemplateLines&#039;] = &#039;SYNO_DashboardTemplateLines&#039;;
    $beanFiles[&#039;SYNO_DashboardTemplateLines&#039;] = &#039;modules/SYNO_DashboardTemplateLines/SYNO_DashboardTemplateLines.php&#039;;
    $modules_exempt_from_availability_check[&#039;SYNO_DashboardTemplateLines&#039;] = &#039;SYNO_DashboardTemplateLines&#039;;
    $report_include_modules[&#039;SYNO_DashboardTemplateLines&#039;] = &#039;SYNO_DashboardTemplateLines&#039;;
    $modInvisList[] = &#039;SYNO_DashboardTemplateLines&#039;;
    $beanList[&#039;SYNO_DashboardTemplates&#039;] = &#039;SYNO_DashboardTemplates&#039;;
    $beanFiles[&#039;SYNO_DashboardTemplates&#039;] = &#039;modules/SYNO_DashboardTemplates/SYNO_DashboardTemplates.php&#039;;
    $modules_exempt_from_availability_check[&#039;SYNO_DashboardTemplates&#039;] = &#039;SYNO_DashboardTemplates&#039;;
    $report_include_modules[&#039;SYNO_DashboardTemplates&#039;] = &#039;SYNO_DashboardTemplates&#039;;
    $modInvisList[] = &#039;SYNO_DashboardTemplates&#039;;
    
    
    ?>
    

    Once you are done and removed all code and referenced files, reload your instance again. You'll see more HTTPD FAIL errors. Repeat the process. Kill everything that has SYNO on it. Eventually, you will remove all of the files that SYNO killed your system with. It is going to take a long time, but eventually after a whole bunch of GREPing, hand deleting SYNO Spaghetti code, and running repairs, your instance will come back to life.

    I've done it twice now and it sucks, but SYNO hasnt been much help. Good luck to you!

    Here is also a useful script that you can run a Quick Rebuild and Repair from the command line. name it "repair.php", place it in your sugar root directory and make it executable, then run it by traversing to your directory and running "php repair.php"

    #!/usr/bin/php
    <?php
    
    /*
     * Copyright 2013
     * Jeff Bickart
     * @bickart
     * jeff @ neposystems.com
     */
    
    if(!defined(&#039;sugarEntry&#039;))define(&#039;sugarEntry&#039;, true);
    
    require_once(&#039;include/entryPoint.php&#039;);
    require_once(&#039;modules/Administration/QuickRepairAndRebuild.php&#039;);
    
    //Bug 27991 . Redirect to index.php if the request is not come from CLI.
    $sapi_type = php_sapi_name();
    if (substr($sapi_type, 0, 3) != &#039;cgi&#039;) {
        global $sugar_config;
      if(!empty($sugar_config[&#039;site_url&#039;])){
            header("Location: ".$sugar_config[&#039;site_url&#039;] . "/index.php");
        }else{
            sugar_die("Didn&#039;t find site url in your sugarcrm config file");
        }
    }
    //End of #27991
    
    if(empty($current_language)) {
        $current_language = $sugar_config[&#039;default_language&#039;];
    }
    
    $app_list_strings = return_app_list_strings_language($current_language);
    $app_strings = return_application_language($current_language);
    
    global $current_user;
    $current_user = new User();
    $current_user->getSystemUser();
    
    $GLOBALS[&#039;log&#039;]->debug(&#039;--------------------------------------------> at repair.php <--------------------------------------------&#039;);
    $repair = new RepairAndClear();
    $repair->repairAndClearAll(array(&#039;clearAll&#039;),array(translate(&#039;LBL_ALL_MODULES&#039;)), true,false);
    
    $exit_on_cleanup = true;
    
    sugar_cleanup(false);
    
    // some jobs have annoying habit of calling sugar_cleanup(), and it can be called only once
    // but job results can be written to DB after job is finished, so we have to disconnect here again
    // just in case we couldn&#039;t call cleanup
    if(class_exists(&#039;DBManagerFactory&#039;)) {
        $db = DBManagerFactory::getInstance();
        $db->disconnect();
    }
    
    if($exit_on_cleanup) exit;
    
    • Tmoriello member avatar

      Tmoriello Verified Purchase

      4 years ago

      Sorry also keep clearing your cache directory after ever time you remove SYNO code. rm -rf /cache/*

      The asterisk is VERY important. It will clear the contents of the cache directory but leave the cache directory there. alternatively you cna just remove the contents of the cache directory through a program like WINSCP. Just dont delete the cache directory itself.

    • lowen member avatar

      lowen Verified Purchase

      4 years ago

      Thank you so much! That worked. Took a while to get through all the files but works again once done. More help than anyone at Synolia! not using them again.

This case is public. Please leave out any sensitive information such as URLs, passwords, etc.
Saving Comment Saving Comment...
  • "This module is a lifesaver. 25 staff all needing the same styles would have been a nightmare to do individually.You only need to create the dashboards on one and then push them out."

    Read More Reviews