-
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
Mage2 cache_dir #3522
Comments
@anjenehm is this still on Gentoo? We have not tested on all flavors of linux, officially only Centos and Ubuntu are supported. |
@mazhalai yes still on gentoo |
@mazhalai you told me in the old ticket #3424 when i set in setup/src/Magento/Setup/Validator/DbValidator.php after the query "checkDatabasePrivileges" to return true, that magento wouldnt be fully functional. What did that mean? a other mysterious thing is that the backend url is www.mydomain.com/admin/admin/dashboard/index/key/ |
If you have a db user without the required permissions, how can you expect all db functions to work? What is mysterious about the backend url? |
Sure.... Maybe i should take a look for a new hoster The url should be like domain.com/admin/dashboard and not doubled /admin/admin, or not? |
@mazhalai can you tell me concretely what functions would not work? |
Any db commands with the ones listed under requiredPrivileges Double admin shows up, since you selected admin as your backend-frontname, by default it is |
So @mazhalai can you give me a update to my error? |
Couldn’t create cache_dir error. If you have cache_dir error in magento 1 and magento 2, goto the [Magento_Root]/vendor/magento/zendframework1/library/Zend/Cache/Backend/File.php on your magento site. Now edit this file and goto line no. 99 and you will see cache dir is assign to null ‘cache_dir’ => null, Add var in place of null and save file ‘cache_dir’ => ‘var’ Now you have assign the magento root var dir as a cache dir for your magento store. this helped! |
[TSG-CSL3] For 2.2 (pr12)
@mazhalai so now you see that this error displays on a mage2 setup!
The text was updated successfully, but these errors were encountered: