I have downloaded a project from some website. When i run php artisan server it runs successfully shows server has started on 127.0.0.1:8000. When hit localhost:8000 in browser it gives http 500 error. So i checked the storage/logs/laravel.log file its blank, the logs are not going there. I don't know why. Apart from this there is not http folder inside app folder which contains controllers. So I go through the routes/web.php to see which controllers are being used so i found 'RegisterController', 'LoginController' written in routes file. So i searched for these controllers in whole project I found 'RegisterController.stub' inside 'vendor/hesto/multi-auth/src/stubs/Controllers'. I don't know how to run this project. I have attached the screenshot of app directory.
Related
When i load my application on the root route / it works normally on both local and on testing server. but when i deployed to production. the root route / does not work. But other route seems to work normally. for example, if i open google.com it just displays a blank page but when i open google.com/another it works fine. The application is hosted on digital ocean. What can be the possible cause?
I tried redeploying to see it the was an issue with the deployment, still nothing. I checked the htaccess file, everything looks fine.
I'm new using Laravel. I'm having problems installing a Laravel project when I try to serve it. The project run well, although it's not loading anything in the public folder. This affects all the scripts or css in the web page.
Browser claims error 404 although files already exists.
I figure it out that the problem is that the public folder it's not included and the router responds with a 404 error for any file located there.
Anyone have idea of what's going on here and how can I solve it?
I have a Laravel 5.2 project working fine locally, after uploading to a live server I have a 'laravel' folder in my root directory and public folder under 'public_html/testsite'
My 'index.php' points to the correct '/bootstrap/autoload.php' and '/bootstrap/app.php'
Upon going to my 'url/testsite/' I get a blank page only (was working fine L5.0) firebug shows : 500 Internal Server Error with HTML : Reload the page to get source for...
index.php is loading by testing with die() before any 'require' methods, but after 'require... autoload.php' the die() is not working, however it is successfully calling autoload.php as a die() works within this file.
I'm not sure if this is a .htaccess issue, or maybe I had to set something up in cPanel last time for this folder (I can't remember). I'd appreciate any help!
Please note this Laravel project sits as a test site in a /testsite/ folder along with my current live site files.
Amongst changing many things at once, I appeared to have solved this by setting up a subdomain within cPanel and setting this to my testsite/ folder.
This was on a server with my current website live under public_html/ and setting up a test laravel app(website) with under public_html/testsite/ to work as an independent site for testing.
The typical "change permissions on storage folder" suggested elsewhere on stackoverflow did not solve my issue so hopefully this helps someone in the same boat.
I am using Laravel 5.1 on WAMP Server 2.5.
And I have this error while working on pagination.
404 Not Found
While I run my site locally using this php artisan serve
php artisan serve --port=212
I run to my site index url http://localhost:212/displays.
The pagination works fine, its pagination link work fine on every page http://localhost:212/displays?page=2.
But when I run it manualy without php artisan serve (http://localhost/bookstore/public/displays), the pagination link goes wrong. The pagination link originally printout http://localhost/bookstore/public/displays/?page=2, but it automatically change into http://localhost/displays?page=2 when the page fully rendered.
Is anyone have same problem like me? Glad if any of you could help.
This is likely because you're meant to set the web root on your server to the public folder (and Laravel assumes that that's the case).
As it is, your web root is set to somewhere two levels above the public folder, so when Laravel tries to redirect to /displays?page=2 it tries to send you to the wrong folder.
I'm working in a Laravel 5 application. I have been playing around with the configuration values and creating routes, controllers, models and views. I used to view all PHP errors in the browser, but now, I don't understand why. I just get some errors. In some case, the browser just returns the 500 http error (Internal server error).
For example, if I call a url that don't have a correspondent route, I get an error description in the browser. If I have a route pointing to a controller that does not exist, I only receive the 500 http error. Why does this happen?
It was a permissions problem, specifically on the storage folder, i.e. Laravel cannot write to the log file. Just running chmod -R 755 storage from the root of the project and the problem was resolve.