warning generated/code/Magento/Framework/App/Config/InitialConfigSource/Proxy.php

Question

This is killing me.

When I run bin/magento setup:upgrade it throws this:

Warning: include(/vendor/composer/../../generated/code/Magento/Framework/App/Config/InitialConfigSource/Proxy.php): failed to open stream: No such file or directory in /vendor/composer/ClassLoader.php on line 444

And when I run bin/magento setup:di:compile it throws this:

Class Magento\Framework\App\ResourceConnection\Proxy does not exist

Site was running perfectly. I had run setup:upgrade before without any problem. I had also ran di:compile.

But today, all of sudden this is happening.

Any idea?

UPDATE

I used to follow this every time when I compile: https://devdocs.magento.com/guides/v2.3/performance-best-practices/deployment-flow.html

Could it be the reason now that I cannot run bin/magento setup:upgrade or bin/magento setup:di:compile?

I remember, at first running bin/magento setup:upgrade it threw error, after that I am stuck, couldn't run any CLI commands.

UPDATE 2

On first run setup:upgrade, it threw an error. Unfortunately I did not make a note of that and re-run the setup:upgrade again. Since then the above-mentioned error is thrown.

UPDATE 3

Alright, so in my local instance, I was able to reproduce a similar error. It's slightly different than what I was getting in my live server:

Warning: include(/vendor/composer/../../generated/code/Magento/Framework/App/ResourceConnection/Proxy.php): failed to open stream: No such file or directory in /vendor/composer/ClassLoader.php on line 444

So, after I ran composer update It did allow me to run Magento CLI commands. And I was able to compile.

I still want to understand this. I am yet to perform this into my live server.

i think here is a solution you look for https://magento.stackexchange.com/a/251709/88489 — Freddy Freddy, Apr 17 '20 at 14:24

WaPoNe · Answer 1 · 2021-07-08T08:54:56.153

15

I solved simply by composer:

composer dumpautoload

edited Jul 08 '21 at 08:54

answered Feb 18 '21 at 16:40

WaPoNe

1,590
3
17
35

score 3 · Accepted Answer · answered Apr 12 '20 at 10:24

3

If you use dockergento try

dockergento composer dump-autoload

 docker exec -it -u 0 hp_redis_1 bash

Then inside

redis-cli flushall
exit

and then run setup:upgrade . If you don't use dockergento it might be something similar for bin magento. first try bin/magento composer dump-autoload.

answered Apr 12 '20 at 10:24

Giga Todadze

138
14

What are the autoloads? Is it safe to dump them? – Adarsh Khatri Apr 13 '20 at 03:51
just have exactly the same error https://i.imgur.com/JAwvpHJ.png it Generated autoload files containing 631 classes https://i.imgur.com/mf90Nst.png fixed. – Giga Todadze Apr 13 '20 at 11:17
Can you tell me what exactly did you do to run into this error? I want to understand what triggers this error. – Adarsh Khatri Apr 13 '20 at 12:05
Sure can. I run dockergento composer install --no-suggest -o --ignore-platform-reqs --prefer-dist and it updated some modules. – Giga Todadze Apr 13 '20 at 12:07
If it fixes an error and you accept my answer I'm gonna bounty my question ... I am so stucked https://magento.stackexchange.com/questions/310097/tring-to-filter-products-with-value-id – Giga Todadze Apr 13 '20 at 12:10
So you are saying, composer install triggered this error? – Adarsh Khatri Apr 13 '20 at 12:19
Sure . In my case absolutely yes. – Giga Todadze Apr 13 '20 at 12:49
If it did the job accept it please and I'll have enough rep to set bounty on my question. – Giga Todadze Apr 13 '20 at 14:21
I am yet to perform this on my live server. It cost me a night before and had to revert from backup. I will perform this soon. – Adarsh Khatri Apr 14 '20 at 00:47
sure ! let me know the results. Don't you have staging server to test things there at first? you can install bitbucket pipelines and everything will be checked for errors , your webpage will never be in the same situation. – Giga Todadze Apr 14 '20 at 07:42
very nice answer. Thanks Giga – Giga Todadze Sep 25 '23 at 11:16

score 3 · Answer 3 · answered Apr 12 '20 at 11:30

3

I would suggest to run update composer. Please follow the below command.

composer update

php bin/magento cache:flush and cache:clean

php bin/magento setup:upgrade

Hope this will help you.

answered Apr 12 '20 at 11:30

Nits

2,496
1
8
21

I know, like I said, I want to understand this. Why this happens, what are the causes? – Adarsh Khatri Apr 12 '20 at 22:00
Can you please let me know, your issue has been fixed using my solution or not? – Nits Apr 13 '20 at 10:29

score 1 · Answer 4 · answered Apr 17 '20 at 20:14

1

You are running composer or magento commands with root user (sudo), just fix the permissions and the owners of your magento files and directories (fix the generated directory and remove its content)

After fixing the owner here is a good answer for the permissions

answered Apr 17 '20 at 20:14

laurent

111
3

There is no permission issue. I am running command same way I have been running, that is from magento user. – Adarsh Khatri Apr 17 '20 at 21:55

warning generated/code/Magento/Framework/App/Config/InitialConfigSource/Proxy.php

4 Answers4

Linked