My larevel app insatller is not going ahead with this error seen in picture below i am using windows 10 with Xampp
Tried .env permission
It's a permission issue try to set 644 for .env file which is standard for files.
You can do that by right-clicking on the file in windows & select properties.
It seems a permission problem.. as you dont have the right permission
Follow this link !
https://stackoverflow.com/questions/30639174/how-to-set-up-file-permissions-for-laravel
hope It will Help You!
Guys it wasn't working normally so i went on shared hosting and there were linux permisssions and i modified them and it worked and i cloned the REPO to my local server and solved the issue tahnks for the feedback
Related
I am receiving a following error
Settings has not been loaded. Used default settings
Wrong config file size connect.cfg please save Settings again
in magento connect. I tried to delete files and did every possible thing, but the issue is not getting resolved. Please help me with possible solution guys. Also the extensions are not getting installed because of this and we are not able to solve problems.
We are using magento 1.9
Make sure that you click settings and click save as this flag will not clear until you do so. I was pulling my hair out with this as I chmod'd the files and chown'd the directory's but it was still showing the error. So once the file and folder permissions are set correctly go to the Magento Connect manager click the settings tab and click save settings then go back to extensions tab and the error will now be gone.
Tony Merlin
When you are in magento connect manager and you get this error
*
Settings has not been loaded. Used default settings
*
Click on magento conect manager Settings tab (top left) and select Use Custom Permissions --> YES and default should be 777 for folders and 666 for files. Deployment Type --> Local Filesystem and then hit SAVE SETTINGS.
The problem should be solved. At least that's how I solved mine when I got this error.
Be sure the /dowloader folder permissions are set to 777 and you can also chown the folder with the apache user. That worked for me. I have done:
chmod 777 -R /downloader/
chown www-data:www-data -R /downloader/
replace www-data with your apache user.
I've done this and worked perfectly for me.
It's a well known issue.
Check if the file named "connect.cfg" hasn't been modified (for
exemple: when I get this issue, the file has nothing into it, every
parameters have been removed and the size is 0kb)
Take a backup of this file and overwrite the existing
The issue should be solved know
For info about the access rights, I have :
2775 for the folder "downloader"
0664 for the file "connect.cfg
chown apache /var/www/ -hR will solve this problem.
It's extremely frustrating that I have 'debug' => true in the app config but all Laravel is showing is "Whoops, looks like something went wrong." For the love of coding, does somebody know how to get debugging to work?
I have faced the same problem. Laravel was showing only "Whoops, looks like something went wrong." but this line and not showing the actual error. Then I have checked the app/config/app.php file and changed "debug" => false to "debug" => true and it worked perfectly.
You said that you have also done it and still not working. I suggest you to run a composer update command for your project and then try again.
To be sure your app is in development mode, edit bootstrap/start.php, in the detectEnvironment function simply put your machine name. On linux use hostname terminal commande to determine your machine name.
$env = $app->detectEnvironment(array(
'local' => array('homestead', 'Jeanphi'),
));
Actually debugging is working fine for me with L4.0.7 when i set 'debug' => true in app/config/app.php
That switch tells Laravel to turn on Whoops and to bypass the 'compiled.php' file. When it is disabled, Whoops will not show. A normal server error page is served instead.
Were you expecting something else?
EDIT: maybe you are referring to "debugging" as the old profiler bar that were in L3 (Anbu). In that case I suggest you install this package
Check you haven't renamed your app/config folder as fideloper suggests in the comment.
For example you might have renamed it to prevent overwriting the default config settings when copying your site somewhere else.
For all it's worth, I was getting this error now after deployment because I didn't create these folders:
/app/storage/cache
/app/storage/logs
/app/storage/meta
/app/storage/sessions
/app/storage/views
Some changes need an apache restart to take effect.
I came across problem recently, after separating out debug and a few other config options into a separate (dev.php) config file.
The in-hindsight obvious, by-logic obscure solution: Don't move debug out of config/app.php
Had that same problem altought my app was in debug mode.
In my case I was deploying on server,and to make that work
you must take care of detectEnvironment variable.
It is located in bootstrap/start.php
$env = $app->detectEnvironment(array(
'local' => array('your_server_name'),
));
as it's instructed in the docs :
http://laravel.com/docs/4.2/configuration
i got same problem with that...
first, laravel run well on windows using apache..
then while i'm using ubuntu and nginx, it shows "Whoops, looks like something went wrong."
no error in php log and nothing found on laravel log..
so i tried modify path folder permission to 0777
sudo chmod -R 0777 {put your folder application folder here}
it works
I had the same problem several times and I have two possibilities.
the folder storage doesn't have the right permissions, you should use chmod 755 or chmod 777
the public/index.php has none permission or a 777
These two options has occurred to me before, maybe there are some more.
well you need to clear configuration cache and regenerate it each time you change config files
run 'php artisan config:cache' in console and your good to go
I have installed new site in Joomla 1.7 and its working fine, but when i checked its back-end (administrator) got 500 Internal Server Error.
Note: Site is working fine in Local server.
Please suggestion me any solution.
Thanks in advance.
First you have change folder permission to 775 for the following folders:
cache, logs, tmp & administrator/cache
then go to: configuration.php
find code:
$log_path = 'XXXXXXXXXXXXX';
$tmp_path = 'XXXXXXXXXXXXX';
and change code into:
$log_path = './logs';
$tmp_path = './tmp';
problem solved :)
I had this problem, but none of your advices didn't help.
I fixed a problem only after I switched off all modules via PhpMyAdmin (PMA).
Table modules, changed parameter "published" to 0 for all and then enabled only few modules with these types:
mod_login
mod_menu
mod_sumbenu
mod_toolbar
mod_title
After this I entered admin page and used top menu to enable all needed modules one by one. After admin page started to give me 500 error again I knew what module is faulty and I disabled it again via PMA.
May be some files are not uploded.Check failed transfer of your FTP server.Make sure all the files are uploded online
Check your error logs and backtrace what is causing the error. It sounds like you have MySQL errors, make sure any of your components/modules/aren't tricking out your site.
Think it's a component?
You can login into PHPMyAdmin and disable/enable modules manually by unpublishing them using the table editor, changing isPublished to 0 .
Try reinstalling database with the correct compatibility and also check web.config file on ftp for correct configuration paths !
I experienced something similar on my site. Digging through the log file, /administrator/error_log i saw this error message:
[08-Oct-2012 15:28:59] PHP Fatal error: Call to a member function login() on a non-object in /home/XXX/public_html/administrator/components/com_login/admin.login.php on line 65 .
Problem was, i had a previous installation of Joomla 1.5.x, and uploaded files for Joomla 1.6 to replace the previous files and upgrade security of the site. Took me almost a month to find a solution for my own case;
Finally found out from this website that I needed to completely delete all previous files in the website root directory before uploading a new version of Joomla.
Hope this helps someone out there who is in the same situation!
I also have the same issue on my site backend when editing or saving some articles, modules etc...Finally i solved it...
Add these lines to /etc/httpd/conf.d/mod_secuirity.conf on your server
SecRuleEngine Off
save it...and restart apache...it works fine for me.
Adding these lines disable mod_secuirity engine off.I don't know if it causes secuirity problems in future..
Tnx all...
Change the permission of folder administrator at 775 or 755
I tried all the above ideas. Without avail. For my site (which was an outdated Joomla 1.5.x site- don't ask!!!), where the backend suddenly stopped working, the final solution was switching the servers PHP version from 4 to 5.5 (even 5.4 did not work!).
I then got some strange PHP warnings in the frontend. But I then updated Joomla from the now again working backend to the last 1.5 version and everything worked fine from the on.
Phew! Maybe this helps someone later on...
In my case there was a single file with bad permissions.
It can be tricky to figure out which file has the problem so just run this to set the permissions for all the files in the directory:
chmod -R ug+rwX .
chmod -R o+rX .
Change the permissions of all of your files/directories.
Files should be 755
Directories should be 644
This is my case and my solution:
I have changed my server and got this error. I have protected my administrator folder using password protection method. So I have checked my new server and found that my protection information are not saved in control panel. also my .htaccess file (in administrator folder) is not compatible to my new server.
The solution:
Simply protect my folder using control panel
I have renamed the .htaccess file to htaccess.txt
It is done.
I hope it could be useful ;)
when i´ll look over my site, created with Kohana 3.2 the wild error "Kohana_Exception [ 0 ]: Directory APPPATH\cache must be writable" appears.
Im using windows 7 with XAMPP and have no idea what to do.
Because the directory "logs" is writable and there are no problems with this dir, but with the cache directory.
please give 777 permission for application/logs folder.
also give 777 permission for application/cache folder.
mod_rewrite and Curl Should be enabled for kohana. These are all are basic requirements of kohana.
Oh yeah, I read an answer from someone yesterday but I only figured it out today. What I did was this:
Go inside application/
Create a new folder cache/
Go inside cache/
Create a empty textfile. (I created empty.txt)
Then thats it. hope it helps
Does folder 'cache' exist in your application folder ?
I have installed new site in Joomla 1.7 and its working fine, but when i checked its back-end (administrator) got 500 Internal Server Error.
Note: Site is working fine in Local server.
Please suggestion me any solution.
Thanks in advance.
First you have change folder permission to 775 for the following folders:
cache, logs, tmp & administrator/cache
then go to: configuration.php
find code:
$log_path = 'XXXXXXXXXXXXX';
$tmp_path = 'XXXXXXXXXXXXX';
and change code into:
$log_path = './logs';
$tmp_path = './tmp';
problem solved :)
I had this problem, but none of your advices didn't help.
I fixed a problem only after I switched off all modules via PhpMyAdmin (PMA).
Table modules, changed parameter "published" to 0 for all and then enabled only few modules with these types:
mod_login
mod_menu
mod_sumbenu
mod_toolbar
mod_title
After this I entered admin page and used top menu to enable all needed modules one by one. After admin page started to give me 500 error again I knew what module is faulty and I disabled it again via PMA.
May be some files are not uploded.Check failed transfer of your FTP server.Make sure all the files are uploded online
Check your error logs and backtrace what is causing the error. It sounds like you have MySQL errors, make sure any of your components/modules/aren't tricking out your site.
Think it's a component?
You can login into PHPMyAdmin and disable/enable modules manually by unpublishing them using the table editor, changing isPublished to 0 .
Try reinstalling database with the correct compatibility and also check web.config file on ftp for correct configuration paths !
I experienced something similar on my site. Digging through the log file, /administrator/error_log i saw this error message:
[08-Oct-2012 15:28:59] PHP Fatal error: Call to a member function login() on a non-object in /home/XXX/public_html/administrator/components/com_login/admin.login.php on line 65 .
Problem was, i had a previous installation of Joomla 1.5.x, and uploaded files for Joomla 1.6 to replace the previous files and upgrade security of the site. Took me almost a month to find a solution for my own case;
Finally found out from this website that I needed to completely delete all previous files in the website root directory before uploading a new version of Joomla.
Hope this helps someone out there who is in the same situation!
I also have the same issue on my site backend when editing or saving some articles, modules etc...Finally i solved it...
Add these lines to /etc/httpd/conf.d/mod_secuirity.conf on your server
SecRuleEngine Off
save it...and restart apache...it works fine for me.
Adding these lines disable mod_secuirity engine off.I don't know if it causes secuirity problems in future..
Tnx all...
Change the permission of folder administrator at 775 or 755
I tried all the above ideas. Without avail. For my site (which was an outdated Joomla 1.5.x site- don't ask!!!), where the backend suddenly stopped working, the final solution was switching the servers PHP version from 4 to 5.5 (even 5.4 did not work!).
I then got some strange PHP warnings in the frontend. But I then updated Joomla from the now again working backend to the last 1.5 version and everything worked fine from the on.
Phew! Maybe this helps someone later on...
In my case there was a single file with bad permissions.
It can be tricky to figure out which file has the problem so just run this to set the permissions for all the files in the directory:
chmod -R ug+rwX .
chmod -R o+rX .
Change the permissions of all of your files/directories.
Files should be 755
Directories should be 644
This is my case and my solution:
I have changed my server and got this error. I have protected my administrator folder using password protection method. So I have checked my new server and found that my protection information are not saved in control panel. also my .htaccess file (in administrator folder) is not compatible to my new server.
The solution:
Simply protect my folder using control panel
I have renamed the .htaccess file to htaccess.txt
It is done.
I hope it could be useful ;)