表达式引擎 - 升级到 2.4 后出现 Fieldframe 错误
我将 MSM 站点从 1.7.1 升级到 2.4,虽然我可以访问站点的控制面板,但无法加载主站点。我收到以下错误:
错误
无法加载请求的字段类型文件:ft.ftype_id_2.php。
确认字段类型文件位于 expressionengine/third_party/ 目录
我已经搜索了 Expression Engine 网站,用 Google 搜索了它,但找不到任何有帮助的内容。结果,我完全被难住了,并对好的见解持开放态度。
谢谢。
I upgraded an MSM site from 1.7.1 to 2.4 and while I can access the Control Panel for the sites I am unable to load the main site. I get the following error:
Error
Unable to load requested field type file: ft.ftype_id_2.php.
Confirm the fieldtype file is located in the
expressionengine/third_party/ directory
I have scoured the Expression Engine site, Googled it and I can't find anything that helps. As a result I am totally stumped and open to good insights.
Thanks.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
FieldFrame 仅适用于 ExpressionEngine 1.x。 ExpressionEngine 2 有一个内置的字段 API 来取代它。
解决此问题的最佳方法是进入字段组设置并确认所有先前的字段类型均已安装。您是否已将所有 ee1 字段类型迁移到 ee2?您可以通过转到插件 -> 来确保它们已安装在 ee2 中。字段类型。
FieldFrame is ExpressionEngine 1.x only. ExpressionEngine 2 has a built in fields API which takes its place.
Your best bet at fixing this is going into your field group settings and confirming all previous field types are installed. Have you migrated all your ee1 field types to ee2? You can make sure they are installed in ee2 by going to addons -> fieldtypes.
我在使用主配置方法时发生过这种情况。我通过将 config.php 更改为使用相对路径来解决 MSM 站点上的 500 错误。这也必须在我们的 config.php 中完成,将 $base_path 设置为相对路径。当我们将系统文件移动到 public/web 文件夹上方时,第二个 MSM 站点找不到third_party 目录,因为 $base_path 基于第二个站点的目录结构。
I had this happen where we're using the Master Config approach. I resolved a 500 error on the MSM site by changing config.php to use a relative path. That also had to be done in our config.php to set $base_path to a relative path. The second MSM site could not find the the third_party dir when we moved the system file above the public/web folder because $base_path was based on the second site's dir structure.