We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 30498
    • 30 Posts
    While trying to upgrade from 2.3.2pl (advanced) to 2.4.0 i'm receiving the following error messages:

    Error updating table for class transport.modTransportProvider
    Array
    (
    [0] => 00000
    [1] =>
    [2] =>
    )
    
    Error updating table for class transport.modTransportProvider
    Array
    (
    [0] => 00000
    [1] =>
    [2] =>
    )
    
    Error updating table for class transport.modTransportProvider
    Array
    (
    [0] => 00000
    [1] =>
    [2] =>
    )
    
    Error updating table for class modCategory
    Array
    (
    [0] => 00000
    [1] =>
    [2] =>
    )
    
    Error updating table for class modCategory
    Array
    (
    [0] => 00000
    [1] =>
    [2] =>
    )
    
    Error creating table for class modAccessNamespace
    
    Successfully upgraded table for class modAccessResourceGroup
    Dropped index `principal_class` on table ``modx_access_resource_groups``.
    
    Successfully upgraded table for class modAccessResourceGroup
    Added new index on `principal_class` for table ``modx_access_resource_groups``.
    
    Error updating table for class modTemplateVarResourceGroup
    Array
    (
    [0] => 00000
    [1] =>
    [2] =>
    )
    
    Error updating table for class modManagerLog
    Array
    (
    [0] => 00000
    [1] =>
    [2] =>
    )
    


    When clicking "try again" or "go back" the browser shows no output at all, also both the front end and the manager aren't outputting anything.

    Any ideas what might be causing this?


    Edit: I was logged out of the manager, sessions destroyed and core/cache emptied. Update zipfile was extracted at the server.
      • 36763
      • 70 Posts
      I had similar results too. I got the following error message:

      Error updating table for class modManagerLog Array ( [0] => 00000 )


      So, then, silly me did a 'back' on the browser... and it wiped the config file to just placeholders - this:
      I'm guessing I should have just clicked on "finish" or "complete" or whatever the last stage in the upgrade is.

      <?php
      /**
       *  MODX Configuration file
       */
      $database_type = '{database_type}';
      $database_server = '{database_server}';
      $database_user = '{database_user}';
      $database_password = '';
      $database_connection_charset = '{database_connection_charset}';
      $dbase = '{dbase}';
      $table_prefix = '{table_prefix}';
      $database_dsn = '{database_dsn}';
      $config_options = {config_options};
      $driver_options = {driver_options};
      
      $lastInstallTime = 1442533676;
      
      $site_id = 'modx55fb512cb82526.66868457';
      $site_sessionname = '{site_sessionname}';
      $https_port = '{https_port}';
      $uuid = 'f9e0500e-9387-4e86-af5e-b9630a804dbc';
      
      if (!defined('MODX_CORE_PATH')) {
          $modx_core_path= '{core_path}';
          define('MODX_CORE_PATH', $modx_core_path);
      }
      if (!defined('MODX_PROCESSORS_PATH')) {
          $modx_processors_path= '{processors_path}';
          define('MODX_PROCESSORS_PATH', $modx_processors_path);
      }
      if (!defined('MODX_CONNECTORS_PATH')) {
          $modx_connectors_path= '{connectors_path}';
          $modx_connectors_url= '{connectors_url}';
          define('MODX_CONNECTORS_PATH', $modx_connectors_path);
          define('MODX_CONNECTORS_URL', $modx_connectors_url);
      }
      if (!defined('MODX_MANAGER_PATH')) {
          $modx_manager_path= '{mgr_path}';
          $modx_manager_url= '{mgr_url}';
          define('MODX_MANAGER_PATH', $modx_manager_path);
          define('MODX_MANAGER_URL', $modx_manager_url);
      }
      if (!defined('MODX_BASE_PATH')) {
          $modx_base_path= '{web_path}';
          $modx_base_url= '{web_url}';
          define('MODX_BASE_PATH', $modx_base_path);
          define('MODX_BASE_URL', $modx_base_url);
      }
      if(defined('PHP_SAPI') && (PHP_SAPI == "cli" || PHP_SAPI == "embed")) {
          $isSecureRequest = false;
      } else {
          $isSecureRequest = ((isset ($_SERVER['HTTPS']) && strtolower($_SERVER['HTTPS']) == 'on') || $_SERVER['SERVER_PORT'] == $https_port);
      }
      if (!defined('MODX_URL_SCHEME')) {
          $url_scheme=  $isSecureRequest ? 'https://' : 'http://';
          define('MODX_URL_SCHEME', $url_scheme);
      }
      if (!defined('MODX_HTTP_HOST')) {
          if(defined('PHP_SAPI') && (PHP_SAPI == "cli" || PHP_SAPI == "embed")) {
              $http_host='{http_host}';
              define('MODX_HTTP_HOST', $http_host);
          } else {
              $http_host= array_key_exists('HTTP_HOST', $_SERVER) ? $_SERVER['HTTP_HOST'] : '{http_host}';
              if ($_SERVER['SERVER_PORT'] != 80) {
                  $http_host= str_replace(':' . $_SERVER['SERVER_PORT'], '', $http_host); // remove port from HTTP_HOST
              }
              $http_host .= ($_SERVER['SERVER_PORT'] == 80 || $isSecureRequest) ? '' : ':' . $_SERVER['SERVER_PORT'];
              define('MODX_HTTP_HOST', $http_host);
          }
      }
      if (!defined('MODX_SITE_URL')) {
          $site_url= $url_scheme . $http_host . MODX_BASE_URL;
          define('MODX_SITE_URL', $site_url);
      }
      if (!defined('MODX_ASSETS_PATH')) {
          $modx_assets_path= '{assets_path}';
          $modx_assets_url= '{assets_url}';
          define('MODX_ASSETS_PATH', $modx_assets_path);
          define('MODX_ASSETS_URL', $modx_assets_url);
      }
      if (!defined('MODX_LOG_LEVEL_FATAL')) {
          define('MODX_LOG_LEVEL_FATAL', 0);
          define('MODX_LOG_LEVEL_ERROR', 1);
          define('MODX_LOG_LEVEL_WARN', 2);
          define('MODX_LOG_LEVEL_INFO', 3);
          define('MODX_LOG_LEVEL_DEBUG', 4);
      }
      if (!defined('MODX_CACHE_DISABLED')) {
          $modx_cache_disabled= {cache_disabled};
          define('MODX_CACHE_DISABLED', $modx_cache_disabled);
      }
      


      I should have backed up the config file. Doh! So now I'm reinstalling the site because something has broken.
        • 3749
        • 24,544 Posts
        Were those error messages in red? If not, they should be ignored and you should proceed with the setup.

        The fact that the 'back' button trashes the config file should be reported as a bug.
          Did I help you? Buy me a beer
          Get my Book: MODX:The Official Guide
          MODX info for everyone: http://bobsguides.com/modx.html
          My MODX Extras
          Bob's Guides is now hosted at A2 MODX Hosting
          • 36763
          • 70 Posts
          I think mine was red, but as warnings. Either way, I'd have to try and see if the bug was repeatable... and that I'm not too keen on right at this point. haha
            • 3749
            • 24,544 Posts
            I can't blame you, but it would still be great if you reported the bug at GitHub. It should be easy for the team to reproduce if it's a real bug (and I suspect that it is).
              Did I help you? Buy me a beer
              Get my Book: MODX:The Official Guide
              MODX info for everyone: http://bobsguides.com/modx.html
              My MODX Extras
              Bob's Guides is now hosted at A2 MODX Hosting
              • 43957
              • 79 Posts
              I'm getting this error in red when I try and update.

              I was on 2.3.1pl and went to 2.3.2pl using upgradeModx package, but then tried to go from 2.3.2pl to 2.4.0pl as recommended by Bob here:https://forums.modx.com/thread/100511/issue-with-upgrademodx-migration-from-2-3-2-to-2-5#dis-post-543157

              Error updating table for class modManagerLog
              Array
              (
              [0] => 00000
              [1] =>
              [2] =>
              )


              I've got captcha on the manager page, but when I try and log in with 2.4.0pl I just get a "1" returned and it doesn't log me in.

              I've been desperately trying to upgrade to 2.5, but everything try seems to fail in some way. :-(

              Any help would be greatly appreciated.
                • 36763
                • 70 Posts
                Quote from: dave-b at Jul 25, 2016, 02:30 PM
                I'm getting this error in red when I try and update.

                I was on 2.3.1pl and went to 2.3.2pl using upgradeModx package, but then tried to go from 2.3.2pl to 2.4.0pl as recommended by Bob here:https://forums.modx.com/thread/100511/issue-with-upgrademodx-migration-from-2-3-2-to-2-5#dis-post-543157

                Error updating table for class modManagerLog
                Array
                (
                [0] => 00000
                [1] =>
                [2] =>
                )


                I've got captcha on the manager page, but when I try and log in with 2.4.0pl I just get a "1" returned and it doesn't log me in.

                I've been desperately trying to upgrade to 2.5, but everything try seems to fail in some way. :-(

                Any help would be greatly appreciated.


                I hate to say the obvious, but have you tried clearing out the cache path? That may solve your issue.
                I think at one stage I had to do some database hacks and remove an item from the dashboard of my user once too, because of things like this. I can't remember the exact thing I did though. Sorry to be vague, but it may either help, or hinder...
                  • 3749
                  • 24,544 Posts
                  UpgradeMODX clears all the cache files for you, so that's not it, but sometimes something left over in the browser cache or cookies will mess up the Manager. If you use private or incognito mode in your browser and that solves the problem, it's definitely a browser issue.


                  For not, try turning off Captcha:

                  Go into the database in PhpMyAdmin and in the modx_system_settings table, find the captcha.enabled setting and set the value to zero, then click on the "go" button.

                  Delete all files in the core/cache directory before logging in.

                  If don't have access to the DB, you can edit the core/cache/system_settings/config.cache.php file and change the value of captcha.enabled to '0', then save the file.

                  As soon as you log in, go immediately to System Settings and turn off the captcha.enabled Setting. Log out, delete the core/cache/system_settings/config.cache.php file, and log back in.
                    Did I help you? Buy me a beer
                    Get my Book: MODX:The Official Guide
                    MODX info for everyone: http://bobsguides.com/modx.html
                    My MODX Extras
                    Bob's Guides is now hosted at A2 MODX Hosting