-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
File permission error on installation process finish #917
Comments
Now I can confirm that error exists every time I install Magento as a first install. To reproduce this error remove all Magento files, restart Windows, clone anew and run composer install. |
We are working on this internally and will have a fix soon. |
@mazhalai Thanks And little offtop: I cant send private messages using github. Is there anyone that I can contact via email (or otherwise) to discuss some minor things that doesn't require github ? (e.g. contribution cases, questions about workflow etc.) I am also PHP Developer and I am willing to help with some issues as well ;) |
closing based on @mazhalai comment. |
It is really hard to reproduce this error as I had it only 2 times during multiple (over 20 now) installation processes.
At the end of installation process I noticed this error in console:
Warning: unlink(foo\bar\AppData\Local\Temp\install.log): Permission denied in foo\bar\magento2\setup\module\Magento\Setup\src\Model\WebLogger.php on line 168
{"key":"28bb7d0ff44ef670a980dd0a202811fc","success":true,"messages":["For security, remove write permissions from these directories: \u0027foo\bar/magento2/app/etc\u0027 "]}
And it also causes Installation Incomplete error on screen. I noticed this error on Windows 7 and I think it may be one of two reasons:
Will it be a good solution to check directory permission (or file permission) and change it (just in case of first point) and to make sure just fclose() it before unlink().
If someone have a better idea just write :)
As I said it's hard to reproduce this error but I am going to implement solution worked out here and keep trying to break installation process just to make sure that its fixed.
The text was updated successfully, but these errors were encountered: