I developed a website using wordpress hosted with godaddy, I further wanted to include a magento solution with it by installing magento as a subfolder of the root. in the process of installing I get this errors.
Im not sure im doing it right
Path "D:\Hosting\11968835\html\magento\app\etc" must be writable.
Path "D:\Hosting\11968835\html\magento\media" must be writable.
Path "D:\Hosting\11968835\html\magento\media\customer" must be writable.
Path "D:\Hosting\11968835\html\magento\media\dhl" must be writable.
Path "D:\Hosting\11968835\html\magento\media\dhl\logo.jpg" must be writable.
Path "D:\Hosting\11968835\html\magento\media\downloadable" must be writable.
Path "D:\Hosting\11968835\html\magento\media\xmlconnect" must be writable.
Path "D:\Hosting\11968835\html\magento\media\xmlconnect\custom" must be writable.
Path "D:\Hosting\11968835\html\magento\media\xmlconnect\custom\ok.gif" must be writable.
Path "D:\Hosting\11968835\html\magento\media\xmlconnect\original" must be writable.
Path "D:\Hosting\11968835\html\magento\media\xmlconnect\original\ok.gif" must be writable.
Path "D:\Hosting\11968835\html\magento\media\xmlconnect\system" must be writable.
Path "D:\Hosting\11968835\html\magento\media\xmlconnect\system\ok.gif" must be writable.
this is a permissions issue. I'm not a windows guy, but when I get this error, I run
find . -type f -exec chmod 644 {} \;
find . -type d -exec chmod 755 {} \;
chmod 550 pear
chmod 550 mage #for magento 1.5+
Then sometimes depending on the filesystem, I have to change the perms on Media and Var:
chmod -R 777 var chmod-R 777 media
Obviously you don't want to leave 777 on there like that, but you can start there and work backwards. Find the same folders on windows and change those perms and it'll solve your issue.
Related
I have this situation, a real folder called "git" is symlinked to .githooks:
Is there a way to make the symlinked files non-writable, without affecting the original files?
I don't want users to accidentally modify the source in the git folder form the .githooks folder.
I tried:
chmod -R .githooks/* 555
and
chmod -R .githooks/* 544
and I got this both times:
chmod: Invalid file mode: .githooks/pre-commit
By mistake I have executed the following command on my redhat office machine and now I cannot run ctags -R * any more.
ln -s /usr/bin/ctags-exuberant
Hope following info helps,
[ypp:~]$ ls /usr/bin/ctags-exuberant
[ypp:~]$ ls: /usr/bin/ctags-exuberant: No such file or directory
[ypp:~]$ unlink /usr/bin/ctags-exuberant
unlink: cannot unlink /usr/bin/ctags-exuberant': No such file or directory
[ypp:~]$ which ctags
alias ctags='/usr/bin/ctags'
/usr/bin/ctags
[ypp:~]$ ln -s /usr/bin/ctags-exuberant /usr/bin/ctags
ln: creating symbolic link '/usr/bin/ctags' to '/usr/bin/ctags-exuberant': File exists
[ypp:~]$ ln -s /usr/local/bin/ctags /usr/bin/ctags-exuberant
ln: creating symbolic link ,/usr/bin/ctags-exuberant' to '/usr/local/bin/ctags': Permission denied
So far I have tried,
[ypp:~]$ rm /usr/bin/ctags-exuberant
/bin/rm: cannot lstat /usr/bin/ctags-exuberant': No such file or directory
[ypp:~]$ rm -i /usr/bin/ctags-exuberant
/bin/rm: cannot lstat /usr/bin/ctags-exuberant': No such file or directory
[ypp:~]$ unlink /usr/bin/ctags
unlink: cannot unlink /usr/bin/ctags': Permission denied
Please tell me how do I get my ctags working back to normal,
I don't have superuser privilege also.
According the manpage, ln creates a link to file TARGET with the name LINKNAME. If LINKNAME is omitted, as was your case, a link to TARGET is created in the current directory, using the name of TARGET as the LINKNAME. As a result, when you executed ln -s /usr/bin/ctags-exuberant a symbolic link (sometimes called soft link) named ctags-exuberant would have been created in your present working directory pointed at /usr/bin/ctags-exuberant.
There seems to be more at play than what you have shared with us here. Simply creating a link to ctags-exuberant in any directory should not have resulted in the changes you are experiencing. Where there other changes made to your path?
If, somehow just creating the link has caused all your troubles, then you need to focus on finding the resulting link and removing it. If you don't know what directory it was created in, you could find it via the following:
find / -type l -name 'ctags-exuberant' 2>/dev/null
Once it is found, remove it and see if that fixes your problems. Let us know what you find.
Else, you might do better to try the wise minds over at https://unix.stackexchange.com/
My Magento site that is consistently erroring out and giving me the report screen with the file name, but the file does not exist in the reports folder.
Also this folder have 777 permission.
what could be the cause of this issue.
Check permissions for the "var/cache" folder, it should be writeable to the system user running PHP. If yours is an Apache/mod_php installation, the user should be the same as in your Apache config (see User configuration directive).
Check the following folders:
var
var/log
var/report
var/cache
Just to test this, make sure all files and folders in Magento's "var" are accessible for the PHP user.
On Linux, your can do this by running:
#> cd /path/to/your/magento/folder/
#> find ./var -type f -exec chmod 666 '{}' ';'
#> find ./var -type d -exec chmod 777 '{}' ';'
Please note that 777 and 666 permissions are NOT recommended in production environment, as they represent a security threat. Please tune your permissions, for all Magento installation files and folders, in production environment.
Im getting blank page while using Laravel, I already gave perms to the folder with
find app/storage -type d -exec chmod 777 {} \;
But still blank page.
Another thing you can try...
run php artisan serve from your projects root dir, and see if the browser comes up if you go to http://localhost:8000
And give us feedback in the run... because now we only can guess.
I don't know where you're at on solving this problem. But, you'll want your permissions to be at 775 not 777. Also, you may want to check ownership on your htdocs folder and all files within that directory. This is pure speculation since I don't know what kind of dev enviroment you're using, but i run a lamp stack and when ever I have to create a new enviroment the htdocs folder is always owned by root. You may want/need to chown that to your user account.
How about chmod -R 777 app/storage
If that does not work it is a htaccess problem propably
Last but not least, and it might sound stupid, but can you verify if the directories are all there in app/storage ? Because it happened to me that i was checking out from svn and empty directories are not transferred, so make sure you check that app/storage/logs exists.
If there is no log file written then it sure has to do with access levels, for example not being able to write into those dirs, hence the chmod command above. And i posted that because i had never seen anybody do it the way you did.
At least if you are able to write to the log file you can find out what exactly is wrong.
But we have so minimal information it is hard to help you in a good way.
I am getting the following warnings when I run homebrew or any of the ruby web servers locally.
Does anyone know how to get them to go away?
larson:local larson$ brew doctor
/usr/local/Library/Homebrew/global.rb:65: warning: Insecure world writable dir /Users/larson in PATH, mode 040757
/usr/local/bin/brew:74: warning: Insecure world writable dir /Users/larson in PATH, mode 040757
/usr/local/Library/Homebrew/global.rb:65: warning: Insecure world writable dir /Users/larson in PATH, mode 040757
/usr/local/bin/brew:74: warning: Insecure world writable dir /Users/larson in PATH, mode 040757
Your system is raring to brew.
Just remove world write permissions from the directory. As it's your home directory, it really shouldn't have them
chmod o-w /Users/larson
Make the directory not world-writable.
chmod o-w /Users/larson
Change the permissions on the indicated directories to remove the world-writable bit.
as in
chmod 750 ${directory}
Edit: This isn't just your home directory, ruby will gripe if any part of the path contains a world writable permission, since the ability to write to a directory means you can delete any file in that directory, even if you don't own it. Then you can recreate the directory structure and put your own files in place, potentially substituting malicious code.
In other words, if the Users directory is also world writable, it will also cause the error to pop up.
To get them all in one whack:
sudo chmod -R 750 /Users