We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 54735
    • 12 Posts
    During our Upgrade from 2.5.7 to 2.6.5 the setup created the following errors:

    (ERROR @ .../user/htdocs/core/xpdo/transport/xpdovehicle.class.php : 181) Could not copy .../user/htdocs/core/packages/core/modContext/457ca7a0b0eaefc2ca1c7c6e01be469a/0/ to .../user/htdocs/index.php
    (ERROR @ .../user/htdocs/core/xpdo/transport/xpdovehicle.class.php : 181) Could not copy .../user/htdocs/core/packages/core/modContext/457ca7a0b0eaefc2ca1c7c6e01be469a/1/ to .../user/htdocs/ht.access
    (ERROR @ .../user/htdocs/core/xpdo/transport/xpdovehicle.class.php : 181) Could not copy .../user/htdocs/core/packages/core/modContext/55899c07a0be09d324666a6a7964aa95/0/ to .../user/htdocs/manager/assets
    (ERROR @ .../user/htdocs/core/xpdo/transport/xpdovehicle.class.php : 181) Could not copy .../user/htdocs/core/packages/core/modContext/55899c07a0be09d324666a6a7964aa95/1/ to .../user/htdocs/manager/controllers
    (ERROR @ .../user/htdocs/core/xpdo/transport/xpdovehicle.class.php : 181) Could not copy .../user/htdocs/core/packages/core/modContext/55899c07a0be09d324666a6a7964aa95/2/ to .../user/htdocs/manager/templates
    (ERROR @ .../user/htdocs/core/xpdo/transport/xpdovehicle.class.php : 181) Could not copy .../user/htdocs/core/packages/core/modContext/55899c07a0be09d324666a6a7964aa95/3/ to .../user/htdocs/manager/min
    (ERROR @ .../user/htdocs/core/xpdo/transport/xpdovehicle.class.php : 181) Could not copy .../user/htdocs/core/packages/core/modContext/55899c07a0be09d324666a6a7964aa95/4/ to .../user/htdocs/manager/ht.access
    (ERROR @ .../user/htdocs/core/xpdo/transport/xpdovehicle.class.php : 181) Could not copy .../user/htdocs/core/packages/core/modContext/55899c07a0be09d324666a6a7964aa95/5/ to .../user/htdocs/manager/index.php
    (ERROR @ .../user/htdocs/core/xpdo/transport/xpdofilevehicle.class.php : 103) Could not install files from .../user/htdocs/core/packages/core/xPDOFileVehicle/ffa5502778b3fb87d28d02f45d927841/ to .../user/htdocs/connectors/
    (ERROR @ .../user/htdocs/core/xpdo/transport/xpdofilevehicle.class.php : 103) Could not install files from .../user/htdocs/core/packages/core/xPDOFileVehicle/1149241767cb39815df8fc2114a9936f/ to .../user/htdocs/connectors/
    (ERROR @ .../user/htdocs/core/xpdo/transport/xpdofilevehicle.class.php : 103) Could not install files from .../user/htdocs/core/packages/core/xPDOFileVehicle/abadc8773bbd03d54796490a67534a63/ to .../user/htdocs/connectors/
    (ERROR @ .../user/htdocs/core/xpdo/transport/xpdofilevehicle.class.php : 103) Could not install files from .../user/htdocs/core/packages/core/xPDOFileVehicle/229a573898f3733982f59f406bed73e1/ to .../user/htdocs/connectors/
    All these long digits and characters directories are not existing but files. And therefore no subdirectories, neither.

    For example, in modContext instead of a directory called "457ca7a0b0eaefc2ca1c7c6e01be469a/" there are two files:
    '457ca7a0b0eaefc2ca1c7c6e01be469a.resolve.core.resolver' and '457ca7a0b0eaefc2ca1c7c6e01be469a.vehicle'!

    For example, in xPDOFileVehicle instead of a directory called "229a573898f3733982f59f406bed73e1/" there are two or one files:
    '229a573898f3733982f59f406bed73e1.resolve.core.resolver' and '229a573898f3733982f59f406bed73e1.vehicle' ... or just a "*.vehicle" file!

    All perms are set to 755/644.

    --> As a consequence our web server performs quite badly and becomes unreachable after a while.

    In the first eight cases (xpdovehicle.class.php) the corresponding program snippet looks like the following:

     156             switch ($options[xPDOTransport::PACKAGE_ACTION]) {
     157                              case xPDOTransport::ACTION_UPGRADE:
     158                              case xPDOTransport::ACTION_INSTALL: // if package is installing
     159                                  if ($cacheManager && file_exists($fileSource) && !empty ($fileTarget)) {
     160                                      $copied = array();
     161                                      if ($preExistingMode === xPDOTransport::PRESERVE_PREEXISTING && file_exists($fileTargetPath)) {
     162                                          $transport->xpdo->log(xPDO::LOG_LEVEL_INFO, "Attempting to preserve files at {$fileTargetPath} into archive {$preservedArchive}");
     163                                          $preserved = xPDOTransport::_pack($transport->xpdo, $preservedArchive, $fileTarget, $fileName);
     164                                      }
     165                                      if (is_dir($fileSource)) {
     166                                          $copied = $cacheManager->copyTree($fileSource, $fileTarget, array_merge($options, array('copy_return_file_stat' => true)));
     167                                      } elseif (is_file($fileSource)) {
     168                                          $copied = $cacheManager->copyFile($fileSource, $fileTarget, array_merge($options, array('copy_return_file_stat' => true)));
     169                                      }
     170                                      if (empty($copied)) {
     171                                          $transport->xpdo->log(xPDO::LOG_LEVEL_ERROR, "Could not copy {$fileSource} to {$fileTargetPath}");
     172                                      } else {
     173                                          if ($preExistingMode === xPDOTransport::PRESERVE_PREEXISTING && is_array($copied)) {
     174                                              foreach ($copied as $copiedFile => $stat) {
     175                                                  if (isset($stat['overwritten'])) $transport->_preserved[$options['guid']]['files'][substr($copiedFile, strlen($fileTarget))]= $stat;
     176                                              }
     177                                          }
     178                                          $resolved = true;
     179                                      }
     180                                  } else {
     --> 181 <--                             $transport->xpdo->log(xPDO::LOG_LEVEL_ERROR, "Could not copy {$fileSource} to {$fileTargetPath}");
     182                                  }
     183                                  break;
    


    I suppose, file_exists($fileSource) will fail, since, for example concerning the first error, "core/
    packages/core/modContext/457ca7a0b0eaefc2ca1c7c6e01be469a/0/" is not existing, but two files instead, 457ca7a0b0eaefc2ca1c7c6e01be469a.resolve.core.resolver' and '457ca7a0b0eaefc2ca1c7c6e01be469a.vehicle'

    Actually, these "wrong" files are part of the modx-2.6.5-pl.zip package!

    Either the Zip file has been wrongly packaged, or then there is a programming error in the transport code!

    Any thoughts would be highly appreciated. Thanks!

    -- zhzhzh

    This question has been answered by zhzhzh. See the first response.

    [ed. note: zhzhzh last edited this post 5 years, 6 months ago.]
      • 54735
      • 12 Posts
      Is it an implementation error? (see my updated opening post) - zhzhzh
        • 36582
        • 463 Posts
        Are you using UpgradeModx snippet or something else?
          Web site design in Nottingham UK by Chris Fickling http://www.chrisficklingdesign.co.uk
          • 54735
          • 12 Posts
          Quote from: chrisandy at Nov 15, 2018, 05:10 PM
          Are you using UpgradeModx snippet or something else?

          The upgrade has been done the very standard way according https://docs.modx.com/revolution/2.x/administering-your-site/upgrading-modx.
            • 3749
            • 24,544 Posts
            First, are those errors in the MODX error log, on the screen as part of the setup process, or in the setup log?

            Second, what I'd recommend:

            Back up the site (unless you already have a backup -- a 2.5.7 backup will do )
            Install the UpgradeMODX extra
            Set your settings_version System Setting back to version 2.5.7.

            Then, using UpgradeMODX, install version 2.6.0 (which it appears that you skipped). Then immediately
            (also using UpgradeMODX) install version 2.6.5.
              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
              • 54735
              • 12 Posts
              Hi Bob,

              thank you for the alternative upgrade way. I will try next.

              The errors are from a "core/cache/logs/install.config.2018-11-15T15.46.22.log" file.

              I will follow suit. Thanks so far.

              -- zhzhzh
                • 3749
                • 24,544 Posts
                That's the setup log. There are normally errors that show up there even when everything goes well (and have for a number of MODX versions). IIRC, though, there are only five of them when using UpgradeMODX.

                I'll be curious to see what the log looks like using UpgradeMODX. It's quite possible that your problems have nothing to do with those errors.

                Skipping MODX 2.6.0 might cause some of them. If so, they would likely show up in the MODX error log.
                  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
                  • 54735
                  • 12 Posts
                  I installed the UpgradeMODX extra and it is available. I changed the System Setting to 2.5.7.

                  But clicking on the on the (inverted ?) Begin Upgrade link does nothing.

                  Where can I download the mode-2.6.0-pl.zip file?
                    • 54735
                    • 12 Posts
                    Hi Bob

                    Quote from: BobRay at Nov 15, 2018, 08:30 PM
                    That's the setup log. There are normally errors that show up there even when everything goes well (and have for a number of MODX versions). IIRC, though, there are only five of them when using UpgradeMODX.

                    I'll be curious to see what the log looks like using UpgradeMODX. It's quite possible that your problems have nothing to do with those errors.

                    Skipping MODX 2.6.0 might cause some of them. If so, they would likely show up in the MODX error log.

                    I restored the old version from backup. I updated MODX extras, I added the UpgradeMODX, and it correctly says the current version is 2.5.7, that I should upgrade to 2.6.0 (preselected), BUT the link Begin Upgrade does not work! It looks like grayed out, see picture.

                    Does apache need to be restarted?

                    Please could you help me out?

                    BTW: During the previous upgrades via site.com/setup did not produce the slightest errors, if tjs was your question.

                    And, do you know where I can download mode-2.6.0-pl.zip file as an alternative?

                    Thank you,

                    zhzhzh
                      • 3749
                      • 24,544 Posts
                      Sorry, I missed this message. The grayed-out button might be caused by a JavaScript conflict.

                      If you turn on Dev. mode in Chrome or Firefox (Ctrl-shift-i), you can see any JS errors in the console.

                      The 2.6.0 package is here (you'll have to click around a little to find it): https://modx.com/download/other-downloads
                        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