我可以在 Plone 3 中使用新的文件夹实现 (plone.app.folder) 吗？
Plone 4 包含一个新的文件夹实现（在 plone.app.folder 包中），对于包含许多项目的文件夹来说效率更高。是否可以升级 Plone 3 站点以使用此文件夹实现，而无需将站点完全升级到 Plone 4？
如果是这样，需要采取哪些步骤？我应该注意什么注意事项？
Plone 4 contains a new folder implementation (in the plone.app.folder package) which is much more efficient for folders with many items. Is it possible to upgrade a Plone 3 site to use this folder implementation without doing a full upgrade of the site to Plone 4?
If so, what steps are required to do so? Any caveats I should be aware of?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我刚刚测试了一个 Plone 3.3.5 站点，其中 plone.app.folder==1.0.3 （较新的版本取决于 Products.CMFPlone，即 Plone 4）。
用这个扩展 Plone 3 构建：
zcml slug 很重要，因为 plone.app.folder 不使用 z3c.autoinclude。
运行构建并启动实例后，将产品作为常规 Plone 产品安装，并通过打开以下 URL 迁移现有文件夹：
http:// /localhost:8080/plone/@@migrate-btrees
您将得到如下所示的输出：
希望这会有所帮助
I just tested a Plone 3.3.5 site with plone.app.folder==1.0.3 (newer version depends on Products.CMFPlone, i.e. Plone 4).
Extend a Plone 3 buildout with this one:
zcml slug is important because plone.app.folder doesn't use z3c.autoinclude.
After running buildout and launching your instance, install the products as a regular Plone product and migrate existing folder by opening this URL:
http://localhost:8080/plone/@@migrate-btrees
You'll get an output like this one:
Hope this helps
当 Plone 3 站点正在开发时，我们在 Plone 3 站点中使用了 Plone 4 文件夹，但我不知道它们最近的开发是否使它们依赖于 Plone 4 的其他部分。
我们仍然让它们在生产中的 Plone 3 站点中运行，所以这是可能的。
We used the Plone 4 folders in a Plone 3 site when they were under development, but i don't know if recent development for them have made them depend on other parts of Plone 4.
We still have them running in Plone 3 sites in production, so it is possible.
没有任何线索。但是Plone 3有一个“大文件夹”，它也是基于BTrees并且可以很好地处理大文件夹。但它并不那么光滑。我会在 Plone 3 下使用该站点，我喜欢让我的 Plone 站点尽可能保持标准。 :-)
Not a clue. But Plone 3 has a "Large Folder" which also is based on BTrees and handles large folders well. It's not as slick though. I would use that one under Plone 3, I like to keep my Plone sites as standard as is humanly possible. :-)