Fixed One click upgrader error (upgrading to beta 5)

[Lee]

Affected version

2.1

See's this error:

Warning

: Uncaught ErrorException: [E_WARNING] require(/home/talkdepression/public_html/src/vendor/composer/../ralouphie/getallheaders/src/getallheaders.php): failed to open stream: No such file or directory in /home/talkdepression/public_html/src/vendor/composer/autoload_real.php:66 Stack trace: #0 /home/talkdepression/public_html/src/vendor/composer/autoload_real.php(66): XF::handlePhpError(2, '[E_WARNING] req...', '/home/talkdepre...', 66, Array) #1 /home/talkdepression/public_html/src/vendor/composer/autoload_real.php(66): require() #2 /home/talkdepression/public_html/src/vendor/composer/autoload_real.php(56): composerRequireec13230cd79e563a6cc995d16a3f88cd('7b11c4dc42b3b30...', '/home/talkdepre...') #3 /home/talkdepression/public_html/src/vendor/autoload.php(7): ComposerAutoloaderInitec13230cd79e563a6cc995d16a3f88cd::getLoader() #4 /home/talkdepression/public_html/src/XF.php(229): require('/home/talkdepre...') #5 /home/talkdepression/public_html/src/XF.php(73): XF::startAutoloader() #6 /home/talkdepression/public_ in /home/talkdepression/public_html/src/vendor/composer/autoload_real.php on line 66

Fatal error: composerRequireec13230cd79e563a6cc995d16a3f88cd(): Failed opening required '/home/talkdepression/public_html/src/vendor/composer/../ralouphie/getallheaders/src/getallheaders.php' (include_path='.:/opt/cpanel/ea-php72/root/usr/share/pear') in /home/talkdepression/public_html/src/vendor/composer/autoload_real.php on line 66

 

[Lee]

Let me add, I used the auto upgrader.

 

[Mike]

I guess you managed to get a partial composer data update in a single "refresh" of the copy. You will likely need to upgrade the traditional way.

 

[sip]

Just upgraded w/o any issues. 2.1B4 to B5

 

[Mike]

It will likely be dependent on the exact number of changes required -- upgrading from B1 to B5 would have more than B4 to B5 -- and your server speed, as it may need to "split" pages and it looks to be dangerous if we update certain parts of our vendor dependencies.

Though not ideal, the good news is that a traditional upload and upgrade should generally directly resolve the issue.

 

[Lee]

Traditional update does indeed resolve the issue

 

[Mike]

This sort of issue should be mitigated (in most cases) as of the next 2.1 release. We handle the file update process in a particular order which should ensure that dependencies are in place before they need to be loaded.