If I start new Laravel project everything is working fine (laravel new project for example) but my cloned projects have 404 error
1.project cloned
2.env coppied
3.vendor composer install
4.key:generated
I can notice that vendor folder and .env file are gray color not white as other files.
In my created project all the folders and files are the same color
Thanks James.
Your answer opened my eyes.
I deleted the home route for some reason and I was trying to access that route all the time. It was not active.
When I tried another route it was all good.
It was working all the time ...
Thanks
Related
After successfully running npm run build I copied the contents of the /dist folder in my local wwwroot folder. Everything renders correctly and I an see my page.
The problem comes when I copy the same contents of the /dist folder to a sub-directory on a Shared Hosting site (Domain.com or GoDaddy.com): https://www.mywebsite.com/sub-directory
All I see is a blank page. Upon checking the Network tab in developer tools, I see all requests status come back with 200 Status Code.
At this point I have thrown the towel and would appreciate any help I can get.
I went around my problem and solved it in another fashion. Instead of making a subfolder in /public_html folder, I created a subdomain using the configuration menu. Therefore my site looked like: https://mysubdomain.myoriginalsite.com
While creating a subdomain, the shared-hosting site's configuration asks me what should be the folder for this newly requested subdomain.
So I created a folder in the root (same level as /public_html) called /mysubdomain and copied all my files from /dist folder over there.
It worked like a charm.
Please NOTE: In vue.config.js file I updated my publicPath variable to be '' instead of '/'
Developers Recently i am working on a vue js Website, and everything is working fine on Development but when i build the code using npm run build , the production build gets successfully build but when i try to open the index.html file inside dist directory the file gets opened in Browser but a Blank white page gets Displayed.
You need to start your server, not open the file directly.
Because Vue builds files and connects JS and CSS like it would be on the server.
And now, when you are opening the file, it can't find JS/CSS.
How do you want to deploy your app? I think the following post can help you:
How to deploy vue app
Please check if you have a vue.config.js file and if the configuration is correct according to your project setup.
I am working on laravel 5.4. I have used laravel storage where I have uploded images. It works fine in local. But when I have created zip and uploaded it on server then the public/storage folder is damaged and converted into files. That's why images are not visible on website.
Then what I have do to resolve it. I have delete that files and created zip of storage folder and upload it on server. And unzip that folder then images are visible.
Now, I am facing the another issue. Images are not uploaded into the storage folder.
So how to prevent this issue?
I got solution for it. I have used putty to use terminal of server.
First I have deleted storage folder from the public directory. Secondly, I had open directory of project folder in terminal using putty. Then write command as below :
php artisan storage:link
Now, its working perfect. As well as it restore all the images.
How is it with the img/p folder in Prestashop 1.6.0.9? Is it possible fully to clean it? Cause this folder went to big now, and FTP is almost full now, i need space. For example when i renamed it on FTP, all images on the website worked, and prestashop created automaticaly one new img/p folder, and all seems that works right (also when the initial img/p was out after renaming). Thanks in advance.
when you delete the folder you may see the images working, its from smarty cache, once you clear the smarty cache, presta default (not found) image will be shown.
I recently installed Laravel 5 on my local WAMP server. Firstly I was surprised, because I was expecting the 4.2 Laravel, but as I got the 5th, I decided to give it a try. Firstly I got confused with the folders, but I got used to that and now understand them, but I cannot seem to get my debugger work. In Laravel 4.2 all I had to do was to set 'debug' => true, in the config/app.php file, and when something went wrong, a nice widow appeared in the browser explaining what was wrong. But now all I get is the default Laravel 5 error page in white n' gray -
Sorry, the page you are looking for could not be found.......
I searched the web for the answer. The possible solutions were to:
run the command php artisan optimize in the app folder for the vegant box, but I seem to be not using it and if I run artisan command in the app folder, I'm getting an error: count not open an input file: artisan
Delete the storage/meta/compiled.php file. The problem here is that I dont have such a file.
So right now I am quite worried, because I can't work without that debugger, especialy when I haven't worked with Laravel for a quite a time.
Any help would be highly appreciated!
Laravel 5 uses dotenv. And it is easy to do it
In the root folder rename .env.example to .env you will see APP_DEBUG=true inside.
restart the webserve
The debug mode should be enabled right now.
More information http://laravel.com/docs/5.0/configuration#environment-configuration