This is my first time working with Laravel 5.4 or any Laravel for that matter. I migrated a perfectly good working website to a new host. Now when I go to upload an image from admin or a user account the image won't upload. I get the whoops! error.
I have fixed all the broken links I can find, but I can't find where to go to fix the image won't upload issue.
Any help with this is greatly appreciated.
Thanks.
Related
I tried displaying uploaded images from cloudinary but it wasn't showing using the below
<img style="width:auto" src="https://res.cloudinary.com/hrwev09ub/image/upload/v1637132013/dnpic_1637127942.png">
before now i tried the img tag above actually worked locally but not through heroku, because on heroku what i could see on checking the code source is the below
<img style="width:auto" src="dnpic_1637127942.png">
i am using Laravel 8 with cloudinary on heroku host -- can someone assist me with way out or refer me to a solution tips please.
I'm Danny and I work on Cloudinary's Developer Support team.
I've not had a lot of experience with deploying to Heroku, so I'm unable to speak on why the src is stripping out the https://res.cloudinary.com/hrwev09ub/image/upload/v1637132013 part, however I do notice that the full image path results in a 404.
Could you please let me know what happens when you try to reference the sample image (https://res.cloudinary.com/hrwev09ub/image/upload/sample.jpg) without specifying style=width:auto?
It may also help to confirm you've followed all the steps on Heroku's documentation about using Cloudinary, available here: https://devcenter.heroku.com/articles/cloudinary
Thanks,
-Danny
I am trying to upload images to S3 using laravel livewire file upload, everything works fine in development, but after deployment on staging or production, I still can upload some images but others ( mostly taken with Iphone ) are giving 422 error, I can upload them after cropping them. How can I solve this issue? I am using Heroku.enter image description here
enter image description here
Okay, I solved this by adding FILESYSTEM_DRIVER=s3 into config vars in productions.
I move the project from shared hosting to VPS hosting now everything working fine such as inner pages, design, image loading but I am unable to login and signup now.
When I submit the login/Signup form it will redirect to the same page but without any error message.
And I also generate the Token via command do I need to do anything more to make it work.
I also check the laravel.log file and other things but unable to solve this.
Can anybody face the same issue
Issue is I do not create the session folder to store the session of Laravel 5.4
I have uploaded my first Laravel project folder to the host and when I load the page it appears broken but it works properly in localhost. Do not know how to fix, some advice would be great. Thanks in advance.
I am a beginner with remote servers and building a website, so please bear with my simple questions, if they are.
So I have created a Laravel project on my remote server (by connecting to the command line via Putty and creating a new Laravel project). However it created a folder, so I had to move all of the directories inside of that folder into my main folder, via FileZilla. This is how it appears now:
Illustration of Uploaded files through Filezilla
My code in Laravel was the sample one which comes up whenever you create a new project, I did not change anything.
The only problem which is appearing, is when I visit my webpage, it says that my webpage is currently unable to handle this request (HTTP ERROR 500).
When I visit my webpage/public or any other sort of link, it gives me an error: NotFoundHttpException in RouteCollection.php line 161 (a Laravel error)
Any help or guidance in the right direction would be greatly appreciated.
I can't comment yet, so i have to answer here.
First what kind of server are you using? Shared or Vps? if it's a shared hosting, you have to do more than just upload the files, you'll need to configure ht access too. See this video for guide: https://youtu.be/wQMZld0Iroo
For the routing issue, it means, the route you are trying to visit does not exist. Check your web.php file to be sure the route is in there. This could be a simple spelling error.