简体   繁体   English

TYPO3-从RealURL迁移到CoolURI

[英]TYPO3 - Migration from RealURL to CoolURI

I have a big TYPO3 instance that exists for ages. 我有一个存在很久的大型TYPO3实例。 All the time the webpage used RealURL but now we want to migrate to CoolURI because we have better experience with this. 网页一直使用RealURL,但现在我们希望迁移到CoolURI,因为我们对此有更好的体验。 Now the problem is that all old links shall be available even after switching the URL extension. 现在的问题是,即使切换了URL扩展名,所有旧链接也仍然可用。 The CoolURI documentation states CoolURI文档指出

Migrating from RealURL 从RealURL迁移
The field Speaking URL path segment (tx_realurl_pathsegment) is kept with its values, but make sure it's listed in the element. 口语URL路径段(tx_realurl_pathsegment)保留其值,但请确保将其列在元素中。

I got the tables tx_realurl_pathcache and tx_realurl_uniqalias besides some other tables like redirects, etc. But I don't really understand the function and differences of these two tables and can't find any indepth documentation on this. 除了重定向等其他表外,我还获得了表tx_realurl_pathcache和tx_realurl_uniqalias。但是我不太了解这两个表的功能和区别,因此无法找到任何深入的文档。 So I'm a bit afraid right now that I have to reverse engineer the whole extensions and then write a script which exports all the old URLs and imports into the new CoolURI tables. 因此,我现在有点担心,我必须对整个扩展进行反向工程,然后编写一个脚本,将所有旧的URL导出并导入到新的CoolURI表中。 Because we also use tt_news and these URLs have to work, too. 因为我们也使用tt_news,所以这些URL也必须起作用。

So does anyone have some experience with this? 那么,有人对此有经验吗? Does CoolURI automatically handle everything and the old links are still valid or if not maybe someone could give me a detailed explanation for all the RealURL tables in the database? CoolURI是否会自动处理所有内容并且旧链接仍然有效,或者如果没有,也许有人可以给我详细解释数据库中的所有RealURL表?

I wouldn't migrate if there is no really important reason (like ie. missing feature). 如果没有真正重要的原因(例如缺少功能),我不会迁移。 To make sure that you'll be able to generate all links properly and then map them into CoolURI you'll need to learn RU logic anyway. 为了确保您能够正确生成所有链接,然后将它们映射到CoolURI中,您仍然需要学习RU逻辑。

Reason: RU generates links on the fly - if it's required, and then caching it in the tables, other tables stores links to common pages and other for extensions. 原因:RU动态生成链接-如果需要,则将其缓存,然后将其缓存在表中,其他表则存储指向公共页面的链接,其他存储扩展。 You would need to just write custom extension which will visit each page, to make sure that RU cached every possible link and then rewrite all results into for an example list of redirects. 您只需要编写自定义扩展名即可访问每个页面,以确保RU缓存了每个可能的链接,然后将所有结果重写为示例重定向列表。 IMHO it's not worth of wasting time. 恕我直言,这不值得浪费时间。

Note , I don't want to say that CU is bad :) actually I don't know it. 注意 ,我不想说CU不好:)实际上我不知道。 I want to just remember Voltaire's most famous words: " the better is an enemy of the good " 我只想记住伏尔泰最著名的话:“ 越多越好

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM