{"id":26041,"date":"2016-12-01T11:00:44","date_gmt":"2016-12-01T11:00:44","guid":{"rendered":"https:\/\/dev.railscarma.com\/create-search-friendly-urls-rails\/"},"modified":"2024-01-10T10:51:03","modified_gmt":"2024-01-10T10:51:03","slug":"creer-des-rails-durl-conviviaux-pour-la-recherche","status":"publish","type":"post","link":"https:\/\/www.railscarma.com\/fr\/blog\/articles-techniques\/creer-des-rails-durl-conviviaux-pour-la-recherche\/","title":{"rendered":"Comment cr\u00e9er des URL conviviales pour la recherche dans Rails"},"content":{"rendered":"
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\tDisplay IDs in your URLs can be terrible and wasteful for SEO. In this blog entry, I will demonstrate to you how you can utilize slugs to make your URLs more relevant to the page content. In the first place, we will utilize an implicit arrangement (superseding the to_param strategy) to change the URLs and a while later, we will utilize a gem called friendly_id to produce slugs and keep up a past filled with these slugs. So that search engines index your web pages.\n\nFor example: http:\/\/www.exaple.com\/blogs\/1<\/strong> \u00e0 http:\/\/www.exaple.com\/blogs\/blog-name<\/strong>\n\nIci, je cr\u00e9e un \u00e9chantillon Rails5<\/strong> application avec mod\u00e8le de publication pour illustrer exactement comment cela va fonctionner avec les jolies URL.\n
titre du message d'\u00e9chafaudage Rails\u00a0G\u00a0: cha\u00eene publi\u00e9e\u00a0: bool\u00e9en<\/code><\/pre>\ncourir base de donn\u00e9es rails: migrer<\/strong>\n\net cr\u00e9ez quelques exemples de publications (http:\/\/localhost:3000\/posts\/new)\n\napp\/models\/post.rb<\/strong>\n
def to_param title.parameterize end<\/code><\/pre>\n<\/a>\n\nAll the links will be changed to pretty URLs once you add the above method to your model. Please check on index page where it lists all the posts. However, when you click on that it will show you error page.\n\nPost.find method cannot find the record with id which we are passing in URL. We need to create slugs for the above posts in our db for that model.\n\nLet\u2019s add migration file for the slug\n
rails g migration AddSlugToPosts slug: cha\u00eene<\/code><\/pre>\nOuvrez le fichier de migration mentionn\u00e9 ci-dessus et ajoutez un index uniq \u00e0 ce sulg. Slug doit \u00eatre unique.\n
class AddSlugToPosts < ActiveRecord::Migration[5.0] def change add_column :posts, :slug, :string add_index :posts, :slug, unique : true end end<\/code><\/pre>\ncourir base de donn\u00e9es: migrer<\/strong>\n\nNow, we have to change our show action db query to find_by instead of find method. Because we need to fetch the results based on slug.\n\nChange our set_post method to\n
def set_post Post.find_by_slug(params[:id]) fin<\/code><\/pre>\nMaintenant, cela fonctionne comme pr\u00e9vu avec les jolies URL. Que se passe-t-il si deux enregistrements ont la m\u00eame URL puisque ces deux enregistrements portent le m\u00eame nom. Parce que .find_by r\u00e9cup\u00e8re toujours le premier enregistrement. Pour r\u00e9soudre ce probl\u00e8me, avant de sauvegarder le slug, nous pouvons combiner l'identifiant de l'enregistrement avec le slug de la mani\u00e8re mentionn\u00e9e ci-dessous\u00a0:\n
def add_slug "#{id}-#{title.parameterize}" fin<\/code><\/pre>\nSo, it will generate like \u201c1-blog-name\u201d. We have a gem called friendly_gem to simply take care of all the above-mentioned scenarios.\n\nFeel free to remove the above mentione code from the sample app because everything is managed by the gem.\n\nJoyau Friendly_id<\/strong>(Rails 5)\n\nAdd the latest gem from rubygem web to the gemfile and run bundle\n
gemme 'friendly_id', '~> 5.1'<\/code><\/pre>\n
les rails g\u00e9n\u00e8rent un friendly_id<\/code><\/pre>\nLa commande ci-dessus g\u00e9n\u00e8re un fichier d'initialisation et un fichier de migration.\n
ex\u00e9cuter db: migrer<\/code><\/pre>\nCr\u00e9ez des enregistrements et modifiez notre m\u00e9thode set_post comme indiqu\u00e9 ci-dessous. Tous les anciens enregistrements doivent \u00eatre r\u00e9g\u00e9n\u00e9r\u00e9s, au cas o\u00f9 vous en auriez.\n
def set_post Post.friendly.find("Joe Schmoe".parameterize) end<\/code><\/pre>\napp\/models\/post.rb<\/strong>\n
extend FriendlyId friendly_id :slug_candidates, utilisez\u00a0: [:slugged, :finders, :history] def slug_candidates [ :title, [:title, :id] ] end<\/code><\/pre>\nAjouter l'attribut slug au mod\u00e8le Post<\/strong>\n
rails g AddSlugToPosts slug: cha\u00eene<\/code><\/pre>\n
add_column :posts, :slug, :string<\/code><\/pre>\n
add_index :posts, :slug, unique\u00a0: vrai<\/code><\/pre>\n\nMise \u00e0 jour du titre du message<\/strong>\nSlug se mettra \u00e0 jour automatiquement lorsque vous mettrez \u00e0 jour l'attribut title. Mais ce n'est pas une bonne pratique de mettre \u00e0 jour les slugs trop fr\u00e9quemment. L'application peut g\u00e9n\u00e9rer des erreurs en cliquant sur l'une des URL mises en signet, car n'importe qui peut avoir d'anciens signets. Nous devons \u00e9viter cela en ajoutant un symbole d'historique \u00e0 l'option d'utilisation dans votre mod\u00e8le Post.\n
def slug_candidates [ :title, [:title, :id] ] fin<\/code><\/pre>\nslug_candidates feature was added in friendlyId 5. It allows us to tell the friendly id gem, what needs to be done in case of duplicate slugs.\n\nThe code mentioned above advises FriendlyId that it needs to utilize the slug_candidates technique to make the slug uniq. It will attempt the rundown right from the beginning to the end, so in the case above, it will attempt to produce the slug first utilizing the title, and afterwards, if a post by that title already exists, it will attempt to fix the ID again.\n\nSlugs are the primary things read by search engines. That ought to, as of now, give you an idea on how essential they are. To utilize a slug, first add the slug alternative to the friendly_id assistant in the Post Model.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t  
\r\n        
Articles Similaires<\/div>\r\n    
\r\n\r\n            
\r\n            
\r\n    \r\n\r\n      \"joyau\r\n\r\n    <\/a>\r\n  <\/div>\r\n\r\n  \r\n        Gemme de Kaminari  <\/a>\r\n\r\n        <\/div>\r\n              
\r\n            
\r\n    \r\n\r\n      \"pourquoi\r\n\r\n    <\/a>\r\n  <\/div>\r\n\r\n  \r\n        Pourquoi engager des d\u00e9veloppeurs Ruby on Rails en 2026 ?  <\/a>\r\n\r\n        <\/div>\r\n              
\r\n            
\r\n    \r\n\r\n      \"Importance\r\n\r\n    <\/a>\r\n  <\/div>\r\n\r\n  \r\n        Importance de l'architecture logicielle dans le d\u00e9veloppement de logiciels d'entreprise  <\/a>\r\n\r\n        <\/div>\r\n              
\r\n            
\r\n    \r\n\r\n      \"MEILLEURES\r\n\r\n    <\/a>\r\n  <\/div>\r\n\r\n  \r\n        Ruby IDE\u00a0: les meilleurs IDE pour le d\u00e9veloppement Ruby on Rails  <\/a>\r\n\r\n        <\/div>\r\n      \r\n  <\/div>\r\n\r\n