是否可以在3.1.7 plone中使用collection.alias? [英] Is it possible to use collective.alias in a 3.1.7 plone?

问题描述

有可能吗?我想将其安装在3.1.7 Plone实例中，但不想输入与构建版本不兼容的版本.

Is it possible? I would like to install it in a 3.1.7 Plone instance, but don't want to enter the buildout incompatible versions hell.

我在机器上尝试过，并添加了collective.alias

I tried in my machine, adding along with collective.alias

extends =
    http://good-py.appspot.com/release/dexterity/1.0a2

和

[versions]
plone.recipe.plone = 3.1.7 
plone.recipe.zope2instance = 3.6

但是开始下载很多东西，直到它下载了Plone 4 egg本身作为依赖项.

But starts downloading a lot of stuff, until it downloaded Plone 4 egg itself as a dependency.

我找不到3.17的真正固定版本的源，该版本可以安装Collector.alias，这就是为什么我问这个问题，我想知道SO的任何人是否有类似的问题. /p>

I couldn't find a source of really pinned versions for 3.17 that would make possible to install collective.alias, that's why I'm asking this question, I would like to know if anyone at SO had a similar problem.

推荐答案

collective.alias取决于灵活性. plone3不完全支持敏捷.而且我猜您将需要升级到3.3.

collective.alias depends on dexterity. Dexterity is not fully supported on plone3. And I guess you will need to upgrade to 3.3.

Dexterity需要Plone4.1才能很好地处理原型内容并具有所有plone功能(历史记录，差异，锁定等)

Dexterity needs Plone4.1 to play well with archetypes content and have all plone feature (history, diff, lock, ...)

尝试一下:

extends=
http://good-py.appspot.com/release/dexterity/1.0?plone=3.3.5

这篇关于是否可以在3.1.7 plone中使用collection.alias?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！