Feature #93768
open
Redirect: Mass import of redirects (solution for editors)
0%
Description
Hello,
I know this feature was already requested 2 years ago (https://forge.typo3.org/issues/85488) but it would be a huge upgrade if editors could upload multiple redirects in a .csv file by themselves.
The originally request was declined because of a lack of requirements but the requirements are actually clear IMHO.
"won't do this, as this would be a "generic CSV importer" which is unclear what the specs would be."
What do you think?
Best regards and keep up the good work!
Updated by Georg Ringer about 3 years ago
have you checked out my extension https://github.com/georgringer/redirect_generator?
Updated by Daniel Hettler about 3 years ago
Georg Ringer wrote in #note-1:
have you checked out my extension https://github.com/georgringer/redirect_generator?
Yes and it is a good solution for the system maintainers but this should be an action editors can do in the TYPO3 backend by themselve.
Your extension is great for an initial import of redirects or for system maintainers but often editors want to import multiple records in their daily work. Currently they have to do this manually or instruct us to do it.
Updated by Daniel Hettler about 3 years ago
- Subject changed from Redirect: Mass import of redirects to Redirect: Mass import of redirects (solution for editors)
Updated by Sybille Peters over 2 years ago
- Category set to Link Handling, Site Handling & Routing
- Tags changed from Import, Redirect, CSV to Import, Redirect, CSV, redirects
Updated by Sybille Peters over 2 years ago
I think it would be a good idea to check if this really makes sense first. It can be problematic to
- give editors access to redirects management
- create lots of redirects (managed via TYPO3, specifically PHP versus within webserver config)
While - of course - this is up to the integrators and site admins, it is not necessarily a good idea IMHO if TYPO3 should supply features which may cause problems if not handled well and are prone to be misused and not used in their intended way.
In the redirects documentation we explicitly added some paragraphs to warn about performance and how to handle editors - this was after much discussion because we did not want to unnecessarily point out problems - but fact remains redirect handling does require some knowledge about SEO etc., too many redirects via sys_redirect will become a problem (because of performance) and - in general the question is whether managing of a large amounts of redirects in the redirects module is such a good idea or they are better maintained in the web server configuration or .htaccess (for performance reasons).
In any case, I would try to focus on fixing bugs first in redirects and site /slug / routing handling and performance issues in managing redirects before starting with this. Not that I want to stand in the way of any cool new features, just something to consider.
see documentation: https://docs.typo3.org/c/typo3/cms-redirects/master/en-us/BestPractices/Index.html
see also issue on performance: https://forge.typo3.org/issues/90143 and this is not trivial to solve and there will most likely still be performance impact with large number of redirects.