Hi everyone, I'm migrating an old plain php website to Laravel, everything works fine except one small thing. Evey time I port an old website to Laravel I'm facing the same problem : keeping the old urls working cause the customer already shared on the net, social and so on, and rightly he doesn't want to loose the seo work he has done.
Right now I've created an array of old urls -> new urls and create the routes with redirects in a simpel foreach loop.
Is there a "best practice" to handle this situation? Changing the .htaccess? (even if I prefer the customer to be able to edit the redirects array) Some kind of library?
And finally, is there a simpe way to allow some urls like http://ww.website.com/folder/something.php to pass through the routing untouched (running the something.php) and at the same time redirecting http://www.website.com/folder/anothersomething.php to a Laravel route?
you could place them with in your .htaccess file as 301 Redirects.
Redirect 301 /old-file-url.php http://www.website/the-new-url
Redirect 301 /folder/anothersomething.php http://www.website/the-new-url/new-url
Hope this helps
I'm also migrating a site to laravel and would like the previous pages to redirect to the new pages.... There is just one thing.
What if I'm already redirecting my public folder through htaccess?
RewriteEngine on RewriteCond %{REQUEST_URI} !^public RewriteRule ^(.*)$ public/$1 [L]
I actually ended up creating a controller that manages an old-route -> new-route relationship and generates the routes with the full path. It was actually quite an easy job cause I used the old sitemap to parse old routes and the new ones have similar names,
Thanks for the suggestion. I added another htaccess within my public folder, then added my redirects there.
how do you have two htaccess files in the same folder?
if you don't, because actually one is in the main laravel folder then you have a serious vulnerability in your setup.. one that could allow someone list the contents of your .env file
Different folders.
I have a parent .htaccess redirect to the "public" folder that Laravel creates. Then, I have a .htaccess within that "public" folder to handle the redirects.
Is there a proper way to set up my Laravel installation, rather than using .htaccess redirects?
I recently installed an SSL certificate and I'd typically use .htaccess to force HTTPS, but there are too many redirects.
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
Ok, this is pretty awesome. Redirects can be added in Laravel 5.5.
Route::redirect('/old-about', '/about');
https://laravel-news.com/laravel-5-5-router-view-and-redirect
This worked slick without any htaccess hacks. This is what I did to handle GET parameters that I needed to change around Route::redirect('quotes.php', 'quote/'.request()['quote-id'] ?? ''.'/'.request()['c'] ?? '');
This package design for redirects missing (404) URLs to new URLs. https://github.com/kmlpandey77/laravel-redirection
Please or to participate in this conversation.