<@U0D4QPHT4> how do you handle redirects for delet...
# generalf
Fabian V. Thobe
01/31/2025, 9:53 AM@tvdeyen how do you handle redirects for deleted pages in alchemy? Did you implement some kind of rack middleware?
t
tvdeyen
01/31/2025, 10:12 AM
At the controller level, because we need database access
https://github.com/AlchemyCMS/alchemy_cms/blob/main/app/controllers/concerns/alchemy/legacy_page_redirects.rb
f
Fabian V. Thobe
01/31/2025, 10:13 AMDo you think that’s a feasible approach for solidus as well?
t
tvdeyen
01/31/2025, 11:26 AM
Yes
f
Fabian V. Thobe
01/31/2025, 11:32 AMOk, we will take a shot at this as current behavior is not great for SEO https://github.com/solidusio/solidus/issues/6093
👍🏻 1
t
tvdeyen
01/31/2025, 11:35 AM
Thanks. I consider this a good feature as well 👍🏻
f
Fabian V. Thobe
01/31/2025, 12:56 PMDo you also have strong feelings about this one? https://github.com/solidusio/solidus/issues/6092
Fabian V. Thobe
02/03/2025, 9:35 AMHey, we will start looking into redirects today. How do you envision cancelling redirects?
Say product has been deleted, where do we redirect (currently the page stays up).
What happens if a slug is removed from a product due to a change and a new product is made using the same slug, do we need a separate process to free it up and throw an error upon safe or do we simply wipe out the old redirect
Fabian V. Thobe
02/03/2025, 9:38 AMOld slug > 301 new slug
Deleted product > 404
Do we want an interface to manage other redirects (eg manual overrides)? I think it’s low hanging fruit kill this issue once and forever and provide also an interface and api to set any manual 301
Fabian V. Thobe
02/03/2025, 4:27 PMSome additional thoughts would be to throw it into a polymorphic table to render the high level functionality also accessible to other ressources such as pages and blog articles.
Fabian V. Thobe
02/03/2025, 4:28 PMWould that work for you?
t
tvdeyen
02/03/2025, 4:37 PM
1. If a new product is made with the same slug as an old product it should win over the old product. It has most likely been replaced by it and shops can explain this in ie. the product description. Everything else is too complex and should be handled by cusotm business logic (product life cycles, etc.)
2. An interface would be nice but is optional (same for API)
3. Polymorphic is fine, as we already need it for products and taxons
f
Fabian V. Thobe
02/03/2025, 5:32 PMok, I would go for a polymorphic table to allow also the addition of other resources later on. If we already have a table, a visualisation to delete lines should not be a problem. I will think about API and if it’s needed.
Fabian V. Thobe
02/03/2025, 6:18 PMIf we have a polymorphic table it would make sense to also add generic 301 as we already have everything else pratically rendering the entire solidus_redirector mood. What do you think?
Fabian V. Thobe
02/03/2025, 6:34 PMIn addition, it would make sense at that point to demote the different treatment of products (slug) and taxons (permalink that is dropped)
Fabian V. Thobe
02/03/2025, 6:36 PMIn addition it’s worth noting that the permalinks in taxons are not real permalinks but in reality slugs
Fabian V. Thobe
02/04/2025, 9:34 AMI am really struggling with the purpose of friendlyid here, could you elaborate why we need it on products, as taxons seems to work well without and it might be easier to just build up a redirection table that contains all lapsed slugs till they are claimed again.
The pathway from a request would be to check in the route first if a ressource is available on that route matching the slug such t for taxons and afterwards cycle a table with redirects and last but not least if nowhere found throw a 404
Fabian V. Thobe
02/04/2025, 9:34 AMThe current implementation of friendlyid creates more problems that it solves from an SEO point of view
Fabian V. Thobe
02/04/2025, 6:54 PMwe have fixed the redirect situation on products, the correct thing would be to handle 301 on taxons the same way and write an interface to delete links or either drop old history urls if they match the slug the slug of a new resource.