简体   繁体   English

无法将TYPO3从4.5升级到6.2

[英]Cannot upgrade TYPO3 from 4.5 to 6.2

A TYPO3 4.4.15 site has been disabled by the remote host's upgrade of PHP to version 5.6.23. 远程主机将PHP升级到5.6.23版已禁用TYPO3 4.4.15站点。 Reading the TYPO3 upgrade docs suggests the upgrade path of the TYPO3 installation to something compatible with 5.6 is: 4.4.15 -> 4.6.n -> 4.7.n -> 6.0.n -> 6.1.n -> 6.2.n -> 7 LTS 阅读TYPO3 升级文档表明TYPO3安装的升级路径与5.6兼容的是: 4.4.15 -> 4.6.n -> 4.7.n -> 6.0.n -> 6.1.n -> 6.2.n -> 7 LTS

This is likely the safest path. 这可能是最安全的道路。 Is there an equally safe but shorter path? 有同样安全但更短的路径吗? [All work will be done in a VM sandbox.] [所有工作都将在VM沙箱中完成。]

Edit 1 编辑1

Made it through 4.5.40. 通过4.5.40。 All update steps pass, all database mods accomplished. 所有更新步骤都通过,所有数据库模块都已完成。 Tarball of 4.5 created, mysqldump created. 创建了4.5的Tarball,创建了mysqldump。 Both copied to VM with PHP 5.6. 两者都使用PHP 5.6复制到VM。 Tarball extracted, database recreated with dump. Tarball已提取,数据库使用dump重新创建。 Launching site with typo3_src -> ../typo3_src-6.2.30 , database mod fails with: typo3_src -> ../typo3_src-6.2.30启动网站typo3_src -> ../typo3_src-6.2.30 ,数据库mod失败:

Database update failed
Error: Data truncated for column 'adminusers' at row 1

Edit #2 编辑#2

Changed title from Shortest safe path from TYPO3 4.4.15 to 7 LTS to Cannot upgrade TYPO3 from 4.5 to 6.2 . 将标题从Shortest safe path from TYPO3 4.4.15 to 7 LTS更改Shortest safe path from TYPO3 4.4.15 to 7 LTSCannot upgrade TYPO3 from 4.5 to 6.2

Above occurs even after adding smooth_migration . 添加smooth_migration后甚至会出现上述情况。 Hate to see what a bumpy migration is! 讨厌看到多么颠簸的迁移!

Edit #3: 编辑#3:

Got past the adminusers error by truncating sys_workspace . 通过截断sys_workspace来解决adminusers错误。 Upgrades performed through the install tool. 通过安装工具执行升级。 Now chasing bugs with a supposedly upgraded site. 现在用一个据称升级的网站追逐bug。 It's astounding how stuff noted years ago persists. 令人震惊的是多年前的事情仍然存在。

Edit #4: 编辑#4:

Errors received after upgrade all see to relate to references to requiring PATH_t3lib... items. 升级后收到的错误全部看到与要求PATH_t3lib...项目的引用相关。 Each error that appeared in /var/log/apache2/error.log was addressed as front & back end screens were refreshed until no further errors occurred. /var/log/apache2/error.log中出现的每个错误都被解决,因为前端和后端屏幕都被刷新,直到没有发生进一步的错误。

Edit #5: 编辑#5:

Once error-free, the site is missing both left & right columns of a three column setup. 一旦没有错误,该站点缺少三列设置的左右列。 I do not know how to recreate them and am largely disinclined to go back to figure out how and where the got lost. 我不知道如何重新创建它们,我基本上不愿意回过头来弄清楚丢失的方式和地点。 But I'm open to hints on finding them, not recreating them. 但是我很乐意找到它们,而不是重新创造它们。 I'll upvote the answer below but not accept because I don't think I've fully upgraded the site. 我将在下面给出答案,但不接受,因为我认为我没有完全升级网站。

Edit #6: 编辑#6:

In going back over the process I learned that elements had actually disappeared on the conversion from 4.4 to 4.5. 在回顾过程中,我了解到元素实际上已经从4.4到4.5的转换中消失了。 What's curious, but beyond my concern for now at least, is that the "missing" elements appear in the backend. 什么是好奇,但至少我现在关注的是,“缺失”元素出现在后端。 They just are not displayed on the page where they appeared in 4.4. 它们只显示在4.4中出现的页面上。

4.4 -> 4.5 (LTS) -> 6.2 (LTS) -> 7.6 (LTS) -> 8.7 (LTS) 4.4 - > 4.5(LTS) - > 6.2(LTS) - > 7.6(LTS) - > 8.7(LTS)

LTS to LTS is a safe way. LTS到LTS是一种安全的方式。

6.2 is already compatible with PHP 5.6. 6.2已经与PHP 5.6兼容。

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

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