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.
Related
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.
I have apparently messed up the permissions of my development environment and can no longer get the web site i'm working on to come up with localhost. There are a lot of files to fix and I do not want to have to try to fix them all manually through finder. Is there a way to fix them all at one time? I'm sure there is a command pompt I could use but I'm not that familliar with comman line.
I am on a Mac running OSX 10.9
Help please
This is an wasy one to fix, especially for wordpress permissions.
Open up a terminal (/Applications/utilities/terminal.app). You would then change directory to where you keep your development sites.
cd /path/to/where/you/keep/your/Site
Then issue the following two commands in you site's directory
find . -type d -print0 | xargs -0 chmod 755
find . -type f -print0 | xargs -0 chmod 644
This will recursively set permissions to what apache expects.
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 have installed Magmi via FileZilla following the instructions on the Magmi wiki. I followed the instructions for common users because I don't know much about webservers, link.
When the permissions are set to 705 I can't get on the Magmi page. I get a 403 Forbidden error when I go to website.com/magmi/web/magmi.php. Setting the permissions on 777 works but it doesn't seem like a good idea.
How can I get to the Magmi page with the permissions set on 705?
Any other tips on how to secure the Magmi page are welcome too. I don't understand the Magmi wiki.
The correct file permissions for Magmi and Magento should be
755 for Folders
644 for Files
Run this shell command in your Magento root folder to set all files and folders to their correct permissions set:
chmod -R 755 *; find -type f -print0|xargs -0 chmod 644
I hope you can help get to the bottom of this. This is whats happened:
We duplicated our live Magento site (for example we'll call it domain1.com) to a development server (for this example I'll call this domain2.com)
Did a find/replace for the domain1.com to domain2.com in both the database and files
Deleted all var/cache and var/session files
Reindexed all indexes via SSH
Emptied browser cache
Checked all file permissions
Disabled the .htaccess incase this was causing a redirect
But it's still redirecting to the live server (domain1.com)??
Any ideas what may be triggering this?
Cheers,
Dave
Solved the issue...hopefully this helps some other people.
When the site was duplicated we edited the "local.xml" file with the new details but kept the old one and renamed it "localnew.xml"
It seems Magento was still picking up these details as so was redirecting to the old site.
Deleting the "localnew.xml" (or whatever you called it eg. localxxx.xml) fixed all our issues!
I'm working in a local Centos 6.4 running in a VM at the moment to test various things.
My production Magento site is in that folder: /var/www/html/magento
and the staging site is there: /var/www/html/staging/magento
I had the same issue than you, did everything I could come up with, triple checked the urls in the database, cleared the cache, checked the .htaccess file, rebooted multiple times.
The one thing that fixed the issue has been to set back the permissions properly:
cd /var/www/html/staging/magento
find . -type f -exec chmod 644 {} \;
find . -type d -exec chmod 755 {} \;
chown -R sysadmin:apache .
chmod -R 777 media app/etc var var/.htaccess
Just open your DB and open the table "core_config_data"
then edit the values for the path web/secure/base_url & web/unsecure/base_url