-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Broken Kernel Dir after relative paths #10943
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
…tainer (fabpot) This PR was merged into the 2.3 branch. Discussion ---------- [HttpKernel] removed absolute paths from the generated container | Q | A | ------------- | --- | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | first step to resolve #6484, #3079, and #9238 | License | MIT | Doc PR | n/a This PR converts absolute paths to relative ones in the dumped container. The code is a bit "ugly", but it gets the job done and I'm not sure that there is a more elegant way without breaking everything. Commits ------- c1450b4 [HttpKernel] removed absolute paths from the generated container
need remove |
dirname won't work when the code is inside phar |
@mvrhov then may use realpath |
Oh. I meant realpath. I don't know about dirname, it has to be tested... |
hmm, i never create phar files, but how i know dirname only work whis strings |
Should be fixed now (see #10942). |
no, not fixed |
@ivan1986 Can you be a bot more explicit. I've just tried on a new Symfony SE and it works. Don't forget that you need to composer up (composer install won't work). |
Any news? Cant start project with 2.4.5 |
Culprit code has been reverted for now in all branches. See #10999 for more information. |
in commit 735e9a4 add use filesystem
wrong way to generate parent dir - not use '../' to up parent, use dirname
current is broken Sensio - generate:bundle - it create bundle in app/cache/dev/../src
old value is
'kernel.root_dir' => '/home/ivan/projects/qs/app',
new
'kernel.root_dir' => __DIR__.'/../..',
need
'kernel.root_dir' => dirname(dirname(__DIR__)),
or some other solution
The text was updated successfully, but these errors were encountered: