[horde] autoload.php

[Brent]

  Quoting Simon B <simon.buongiorno at gmail.com>:

> On Fri, 13 Jun 2025 at 16:16, Brent <impuser at bitrealm.com> wrote:
>> Quoting Simon B <simon.buongiorno at gmail.com>:
>>
>> Hi Ralf,
>>
>> I was debuggging something else and I ran across these log lines in the
>> apache error_log.
>>
>> [Thu Jun 12 12:41:32.582396 2025] [php:warn] [pid 502630:tid 502630]
>> [client 80.187.120.191:26331] PHP Warning:
>> require_once(/usr/share/2024-composer-horde6/vendor/vendor/autoload.php):
>> Failed to open stream: No such file or directory in
>> /usr/share/2024-composer-horde6/vendor/horde/horde/rampage.php on line 2
>> [Thu Jun 12 12:41:32.582542 2025] [php:error] [pid 502630:tid 502630]
>> [client 80.187.120.191:26331] PHP Fatal error:  Uncaught Error: Failed
>> opening required
>> '/usr/share/2024-composer-horde6/vendor/vendor/autoload.php'
>> (include_path='.:/usr/share/php') in
>> /usr/share/2024-composer-horde6/vendor/horde/horde/rampage.php:2\nStack
>> trace:\n#0 {main}\n  thrown in
>> /usr/share/2024-composer-horde6/vendor/horde/horde/rampage.php on line 2
>>
>> I checked for the file, and whilst there is an autoload.php - 2 actually -
>> neither is where Apache is looking for it.
>>
>> root at mail:~$ find /usr/share/2024-composer-horde6/ -type f -name
>> autoload.php
>> /usr/share/2024-composer-horde6/vendor/autoload.php
>> /usr/share/2024-composer-horde6/vendor/horde/css_parser/bundle/vendor/autoload.php
>> root at mail:~$ ls /usr/share/2024-composer-horde6/vendor/vendor/autoload.php
>> ls: cannot access
>> '/usr/share/2024-composer-horde6/vendor/vendor/autoload.php': No such file
>> or directory
>>
>> Is it safe to move (copy one of them to the correct location?  And which
>> one, since they are not identical.
>>
>> I am currently petrified to do a composer upgrade since I do not really
>> have the skills to roll-back like the others had to do last week.
>>
>> Have a nice weekend.
>>
>> Simon
>> --
>> Horde mailing list
>> Frequently Asked Questions: http://horde.org/faq/To unsubscribe,
>> mail: horde-unsubscribe at lists.horde.org
>>
>> Your "cannot access" is because your "ls" has a double "vendor" in the
>> path. Vendor/vendor would not be correct, of course.
>>
>> For the error you're getting in php, check your rampage.php file.
>> You're picking up an extra "vendor" from somewhere. Mine shows
>> '/vendor/autoload.php'.
>
> But that is kind of my point.  The file exists at the correct location
>
> /usr/share/2024-composer-horde6/vendor/autoload.php
>
> The rampage.php file (whatever that does, and I certainly have not
> edited it) is seeing an extra /vendor directory.
>
> For me this is an error in some php syntax.
>
>> For trying out installs and having a way to back out a change, there's
>> two options.
>>
>> 1) Setup a vm with your config and test the upgrades there before
>> going to production.
>>
>> 2) Backup your install before you try an upgrade, then you can revert.
>> Your example using a user that has full access to the directory
>> needing to be backed up:
>>
>> $ cd /usr/share/2024-composer-horde6
>> $ mkdir ~/backups
>> $ tar cf ~/backups/horde-6-13-25.tar .
>>
>> Try it out. If something is broken and you want to revert:
>>
>> $ cd /usr/share/2024-composer-horde6
>> $ tar xf ~/backups/horde-6-13-25.tar
>>
>> What's nice about composer horde is that there's no system components
>> outside the install directory that you generally need to worry about.
>>
>> You MIGHT need to remove cached php, css, and session files. On my
>> system, they are in /var/lib/php/session and /var/lib/php/tmp. I then
>> restart the php-fpm service for good measure.
>
> Thanks Brent - that is very helpful!
>
> Regards
>
> Simon
>
>> brent
>> --
>> Horde mailing list
>> Frequently Asked Questions: http://horde.org/faq/
>> To unsubscribe, mail: horde-unsubscribe at lists.horde.org
>
> --
> Horde mailing list
> Frequently Asked Questions: http://horde.org/faq/To unsubscribe,  
> mail: horde-unsubscribe at lists.horde.org

The files DON"T exist at the error location. Check that error  
closely...you see there is "vendor/vendor" in the error message path.  
That shouldn't be there, should just be "vendor". I'm not sure where  
that is coming from, offhand. 

brent